Project Zomboid

Project Zomboid

[B42] Knox Event Expanded NPC mod [alpha v0.3.6-2]
Suddenly not working (Linux).
Hi. I apologize for being a bother, but the mod appears to have stopped working, and I can't figure out how to make it happy again.

I'm running Linux, and I have two disks, one SSD mounted on / and some large capacity spinning rust mounted on ~/Media. I have steam set up with install locations on both of these disks.

Zomboid was originally installed to the steam directory on ~/Media. I moved it to the one on ~/.steam (SSD) in an attempt to improve performance. This is when the mod stopped working.

I discovered that during the move, my ProjectZomboid64.json file had been reverted, removing the Knox jar from the classpath. I fixed this, and marked the file readonly.

The mod still did not work, at least as far as I can tell. What tipped me off that it had broken to begin with is that the option to radio survivors has disappeared from the right-click menu on the valu-tech walkie-talkie.

I tried starting a new save, and the mod still did not work. The screen to simulate the population did not appear. I spawned in a walkie-talkie and the option to radio survivors did not appear.

I have verified that the proper classpath entry is back in ProjectZomboid64.json, uninstalled and reinstalled the mod, verified that the mod is at the bottom of the load order, and tried starting a new game.

I have not tried moving Zomboid back to the original drive. This is what I plan to try next, but I sure would rather have it on the SSD even if that does "fix" it.

So I am not sure what to try next, other than that. Any suggestions would be appreciated. And thanks for all your work on this mod. It's pretty sweet.
< >
1-5 / 5 のコメントを表示
Update: Moving it back to the spinning rust (and updating the path in ProjectZombiod64.json too of course) didn't fix it. However, I was able to get it working by rsyncing the files into the PZ directory manually.

I am not sure what broke, then. It was working fine with just the classpath pointing to your jar at first. Weird.
Snejk  [開発者] 8月16日 11時03分 
I don't recommend using the old installation method. It will soon be dropped completely.

Worth noting is that ~ isn't expanded when parsing classpath i.e. you need to write out the full absolute path /home/<username>/.... etc.
最近の変更はSnejkが行いました; 8月16日 11時37分
Snejk の投稿を引用:
I don't recommend using the old installation method. It will soon be dropped completely.

Worth noting is that ~ isn't expanded when parsing classpath i.e. you need to write out the full absolute path /home/<username>/.... etc.
the old installation method will be dropped? what about those who want to stay using it (like me)? dont really want to use the new method
Snejk  [開発者] 8月16日 12時31分 
I'm tired of dealing with false bug reports because people don't update, even if it's literally written on the screen. Hence, the new update method will become permanent.
Snejk の投稿を引用:
I'm tired of dealing with false bug reports because people don't update, even if it's literally written on the screen. Hence, the new update method will become permanent.
why not just make it so you dont respond to bug reports from people using the old installation method? i only ask since i'd just like the option to use the old method be able to be used
< >
1-5 / 5 のコメントを表示
ページ毎: 1530 50