Map-exit handlers - Githubissues

skunkfrukt / oblong-conglomerate

An epic tale of self-discovery.

Do What The F*ck You Want To Public License

0 stars 0 forks source link

Map-exit handlers #33

Closed skunkfrukt closed 10 years ago

skunkfrukt commented 10 years ago

[x] Detect the player exiting the map.
[x] Stage parameters for handling exit at different edges.
[x] 'block' behaviour: treat pseudo-tiles outside the map as obstacles.
[x] 'void' behaviour: treat pseudo-tiles outside the map as non-obstacles.
[x] Separate functionality for edges that lead to other stages?

skunkfrukt commented 10 years ago

'block' and 'void' behaviours determine what happens when the player hits the edge, while 'death' and 'next' behaviours determine what happens when the player exist the screen completely. The two latter thus imply a 'void' behaviour in the first case.

skunkfrukt commented 10 years ago

Town: 'void' T; 'next' R; 'block' B, L.
Stage 1: 'void' T; 'next' R; 'block' B, L.
Stage 2: 'next' T; 'block' R, L; 'die' B.
Stage 3: 'void' T; 'block' R, L; 'block' B pre-OC, 'next' post-OC. Need additional functionality.
Stage 2 (return): 'block' T, R; 'die' B; 'next' L.
Stage 1 (return): 'void' T; 'block' R, B; 'next' L.

skunkfrukt commented 10 years ago

Re. Stage 3: Since the OC triggers a text scene, maybe treat pre- and post-OC scenarios as separate stages:

Stage 3 (pre-OC): 'void' T; 'block' R, B, L.
Stage 3 (post-OC): 'void' T; 'block' R, L; 'next' B.

skunkfrukt commented 10 years ago

Maybe set 'die' B on all stages to cause a respawn if the collisions fail for some reason.