You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To workaround !special targetnames still recieving instance fixups in P1, I attempted to add the outputs through a comp_kv_setter, using the keyvalues so the fixups aren't applied (since outputs are stored as part of the keyvalues internally).
However, this resulted in only a single OnStartTouch output being added with an empty value, then the three intended outputs were added with an output name of kv_value_global (the name of the Value - String keyvalue on comp_kv_setter itself):
(The second OnStartTouch output was present originally on the entity)
The text was updated successfully, but these errors were encountered:
Hmm, this isn't really something I intended you to be able to do :). Though in the BSP they are the same, in srctools they're treated like in VMFs, being distinct kinds of values. I probably will want to add a specific ent for this purpose perhaps, but also make this not produce that nonsensical result.
To workaround


!special
targetnames still recieving instance fixups in P1, I attempted to add the outputs through acomp_kv_setter
, using the keyvalues so the fixups aren't applied (since outputs are stored as part of the keyvalues internally).However, this resulted in only a single
OnStartTouch
output being added with an empty value, then the three intended outputs were added with an output name ofkv_value_global
(the name of the Value - String keyvalue oncomp_kv_setter
itself):(The second OnStartTouch output was present originally on the entity)
The text was updated successfully, but these errors were encountered: