[ImBatman]

Hi guys,

Thank you all who worked on Eduke32 for the great job, I completed Blood with NBlood (a derivative of Eduke32), DN3D with Eduke32, RR with Rednukem.

Now I want to play Shadow Warrior. I downloaded a voxel pack from moddb. Instructions are: place `Shadow-Warrior-Voxel-Pack.zip` into the 'autload' folder and make sure you checked the "Enable autoload folder" checkbox.

Unfortunately, I don't see the checkbox when starting `voidsw.exe`. It's from the same archive `eduke32_win64_20260203-10664-ba6b7bb1d.7z`, where I copied `eduke32.exe` from, but `eduke32.exe` has the checkbox and `voidsw.exe` doesn't.

[Hendricks266]

My development strategy for VoidSW has been a painstaking process of wiring up JFSW's game code to EDuke32's engine, adding comparable functionality, and going through any engine/audiolib/etc API changes with a fine-tooth comb to ensure they are documented, executed properly, and don't break accuracy. The autoload feature as implemented in EDuke32 is defective by design in that it only adds the contents to the virtual filesystem without any further management, leading to the well-known problem having to edit your own def files if you want more than a single zip file to work at the same time. Therefore, I have decided that VoidSW will simply not get the autoload anti-feature as it currently stands, and will only get whatever its proper replacement is.

If you only have a single mod to use such as the voxel pack, you can simply extract the zip file into your VoidSW directory so that sw.def is next to voidsw.exe, and it will work.

[ImBatman]

Hendricks266, on 22 June 2026 - 02:32 PM, said:

If you only have a single mod to use such as the voxel pack, you can simply extract the zip file into your VoidSW directory so that sw.def is next to voidsw.exe, and it will work.

Thank you, Hendricks266, I should have realized myself.