Cannot use xs scripts from mods: EXTERN(1): XS: Error 0354: failed to open file 'wtf.xs'

[HSZemi]

GAME INFORMATION

^{These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.}

• GAME BUILD #: 101.101.44834.0 6148570
• GAME PLATFORM: Steam
• OPERATING SYSTEM: Linux

ISSUE EXPERIENCED

^{DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.}

I want to include an xs script (e.g. wtf.xs) in a rms script (e.g. TradeCartNothing.rms). Both scripts are part of a local mod.
When I launch a game with the rms script, I get the error:

EXTERN(1): XS: Error 0354: failed to open file ‘wtf.xs’.

and the modifications from the xs script are not applied.

If I place the xs script directly into the xs folder in the game files, it works.

FREQUENCY OF ISSUE

^{How often does the issue occur?}

• 100% of the time / matches I play (ALWAYS)

REPRODUCTION STEPS

^{List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!}

Here’s the steps to reproduce the issue:

1. Create a new folder named test in your local mod folder (Games/Age of Empires 2 DE/mods/local) and create a valid info.json file inside it
2. Inside that test folder, create an resources/_common/xs folder
3. Inside that xs folder, create an xs script called wtf.xs
4. Inside the test folder, create a resources/_common/random-map-scripts folder
5. Inside that random-map-scripts folder, create a random map script called TradeCartNothing.rms, which includes the line #includeXS wtf.xs
6. Start the game and make sure that the new local mod is enabled
7. Start a game against the AI on the TradeCartNothing map
8. Receive the attached error message

EXTERN(1): XS: Error 0354: failed to open file ‘wtf.xs’.

EXPECTED RESULT

^{What was SUPPOSED to happen if the bug you encountered were not present?}

The game should find the xs script and execute it.

IMAGE

^{ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.}

[HSZemi]

This is the mod layout:

[MrKirby7215]

Just to add to this report:

This also happens in scenarios. If you add an xs script in the scenario and load it up using multiplayer lobby, it’ll work for you but not for any other player that doesn’t have the XS script. Even though the main xs file is saved INSIDE of the scenario file. So it is available, just not used. Include statements do break it either way though, as they aren’t stored in the scenario. Which I guess is a bug on it’s own…

[TWest6709]

Bumping this report, right now I’m writing in my mod instructions that players need to copy and paste the xs file from the mod into their local files.

[Bassefrom]

Has this been fixed yet?

[peacekeeper1442]

How to fix? I found that if add absolute path to xs file when starts without error, but this is wrong because in multiplayers mod will be broken. Maybe this is path problem? xs folder must be in another path?

[VisibleAnt2066]

Was this fixed, its a shame to have xs scripting feature and not being able to use it in custom scenario

[VisibleAnt2066]

Just for clarity, the game looks for the xs inside the global resources\_common\xs instead of the folder inside the mod itself

[IkoKnight]

Hello everyone!

Sorry for the delay. Thank you for letting us know this! We are already tracking this issue ヾ(＾∇＾)

[Super-Skurken]

It should look in the mod folder first, like with everything else!

We have the same issue with AI scripting.

(include "../ai/MyAI/XS/myXS.xs")

should look for an xs within my AI folder in my mod.

(include "myXS.xs")

should look for an xs within the xs folder in my mod.

They didn’t work a few months ago. I haven’t tested again recently, but I have been reading the patch notes. They do not mention fixing any such bug.

Update: I tested the first one again later the same day (on the current patch). It still doesn’t work!

[TWest6709]

We have the same problem with map scripts. An xs file that is included in the mod directory is not searched for. We can use a relative path from the profile folder to the xs file… but can’t include spaces in the file path (surrounding the path with quotation marks does not work), which means the name of the mod can’t include spaces lol.