Thanks for the report. I noticed I included the .js files in the latest release. That’s caused issues with linux users in the past. If you delete the .js files, does the ts file generate a working js file when you run the server?

Thanks for the reply!

This has been an issues for months and I’ve just finally made a comment. I did delete the .js files just to be sure and it did not fix it.

I believe this is a fundamental difference in Linux vs Windows with how the .split method works. I modified the constructor as follows to try to understand the difference:

constructor(container: DependencyContainer) { this.container = container; this.pkg = require(“../package.json“); this.modName = this.path.basename(this.path.dirname(__dirname.split(’/’).pop()!)); this.logger.info(dirname: ${\_\_dirname}); this.logger.info(split: ${\_\_dirname.split('/')}); this.logger.info(pop: ${\_\_dirname.split('/').pop()}); this.logger.info(pop!: ${\_\_dirname.split('/').pop()!}); this.logger.info(path.dirname: ${this.path.dirname(\_\_dirname.split('/').pop()!)}); this.logger.info(modname: ${this.modName}); } which prints out the following on Linux

dirname: /opt/server/user/mods/redlaser42-HD Vanilla Trader Pics/src split: ,opt,server,user,mods,redlaser42-HD Vanilla Trader Pics,src pop: src pop!: src path.dirname: . modname: . and the following on WIndows

dirname: C:\Users\Rob\Documents\Applications\SPTarkov\zDev\SPT-310\user\mods\redlaser42-HD Vanilla Trader Pics\src split: C:\Users\Rob\Documents\Applications\SPTarkov\zDev\SPT-310\user\mods\redlaser42-HD Vanilla Trader Pics\src pop: C:\Users\Rob\Documents\Applications\SPTarkov\zDev\SPT-310\user\mods\redlaser42-HD Vanilla Trader Pics\src pop!: C:\Users\Rob\Documents\Applications\SPTarkov\zDev\SPT-310\user\mods\redlaser42-HD Vanilla Trader Pics\src path.dirname: C:\Users\Rob\Documents\Applications\SPTarkov\zDev\SPT-310\user\mods\redlaser42-HD Vanilla Trader Pics modname: redlaser42-HD Vanilla Trader Pics Clearly what returns from split on Linux can be handled by pop but when it’s fed into the path.dirname function what you actually want is not what comes out. I’m surprised any Linux users have had success without modifying it (that’s what I’ve done for the last 6 months or so and just forgot about it until I upgraded to 3.10 and had to do it again)

Other Options

I also did a bunch of tinkering with some other options so if you don’t want to hard code the mod name in.

Relative Path

const filepath = ${PreSptModLoader.getModPath(this.modName)}res/; to

const filepath = ${this.path.join(\_\_dirname, "..", "res/")}; I think this would also allow you to remove the PreSptModLoader dependency (if you so desire)

Use the pkg dependency to dynamically create the modName

this.modName = this.path.basename(this.path.dirname(__dirname.split(’/’).pop()!)); to

this.modName = ${this.pkg.author}-${this.pkg.name};

Awesome, thanks for looking into this! I’ll be sure to include one of these changes in the next update.

Thanks a bunch!

Any chance you can revisit this? I believe it’s still an issue.

Hmm basic troubleshooting steps

• What SPT and Mod version? OS?
• The HD Vanilla Trader Pics folder is in the \user\mods?
• There are no files in \user\sptappdata\files\trader\avatar before loading in?

Worked now, my \user\sptappdata\files\trader\avatar was not empty. Ty

Thanks, I think I’ve gotten that before. I will look into it tonight. You could download 1.0 and drop in the new pics in the meantime.

That’s just what I did

Should be all good now. Ty for the report

Appreciate it!

You can also “Clear Temp Files” in the SPT Launcher settings.

Not sure what this could be having not done the coding, but there are other alternate trader pic mods you could try and use these photos with.

This should be fix now btw