I'm switching back to GZDooM... :facepalm

[WindowsVistaLover5570]

So, I'm still not using GZDoom, and I totally paid the price. I was playing TUCQ, and if you do it in plain ZDooM, there is a HORRIBLE bug where the keys are picked up, but the game can't tell, and you can't open key doors. So, DO NOT use TUCQ in ZDooM!

EDIT: GZDooM Git builds don't like TUCQ.

[Awesomedude249]

I remember this happening to me when I tried it with ZDooM, but why don't you use GZDooM? It has a lot more features than ZDooM, and most mods nowadays require it anyway. I can't run GZDooM with my current PC though, as GZDooM doesn't like Intel integrated graphics

[WindowsVistaLover5570]

Just found a major bug in GZDooM where most things are invisible. Stop breaking, OpenGL!

[75]

The key bug in TUCQ happened because Boingo's code had issues with duplicate Actor names, and he needed to add LOCKDEFS.

One thing that's very important for modders to remember is that all of the actors (for every zdoom supported game, Strife, Doom, Heretic, Hexen, and Chex) are loaded by the engine, regardless of which IWAD you're using, and the engine doesn't know what to do when you create an actor with the exact same name as one that's already defined.

What he has in the latest release (this won't work, BlueCard is already defined in Doom)

ACTOR BlueCard : DoomKey 5
{
  SpawnID 85
  Inventory.PickupMessage "Picked up a blue key."
  Inventory.Icon "STKEYS0"
  +FORCEXYBILLBOARD
  States
  {
  Spawn:
    BKEY A 10
    BKEY B 10 Bright
    Loop
  }
}

What he needed to do:

ACTOR TUCQBlueCard : ChexBlueCard 5
{
   Inventory.Icon "STKEYS0"
   Inventory.PickupMessage "Picked up a blue key"
   +FORCEXYBILLBOARD
}

Unfortunately at this point he probably needs to go through and check all of his actor names, to make sure that none of them conflict with any IWAD's actors; I ran into the exact same problem with Chex Pack early on.

I spent a bit of time helping Boingo out with this in IRC, hopefully he'll get this resolved soon.

[Boingo the Clown]

What 75 said.

It's a pain to have everything that has worked up until now stop working in the latest version of GZDooM.

Try using an older version of GZDooM for now.  There will probably be a new release of T.U.C.Q. in a month or two.

[WindowsVistaLover5570]

The key bug mostly happens in newer git versions of ZDooM (maybe because ZScript?) and not the latest stable version.

[75]

I'm not sure it's related to the svn builds, the keys didn't seem to work in gzdoom 2.3.2 (from March 13th, 2016) either.