informator/delivivor
1
0
Fork 0
Code Issues 6 Pull requests 1 Projects 1 Releases Packages Wiki Activity Actions

GameState architecture #1

New issue
Open
opened 2026-07-13 00:51:58 +01:00 by informator · 1 comment
informator commented 2026-07-13 00:51:58 +01:00
Owner
Copy link

Implement Game state, transition and propagation to allow augment selection phase implementation, alongside with pause menu and prepare for upcoming states

Implement Game state, transition and propagation to allow augment selection phase implementation, alongside with pause menu and prepare for upcoming states
informator added reference chore/gameState 2026-07-13 16:42:44 +01:00
informator removed reference chore/gameState 2026-07-14 21:36:21 +01:00
informator commented 2026-07-14 21:42:00 +01:00
Author
Owner
Copy link

PR http://steinsgateway:3000/informator/delivivor/pulls/6 implements rough gamestate architecture as base.

GameController component is core and manage every modules needed in a gameplay level :

  • PlayerController : Handles player instantiation, interaction and lifecycle. (including UI)
  • MonsterSpawn : Handles monsters spawing and lifecycle.

GameController holds previous and current GameState values, changing current GameState will call PlayerController and MonsterSpawn directly. Latters will propagate the state change without unification.

Still TODO : Plan and implement an unification architecture to keep a good readability and maintainability

PR http://steinsgateway:3000/informator/delivivor/pulls/6 implements rough gamestate architecture as base. GameController component is core and manage every modules needed in a gameplay level : - PlayerController : Handles player instantiation, interaction and lifecycle. (including UI) - MonsterSpawn : Handles monsters spawing and lifecycle. GameController holds previous and current GameState values, changing current GameState will call PlayerController and MonsterSpawn directly. Latters will propagate the state change without unification. Still TODO : Plan and implement an unification architecture to keep a good readability and maintainability
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
chore/variousTests
main
No results found.
Labels
Clear labels   
art

   
chore
No labels
art
chore
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Core Development
Assignees
Clear assignees
No assignees
informator
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#6 Rough GameState architecture
informator/delivivor
Reference
informator/delivivor#1
No description provided.