Skulltag content script error

[hypnotik]

hello and good evening, I'm sure this topic has been posted before, but I had been able to play servers just fine until recent when I started getting script error for an invasion server I usally played on, now I keep getting an error, I have looked for ways to fix but so far nothing has worked. any help and suggestions would be appreciated. thank you for taking the time to read this, attached is the log for the server I was trying to load.


M_LoadDefaults: Load system defaults.
Using program directory for storage
W_Init: Init WADfiles.
adding D:/Program Files (x86)/zandronum.pk3, 699 lumps
adding D:/Program Files (x86)/Steam/steamapps/common/Doom 2/base/doom2.wad, 2919 lumps
adding D:/Program Files (x86)/announcer/ZanACG.pk3, 104 lumps
adding D:/Program Files (x86)/announcer/ZanGeneric.pk3, 105 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/skulltag_content-3.2-beta2.pk3, 2470 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/complex-doom.v26a2_cdi_1.0b.pk3, 9646 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/complex-doom.v26a2_cdi_1.0b.pk3:acs.wad, 5 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/complex-doom.v26a2_cdi_1.0b.pk3:font.wad, 80 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/complex-doom.v26a2_cdi_1.0b.pk3:terrain.wad, 46 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/lca-v1.5.8_cdi_v1.0b.pk3, 8377 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/lca-v1.5.8_cdi_v1.0b.pk3:lcademo.wad, 8 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/lca-v1.5.8_cdi_v1.0b.pk3:montest.wad, 4 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/complex-doom-invasion_1.0b1.pk3, 33279 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/complex-doom-song_1.0.pk3, 91 lumps
adding C:/Users/hypno/AppData/Local/doomseeker/hpbar-v21-cdi_2.0c.pk3, 38 lumps
I_Init: Setting up machine state.
CPU Speed: 4013 MHz
CPU Vendor ID: AuthenticAMD
Name: AMD FX(tm)-8350 Eight-Core Processor
Family 21 (21), Model 2, Stepping 0
Features: MMX MMX+ SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2
I_InitSound: Initializing FMOD
FMOD Sound System, copyright © Firelight Technologies Pty, Ltd., 1994-2009.
Loaded FMOD version 4.44.64
V_Init: allocate screen.
Using in-memory database. The database will not be saved on exit.
S_Init: Setting up sound.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
ParseSectInfo: Loading sector identifications.
Texman.Init: Init texture manager.
Attempting to remap non-existent texture M_DOOM to MDOOMHD
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.

Execution could not continue.

Script error, "skulltag_content-3.2-beta2.pk3:actors/skulltagweapons.txt" line 141:
"selfobituary" is an unknown actor property

[Sean]

The Skulltag content version corresponds to Zandronum version. If you're trying to join a Zandronum 3.2 server but 3.1 is launching instead, configure your server browser to enable testing versions: https://wiki.zandronum.com/Setting_up_testing_versions

If you're launching the server yourself then use skulltag_content-3.0-beta01.pk3 for Zandronum 3.1.

[Dick Ringeisen]

Old thread, I know, but hey, I used the search function to try and solve my problem before posting.

I am getting this same error. I have tried deleting the wad, reinstalling zandronum, checking and double-checking doomseeker setting, and so on, but I keep getting this error with Complex Doom invasion servers, except for the Polish server, which is running an older version of CDI.

Any advice?

[Ru5tK1ng]

Remove all old version of Zandro and make sure you downloaded the correct version of Skulltag actors off of TSPG.

[Dick Ringeisen]

Remove all old version of Zandro and make sure you downloaded the correct version of Skulltag actors off of TSPG.

Thanks for the response. I'll give things a try, in a bit.

Zandronum + CDI had been working fine, but I took a few months away from it, and when I returned, it downloaded some updated stuff through Doomseeker. After that, I got this error.