search

Warzone2100 / old-trac-import

Archived Import of (old) Warzone 2100 Trac
0 stars 0 forks source link

Mods not getting loaded #4835

Closed wzdev-ci closed 6 years ago

wzdev-ci commented 6 years ago

resolution_closed type_bug | by OpenSourceGames

warzone2100-3.2.3_portable

win64

To reproduce:

  1. make mods/autoload contain: ARmod_beta3.wz sequences.wz

  2. Start new campaign game and save the game

  3. Restart WZ and load that game

Error message:

Warzone has detected a problem A non fatal error has occured. [rebuildSearchPath:446] The required mod could not be loaded: ARmod_beta3.wzsequences.wz,

Warzone will try to load the game without it.

Seems to be a delimiter error or something like that.

Issue migrated from trac:4835 at 2022-04-16 13:09:17 -0700

wzdev-ci commented 6 years ago

OpenSourceGames uploaded file err.png (7.8 KiB)

error message err.png

wzdev-ci commented 6 years ago

Berserk Cyborg changed status from new to closed

wzdev-ci commented 6 years ago

Berserk Cyborg changed resolution from ` toclosed`

wzdev-ci commented 6 years ago

Berserk Cyborg changed blocking which not transferred by tractive

wzdev-ci commented 6 years ago

Berserk Cyborg changed blockedby which not transferred by tractive

wzdev-ci commented 6 years ago

Berserk Cyborg commented

Seems to be a delimiter error or something like that.

Yep, this was fixed in #2918 (after 3.2.3 release). Feel free to try this on the development builds at https://github.com/Warzone2100/warzone2100#latest-development-builds.

A PhysicsFS bug will prevent the dev builds from starting on Windows 10 build 1809+ at the moment.

wzdev-ci commented 6 years ago

OpenSourceGames commented

Thanks, I tested the https://ci.appveyor.com/api/projects/Warzone2100/warzone2100/artifacts/warzone2100-master_x86_portable.zip?branch=master&job=Environment%3A%20APPVEYOR_BUILD_WORKER_IMAGE%3DVisual%20Studio%202017%2C%20WZ_JOB_ID%3Drelease_x86 release and copied the savegame into it. I got the same error, I added the mod files, got the same error. I'm assuming this means the savegame file has the issue.

wzdev-ci commented 6 years ago

Berserk Cyborg commented

Saves affected by that bug will still have incorrect comma separation. Also, saves from 3.2.3 will not be compatible with the development builds (and next releases) due to many changes and improvements to the campaign scripts.