DMX event request; Self-Destruct
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 869
- Forks
- 222
- Avg merge
- 18h 33m
- Merged PRs (30d)
- 1
Description
I'm not sure if all that I am asking for is possible.
- Self Destruct Initiated by Engineer (should be pretty straight forward)
- Awaiting input from each station; awaiting A, awaiting B, awaiting C, etc.
- Successful input of code from each station.
- Failed/wrong code input
- Self Destruct Activated (all codes entered successfully)
So here is what may not be possible:
2.A. Instead of awaiting input A, B, C create a state awaiting input from Helms, Science, Relay, etc. I have not delved into the code but it appears that what stations (Helms, Science, Relay, etc.) get 'assigned' the 'Alpha' code (A, B, C) is random so I'm not sure that there is a way to identify which 'Station' is next in the cue.
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
No files or tests are named. Start by locating the DMX event and self-destruct state handling, then trace how station codes are assigned and displayed. Done would mean the event supports engineer initiation, per-station waiting and code results, activation after all correct inputs, and a clear determination of the next station.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100