Welcome to the ZDoom Forums!

/le-dumb

is there a reason that invalid targets don't produce at least a warning? i imagine logging a "warning: field not found" couldn't hurt foward compatibility

From the UDMF specs:

[quote]
For purposes of forward compatibility, user-defined fields are restricted to
beginning with the string "user_", but are otherwise normal identifiers.
Implementing editors should not restrict the entry of custom field names to
those beginning with "user_", however, in order to avoid problems with
out-of-date configurations.

[/quote]

It is fully intentional that other keys cannot be queried. The UDMF specification explicitly prohibits it.

#include "zcommon.acs"

script 01 (void)
{
  log(i:GetLineUDMFInt(3, "triggertype")); //int lineid, string fieldname
}

GetLineUDMFInt don't work. Attached example wad is two sectors, one inside the other. One linedef (not sidedef) of the inner sector has the custom user key (called property in DB2) named "triggertype", an integer, with the value of 15. Said line is tagged 3. This same line, onuse, repeatableaction, will execute script 01.

Scriptlump is simply as follows: [code]#include "zcommon.acs"

script 01 (void)
{
log(i:GetLineUDMFInt(3, "triggertype")); //int lineid, string fieldname
}[/code]

For all intents and purposes, the player should see 15 in the console and upper left corner, correct? 'Fraid not.

Regardless of tag number, field name, field value, direct usage or preloading in a variable in a script, it returns 0. It also returns 0 if triggertype is not defined. that's totally unexpected behavior for a really big error like that.

You can even open it up in SLADE3 and scroll to line 118 - 131 to look at the linedef def ( :lol: ) ; triggertype is defined.

[size=150]tl;dr GetLineUDMFInt seems to always = 0; even when acting on invalid targets.[/size]