The Config.asm file is currently overloaded with various patches used to activate or deactivate specific hacks. The plan is to reorganize this by relocating each hack into its own separate file within a patch folder. This way, the Config.asm file will be streamlined to only include options for enabling or disabling, ensuring a cleaner and more manageable configuration.
Expected Result
New folder for patches, each patch will have its own file and be included "incsrc" from the main.asm file
Benefits
[x] More manageable config.asm file
[x] Each patch is in a separate file and easy to modify
Actual Changes
New folder for patches, each patch will have its own file and be included "incsrc" from the main.asm file
Acceptance criteria
[x] Verify all the patches still function after code refactor.
[x] Provided brief description of the actual changes (Solution) performed.
Sprint Ready Checklist
[x] Acceptance criteria defined.
[x] Identified solution / steps to satisfy acceptance criteria.
Mhopkinsinc
commented
7 months ago
User story
The Config.asm file is currently overloaded with various patches used to activate or deactivate specific hacks. The plan is to reorganize this by relocating each hack into its own separate file within a patch folder. This way, the Config.asm file will be streamlined to only include options for enabling or disabling, ensuring a cleaner and more manageable configuration.
Expected Result
New folder for patches, each patch will have its own file and be included "incsrc" from the main.asm file
Benefits
Actual Changes
Acceptance criteria
Sprint Ready Checklist