item_healthkit_full, item_ammopack_full and all the other entities in this category got some new parameters in TF2C such as "force_respawntime_override_timer". However this keyvalue is evil because it causes VVIS and VRAD compiles to fail giving "ParseEpar: token too long" & "Command failed with return code 0x1!" errors! A very serious problem when these entities are used on every map!
Here is a compile log where this happens on an empty map:
compile.txt
And here is the empty map vmf:
test_tf2cnocompilepickups.txt
The map will compile if you delete this keyvalue (needs it missing from fgd to do so) or disable VVIS and VRAD (bad).
If you try to compile this keyvalue in live TF2 hammer with live TF2 compilers, the same fail happens.
This may be an issue with the latest hammer++ version instead of TF2C, but this can be worked around on the TF2C code level by replacing the problem keyvalue name in the .fgd and making both keyvalue names read by the game.
111112oo
commented
1 month ago
item_healthkit_full, item_ammopack_full and all the other entities in this category got some new parameters in TF2C such as "force_respawntime_override_timer". However this keyvalue is evil because it causes VVIS and VRAD compiles to fail giving "ParseEpar: token too long" & "Command failed with return code 0x1!" errors! A very serious problem when these entities are used on every map!
Here is a compile log where this happens on an empty map: compile.txt And here is the empty map vmf: test_tf2cnocompilepickups.txt The map will compile if you delete this keyvalue (needs it missing from fgd to do so) or disable VVIS and VRAD (bad). If you try to compile this keyvalue in live TF2 hammer with live TF2 compilers, the same fail happens.
This may be an issue with the latest hammer++ version instead of TF2C, but this can be worked around on the TF2C code level by replacing the problem keyvalue name in the .fgd and making both keyvalue names read by the game.