convert: non-nyan data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Some of the converted data is not suitable for nyan and should be handled otherwise.
Interface
The location of buttons for unit and building creation is written into the .dat. The location of the rest of the interface, including buttons, minimap, quickbars, is hardcoded directly into the engine. Ideally the elements are freely arrangeable (#738 ) or decided by the modpack creators. Scripting is a good option here, maybe as an entry point for #735 .
Player colors
In the Genie Engine, the player colors (unit color, outline color, minimap color) are tied to the player number. We don't need this strict dependency, but can use the old values as default colors for new games. The color settings should be scriptable like the interface.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how converted .dat data reaches the engine, then locate the hardcoded handling for interface elements and player colors. Review the related goals in #738 and #735. Done means non-nyan interface data and player colors can be controlled through scripting, with existing colors retained as defaults.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100