UDMF Specific functions

[Demolisher]

From ZSpecial.acs:

Code: Select all

	-1:GetLineUDMFInt(2),
	-2:GetLineUDMFFixed(2),
	-3:GetThingUDMFInt(2),
	-4:GetThingUDMFFixed(2),
	-5:GetSectorUDMFInt(2),
	-6:GetSectorUDMFFixed(2),
	-7:GetSideUDMFInt(3),
	-8:GetSideUDMFFixed(3),

Are these usable? They seem to be undocumented.

[Demolisher]

Curiosity strikes again, sorry for the bump, I didn't feel the need for a new thread.

[Ceeb]

I too am curious about these functions. Why, with them, you could have more than three arguments to a script, for instance.

[Demolisher]

They seem self explanatory, but I don't know the variable order, making them useless atm.

[CodeImp]

A guess here: GetLineUDMFInt(lineid, fieldname)
Example: GetLineUDMFInt(14, s:"maxbrightness")
Where "maxbrightness" is ofcourse some custom UDMF field you added to that line and it has to be of Integer type, or use the other functions to read the value

[NeuralStunner]

These could come in very handy.

[carlcyber]

Code: Select all

GetLineUDMFInt (int lineid, str fieldname);
GetLineUDMFFixed (int lineid, str fieldname);
GetThingUDMFInt // Not implemented. guess: (int tid, str fieldname)
GetThingUDMFFixed // Not implemented. guess: (int tid, str fieldname)
GetSectorUDMFInt (int tag, str fieldname);
GetSectorUDMFFixed (int tag, str fieldname);
GetSideUDMFInt (int lineid, int side, str fieldname);
GetSideUDMFFixed (int lineid, int side, str fieldname);  

lineid = 0 represents the calling line.

[Caligari87]

Can anyone add these to the Wiki? I'd try, but I tend to botch stuff like that horribly.