jsgamesoup

Recently I added Sean McCullough's Javascript implementation of the Perlin noise algorithms to jsGameSoup. These Academy Award winning algorithms by Ken Perlin are fantastic for adding procedural content to your games. The RPG map above with grass ... [More] , water, road, sand, and tree tiles represented in the different colours, was produced with the simplex noise demo here. It can randomly generate a basically infinite number of unique RPG maps of basically infinite size. Check the jsGameSoup documentation for more details. [Less]

Recently I added Sean McCullough's Javascript implementation of the Perlin noise algorithms to jsGameSoup. These Academy Award winning algorithms by Ken Perlin are fantastic for adding procedural content to your games. The RPG map above with grass ... [More] , water, road, sand, and tree tiles represented in the different colours, was produced with the simplex noise demo here. It can randomly generate a basically infinite number of unique RPG maps of basically infinite size. Check the jsGameSoup documentation for more details. [Less]

I have included a modified version of Benjamin Hardin's 2009 A* implementation in jsGameSoup. This is a nice general way for entities in your game to find a path between two squares on a two dimensional board with some obstructed squares. Check the demo here and the documentation here. Have fun!

I have included a modified version of Benjamin Hardin's 2009 A* implementation in jsGameSoup. This is a nice general way for entities in your game to find a path between two squares on a two dimensional board with some obstructed squares. Check the demo here and the documentation here. Have fun!

I have included a modified version of Benjamin Hardin's 2009 A* implementation in jsGameSoup. This is a nice general way for entities in your game to find a path between two squares on a two dimensional board with some obstructed squares. Check the demo here and the documentation here. Have fun!

A finite-state machine is an algorithmic structure which is frequently useful in video games. A finite-state machine can be used to simulate any game entity which has a set of discrete states which it changes between, and which looks different and/or ... [More] exhibits different behaviour in each of those states. Here are some examples: A non-player character which wanders around and then starts chasing the player once they come in range. A door which switches between closed, opening (animated), and open states. A spacecraft under player control which has an proximity-triggered docking procedure. Many video game entities can be most easily modelled in this way. In jsGameSoup it is now very easy to create state machines like this. Simply include "statemachine.js" in your HTML file: Then call the statemachine() function on an entity inside it's constructur: function MyEntity() { statemachine(this); ... } After that your entity will have a new method set_state(state) which switches it between different arbitrary states. These states are completely up to you. You can define different behaviours, events, and visual representations by creating multiple versions of jsGameSoup's normal expected methods. For example, let's say the entity above has a state "wandering" and a state "seeking" when it is moving towards the player. In this case we would define two different sets of methods: /****** Update and draw this entity in the wandering state. ******/ this.wandering_update = function() { // update the entity in "wandering" mode ... } this.wandering_draw = function() { // draw the entity in "wandering" mode ... } /****** Update and draw this entity in the seeking state. ******/ this.seeking_update = function() { // update the entity in "seeking" mode ... } this.seeking_draw = function() { // draw the entity in "seeking" mode ... } When you want to put the entity into a particular state, you call set_state(state), for example in the init() method of the entity to put it into a certain state from the start: this.init = function() { this.set_state("wandering"); } Here is an example of a jsGameSoup entity class which switches between a "chill" and an "antsy" state. View source to see how it works. Hopefully this will help you write games and get them infront of players more quickly. [Less]

A finite-state machine is an algorithmic structure which is frequently useful in video games. A finite-state machine can be used to simulate any game entity which has a set of discrete states which it changes between, and which looks different ... [More] and/or exhibits different behaviour in each of those states. Here are some examples: A non-player character which wanders around and then starts chasing the player once they come in range. A door which switches between closed, opening (animated), and open states. A spacecraft under player control which has an proximity-triggered docking procedure. Many video game entities can be most easily modelled in this way. In jsGameSoup it is now very easy to create state machines like this. Simply include "statemachine.js" in your HTML file: Then call the statemachine() function on an entity inside it's constructur: function MyEntity() { statemachine(this); ... } After that your entity will have a new method set_state(state) which switches it between different arbitrary states. These states are completely up to you. You can define different behaviours, events, and visual representations by creating multiple versions of jsGameSoup's normal expected methods. For example, let's say the entity above has a state "wandering" and a state "seeking" when it is moving towards the player. In this case we would define two different sets of methods: /****** Update and draw this entity in the wandering state. ******/ this.wandering_update = function() { // update the entity in "wandering" mode ... } this.wandering_draw = function() { // draw the entity in "wandering" mode ... } /****** Update and draw this entity in the seeking state. ******/ this.seeking_update = function() { // update the entity in "seeking" mode ... } this.seeking_draw = function() { // draw the entity in "seeking" mode ... } When you want to put the entity into a particular state, you call set_state(state), for example in the init() method of the entity to put it into a certain state from the start: this.init = function() { this.set_state("wandering"); } Here is an example of a jsGameSoup entity class which switches between a "chill" and an "antsy" state. View source to see how it works. Hopefully this will help you write games and get them infront of players more quickly. [Less]

A finite-state machine is an algorithmic structure which is frequently useful in video games. A finite-state machine can be used to simulate any game entity which has a set of discrete states which it changes between, and which looks different ... [More] and/or exhibits different behaviour in each of those states. Here are some examples: A non-player character which wanders around and then starts chasing the player once they come in range. A door which switches between closed, opening (animated), and open states. A spacecraft under player control which has an proximity-triggered docking procedure. Many video game entities can be most easily modelled in this way. In jsGameSoup it is now very easy to create state machines like this. Simply include "statemachine.js" in your HTML file: Then call the statemachine() function on an entity inside it's constructur: function MyEntity() { statemachine(this); ... } After that your entity will have a new method set_state(state) which switches it between different arbitrary states. These states are completely up to you. You can define different behaviours, events, and visual representations by creating multiple versions of jsGameSoup's normal expected methods. For example, let's say the entity above has a state "wandering" and a state "seeking" when it is moving towards the player. In this case we would define two different sets of methods: /****** Update and draw this entity in the wandering state. ******/ this.wandering_update = function() { // update the entity in "wandering" mode ... } this.wandering_draw = function() { // draw the entity in "wandering" mode ... } /****** Update and draw this entity in the seeking state. ******/ this.seeking_update = function() { // update the entity in "seeking" mode ... } this.seeking_draw = function() { // draw the entity in "seeking" mode ... } When you want to put the entity into a particular state, you call set_state(state), for example in the init() method of the entity to put it into a certain state from the start: this.init = function() { this.set_state("wandering"); } Here is an example of a jsGameSoup entity class which switches between a "chill" and an "antsy" state. View source to see how it works. Hopefully this will help you write games and get them infront of players more quickly. [Less]

I wrote this game in a few hours today using jsGamesoup. Is it fun? I would like to know what you think. (Inspired by SpoutDS).

I wrote this game in a few hours today using jsGamesoup. Is it fun? I would like to know what you think. (Inspired by SpoutDS).