EngineHub / EngineHub/CommandHelper
include(), read(), etc within a file use a different base directory when called from cmdline/MC VS interpreter
- Dominant language
- Java
- Stars
- 128
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
This topic was discussed on Discord, this issue serves the purpose of not losing the results.
## Desired behavior
- MC: Relative to script directory (no change).
- Cmdline: Relative to script directory.
- Interpreter/MC interpreter:
- Functions entered directly into the interpreter use the directory set using `cd()` as base directory.
- Included MS files (including the procedures defined within them) use their parent directory as base directory (same behavior as non-interpreter mode).
- Procedures defined in the interpreter use the directory set using `cd()` at definition time for all calls to that procedure.
Contributor guide
Assessment
This issue has not been assessed yet.