[Bug] GM-saved scenario with max impulse and max reverse speeds fails on load
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 869
- Forks
- 222
- Avg merge
- 18h 33m
- Merged PRs (30d)
- 1
Description
On legacy, setting forward and reverse impulse speeds on a PlayerShip and then saving the scenario adds lines for both SetMaxImpulseSpeed and SetMaxReverseSpeed. Loading the resulting scenario then fails.
...
Raised by Smarty on the Bridge Command Discord.
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
Reproduce the failure by saving a legacy scenario with both SetMaxImpulseSpeed and SetMaxReverseSpeed on a PlayerShip, then loading it. Trace the scenario save and load entry points for those two commands and consider the issue done when the generated scenario loads successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100