OVL: confirm unverified field meanings
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation, reverse-engineering
Research direction
The issue names no files, tests or entry points, so begin by finding where the listed fields (texture, palette, mesh, scenery, bone, sound) are read in the repository and where the public notes live. Work through the checklist one field at a time, confirming each meaning from observed behaviour rather than inference. Done means every item is either documented in your own words or marked open, and the trailing-data question has a recorded answer on whether the parser can safely skip it.
Written by the indexing model from the issue text.
Description
Several fields are read but their meaning is inferred from data, not confirmed:
- texture animation value and flag bits
- paletted texture palette byte order
- static shape mesh flags, transparency and sides values
- scenery visual flags and distance semantics
- bone animation rotation axis order and interpolation
- sound descriptor float fields
Track each as a checklist item; confirm through observed behaviour and document in public notes in our own words.
Trailing data
Folded in from #3: each file ends with build-time bookkeeping that is currently skipped.
- Decide whether it carries anything needed at runtime; if not, document that it is safely ignorable and keep the parser tolerant of it.
- Dominant language
- C++
- Stars
- 4
- Forks
- 1
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 156
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 tomast1337/RCT3PlusPlus
-
area:engine enhancement
Difficulty 5/5 Over a week Newbie friendliness 18/100
tomast1337/RCT3PlusPlus#406 ·
Maintainers usually reply within 1 day
-
area:engine enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
tomast1337/RCT3PlusPlus#405 ·
Maintainers usually reply within 1 day
-
area:render area:ui enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
tomast1337/RCT3PlusPlus#401 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
tomast1337/RCT3PlusPlus#384 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
tomast1337/RCT3PlusPlus#383 ·
Maintainers usually reply within 1 day
All issues in tomast1337/RCT3PlusPlus
Similar issues
-
launcher: settings are never saved on macOS — QSettings SystemScope points to /Library/PreferencesOpen
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 82/100
supercollider/supercollider#7872 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA-RTX/ShaderMake#29 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
yetanotherbrowser/yab#1062 ·
Maintainers usually reply within 1 day