[DECOHack] "Safe" Freeing of States from a Starting Label
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the DECOHack state-freeing logic and how its traverser follows state indexes; the issue does not name source files or tests. Investigate how labels are represented and whether a reverse lookup or startup scan is needed. Done means a new clause safely stops freeing at a state with a defined label, without overfreeing; the issue gives no test entry point.
Written by the indexing model from the issue text.
Description
So, DECOHack's state freeing is a tad... overzealous, let's say.
There needs to be a way to safely free a state on a weapon or thing such that it doesn't "overfree" what is expected, despite it being the intended behavior.
A new clause keyword may be in order. Something like:
weapon WP_PISTOL only free Label
Or somesuch language to convey that it should only free that state until it hits a state that has a defined label. Will a reverse lookup need to be in order?
This may turn into a bit of a complicated issue, unfortunately, as the traverser only can see the next state via indexes, not labels. A quick scan may need to be in order at startup to set these up, if not baked into code, initially.
- Dominant language
- Java
- Stars
- 78
- Forks
- 6
- Avg merge
- 17h 32m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from MTrop/DoomTools
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement
Difficulty 3/5 Half a day Newbie friendliness 62/100
-
help wanted
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
enhancement low priority
Difficulty 4/5 3-5 days Newbie friendliness 43/100
Similar issues
-
area/kotlin
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Large page[number] overflows the computed offset and returns the wrong pagePossibly taken @auraseb claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100