KEYCONF trouble with SetSlot

[Tormentor667]

This problem is existing in 1.2.01 but not in 1.1.06, that's what I can say so far. Here is the code for the KEYCONF lump in question (from UTNT)

Code: Select all

clearplayerclasses
addplayerclass Marine
addplayerclass Scout
addplayerclass Commando

weaponsection "TNT3-New Weapons"

setslot 2 NewPistol           
setslot 3 NewShotgun NewSuperShotgun
setslot 4 NewChaingun STMinigun
setslot 6 PlasmaRifle Flamer
setslot 8 PyroCannon

So the problem is that in the latest version of GZDoom, I can't select the Rocket Launcher, the Fist and the BFG9000 anymore although I haven't touched slots 1, 5 or 7 in any way. The only weapons available are those for which I have applied a weapon via "setslot". In 1.1.06 this worked as intended. "Setslot" redefined the slots, and all the other slots stayed the same making it possible to select the Rocket Launcher, the Fist and the BFG.

[Graf Zahl]

If this bothers you, please re-report at zdoom's bugs forum. This is a result of the weapon slots redesign. Since weapon assignments are now local to each player class your definitions no longer inherit the DoomPlayer's weapon assignments - and this can't be changed back without breaking the entire system.

[Rex Claussen]

So the problem is that in the latest version of GZDoom, I can't select the Rocket Launcher, the Fist and the BFG9000 anymore although I haven't touched slots 1, 5 or 7 in any way. The only weapons available are those for which I have applied a weapon via "setslot".

I know this is not the optimal solution, but couldn't you define Slot 1 for the fist, Slot 5 for RL, & Slot 7 for BFG?

[Gez]

It's for an already-released mod.

It's odd that a class that inherits from DoomPlayer doesn't inherit from its slots as well; if it would break the system maybe it should be redesigned in a more robust manner...

[Graf Zahl]

The class in question does not inherit from the DoomPlayer - and that's the problem here.