What is the most efficient way to deliver my game to the browser? If I make a game with multiple rooms, are all rooms and assets delivered at once to the client browser, or is each room delivered by itself as it is called?
Simplistic example:
Assume I have three rooms for a board game:
0. Main Menu
1. Game room ... with the main board on it.
2. Editor ... for creating custom boards
Should each of these rooms be in a separate game so that they only get sent to the browser when they are in use, or should thy all be in the same application? Will GM send them all at once or one at a time? Or can I control that?
Game module planning
Started by DamonZero, Apr 18 2012 04:38 PM
1 reply to this topic
#1
Posted 18 April 2012 - 04:38 PM
#2
Posted 26 April 2012 - 02:09 AM
If the rooms are all in the same project your game will load them upon loading the game. You can switch to another room using the GML functions:
Its best to keep it all in the same game and change rooms when needed. This way, the people playing your game don't have to link off to another webpage and have to sit through another loading screen.
room_goto(roomname); // Change roomname to the room you want to switch to room_goto_next(); // This will go to the next room available room_goto_previous(); // This will go to a previous room (The room above the current)
Its best to keep it all in the same game and change rooms when needed. This way, the people playing your game don't have to link off to another webpage and have to sit through another loading screen.
Edited by dereklarue, 26 April 2012 - 02:14 AM.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users











