My previous rewrite attempt in explicit-loops stalled, partly due to trying to keep up with features and systems added on other forks.
This stable branch is feature-frozen at v2.5.1.2 of nergantre's master branch. Commits to this branch will be either bugfixes or refactoring.
--Ryplinn
-
DONE Some tests are failing or broken. Restore to green status.
-
DONE [GUI BREAKUP] Move game logic out of GUI. For this step, code reaching into the gui package is fine; code reaching out is not. Might look uglier than before.
-
DONE [GLOBAL BREAKUP] Break up the Global monstrosity. Find similar parts and move them to their own classes/packages.
ENOUGH This looks like a good time to do some post-move cleanup.
-
DONE Make the game loop explicit, or at least document it. (holy balls that was way easier than last time! amazing what focusing on one thing at a time will do)
-
[STATIC DISCHARGE] Reduce reliance on static fields and methods. Static members make testing harder and can introduce spooky action at a distance.
-
IT'S BETTER NOW AT LEAST Concurrency is hard! Build infrastructure to make it easy to do things like wait for user input.
-
DONE Make the night-time match loop explicit.
DONE Kludge combat into compatibility with the match loop so I can playtest.
DONE I want to work out why the main text window is so stuttery/flickery now. I'd like to figure out a way to only paint the text when the player is about to be presented with an interactable prompt.
-
DONE Make the combat loop explicit.
CODER BONUS Providing an save game file as an argument to the main function will now launch that game directly. No more clicking through dialog boxes while debugging! (If we already had a way to do that, I'm gonna feel silly)
-
DONE Make the daytime loop explicit.
-
PRETTY GOOD Fix everything I broke in the previous steps.
-
Migrate combat to an event-based system, or at least some sort of system. Will enable the next step.
- Add hooks to combat phases, movement phases, taking and receiving damage, daytime activities, etc. that trait and status specifications can use to apply their effects.
- Migrate existing traits and statuses to use this system.
-
Separate display and game logic. There will need to be a layer between display logic and game logic, although exactly where that code lives is less important than the conceptual structure.
- HTML styling should be handled on the display style. Having on-screen text stored in an easy-to-parse/compare format somewhere would be helpful.
-
Make most trait and status effects specified in data files, rather than code.
-
Create an editor?
-
man who even knows
-
anything that isn't done yet will probably change