Expected behaviour: loading imports uses the current file's path
Actual behaviour: loading imports always looks at the mod folder path, even when the current file that is loading an import is in a subfolder.
Example:
Say I have the following file/folder structure:
D2RMM 1.6.1.
Expected behaviour: loading imports uses the current file's path Actual behaviour: loading imports always looks at the mod folder path, even when the current file that is loading an import is in a subfolder.
Example: Say I have the following file/folder structure:
mod.ts
imports onlyfile1.ts
file1.ts
importsfile2.ts
andfile3.ts
mod.ts:
file1.ts:
Error: Mod mymod encountered a compile error! Error: BridgeAPI.readModCode: Failed to read mods\mymod\file3.ts