Monster list: Difference between revisions
→MS behavior
(Full page rewrite) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 4: | Line 4: | ||
The [[DAT]] format and as such the MS ruleset allows for a maximum of 128 entries on the monster list ''at level start'', the monster list can expand to any size during play from cloning. Chip and blocks are not on the monster list and are handled separately. The monster list is processed from front to back in the ordered specified by the DAT entry for the level. All movement is done in one shot, choosing a direction, moving, and side effects – such as pressing buttons – are all done for one monster before moving onto the next. | The [[DAT]] format and as such the MS ruleset allows for a maximum of 128 entries on the monster list ''at level start'', the monster list can expand to any size during play from cloning. Chip and blocks are not on the monster list and are handled separately. The monster list is processed from front to back in the ordered specified by the DAT entry for the level. All movement is done in one shot, choosing a direction, moving, and side effects – such as pressing buttons – are all done for one monster before moving onto the next. | ||
Due to the MS ruleset taking the contents of the monster list without any checks, several issues can arise such as a monster listed multiple times (which causes it appear multiple times from a single tile), tiles that aren't monsters appearing in the list (which usually has no effect), or monster tiles without an entry (which leaves an unmoving monster in the level). | Due to the MS ruleset taking the contents of the monster list without any checks, several issues can arise such as a monster listed multiple times (which causes it to appear multiple times from a single tile), tiles that aren't monsters appearing in the list (which usually has no effect), or monster tiles without an entry (which leaves an unmoving monster in the level). | ||
Take this level for example: | Take this level for example: | ||
| Line 22: | Line 22: | ||
The last oddity in the Lynx ruleset is that when loading the level Chip is always at the start of the list (meaning he is processed last due to the reverse order), if Chip is not at the start of list by the time the list is built, he will swap places with the first monster on the list, which can cause the occasional oddity. | The last oddity in the Lynx ruleset is that when loading the level Chip is always at the start of the list (meaning he is processed last due to the reverse order), if Chip is not at the start of list by the time the list is built, he will swap places with the first monster on the list, which can cause the occasional oddity. | ||
=== [[Ruleset#Steam ruleset (CC2)|Steam]] behavior === | |||
The monster list in Steam is functional identical to that of Lynx, except Chip (or Melinda) is not moved to the list's start. | |||
== See also == | == See also == | ||