Saving: Difference between revisions
Saving
(Created page with "The game has the capacity to save the player's progress, including current inventory, health, and moodles. When transitioning between map segments, the un...") |
(Java != JavaScript) |
||
| Line 3: | Line 3: | ||
== Auto-Save == | == Auto-Save == | ||
Every two seconds, the game saves its current state. The game also saves when closing the | Every two seconds, the game saves its current state. The game also saves when closing the Java application. | ||
Progress cannot be manually saved. The goal is to prevent players from optimizing their run-through by reloading before critical moments to "change history". | Progress cannot be manually saved. The goal is to prevent players from optimizing their run-through by reloading before critical moments to "change history". | ||
Revision as of 16:15, 21 December 2011
The game has the capacity to save the player's progress, including current inventory, health, and moodles. When transitioning between map segments, the unoccupied segments remain static: in the absence of the player, no zombies nor NPC will move, food will not rot further, and so on.
Auto-Save
Every two seconds, the game saves its current state. The game also saves when closing the Java application.
Progress cannot be manually saved. The goal is to prevent players from optimizing their run-through by reloading before critical moments to "change history".