Support Lua 5.1 (without LuaJIT)
Open
Nobody has claimed this yet.
Developer Experience
Help wanted
Lua
Modmaker Experience
Portability
- Dominant language
- C++
- Stars
- 3.6k
- Forks
- 536
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 3
Description
To ease scripts debugging and also increase portability, we can support pure Lua 5.1.
We can use https://github.com/WheretIB/LuaDkmDebugger to debug Lua from within the Visual studio, but it doesn't support LuaJIT, so using pure Lua can help in this matter. (https://github.com/WheretIB/LuaDkmDebugger/issues/8) LuaDkmDebugger now supports LuaJIT.
Contributor 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.
Research direction
No files, tests, or entry points are named. Start by locating the engine's current Lua integration and the LuaJIT-related support, then determine what is required for pure Lua 5.1; done means scripts run with Lua 5.1 without LuaJIT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, lua
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100