Opbys and Triggers going click

[Joramun]

1 - Added opby_party_carry opby
2 - Added bool "release" exvar for object hiding/sconces
3 - Added bool "air" and "air_only" exvar for opby flying objects

1 - EDIT :
Triggers are either looking for a specific type (thing, monster or party, as specified by opby_(type) = true ),
Or a specific archetype (in which case it is either on the tile or in the inventory) specified by opby = "archetype" or opby = { archetypes }
in which case i would implement : opby_party_carry, opby_monster_carry, opby_inside_thing (for chests etc. ) as BOOLEANS
( true by default for triggers ! ), and if true just look for the opby list in the inventory

2 - The sconce in the test dungeon doesn't work anymore : sconce_full should have release = true by default

3 - Is there also a way to differenciate flying monsters from the rest ?
In DM they didn't trigger plates. But some triggers or teleporters will
need to catch them. [only, or inclusively]
EDIT : Yes, there is : "hover = true"

EDIT :

4 - Added "default_silent" property to triggers

4 - Could it be used by the teleporter function, too ? (i added that in my own code)

[Joramun]

4 - Added "default_silent" property to triggers

Somehow the way it is done force to set sound = snd.click for all noisy triggers :

Code: Select all

if (not exvar[id].silent) then
	if (exvar[id].sound) then
		local_sound(id, exvar[id].sound)
	elseif (not self.default_silent) then
		local_sound(id, snd.click)
	end
end

The problem is : silent = nil and false is the same...
I can set RTSB to put silent = true for all (silent) triggers and teleporters by default, and therefore default_silent is unecessary.

[Sophia]

Triggers are either looking for a specific type (thing, monster or party, as specified by opby_(type) = true ),
Or a specific archetype (in which case it is either on the tile or in the inventory) specified by opby = "archetype" or opby = { archetypes }
in which case i would implement : opby_party_carry, opby_monster_carry, opby_inside_thing (for chests etc. ) as BOOLEANS
( true by default for triggers ! ), and if true just look for the opby list in the inventory

This is more consistent. I'll change the behavior.

The sconce in the test dungeon doesn't work anymore : sconce_full should have release = true by default

Oops!

Is there also a way to differenciate flying monsters from the rest ?...
EDIT : Yes, there is : "hover = true"

I'll make triggers check hover, too.

Could [default_silent] be used by the teleporter function, too ? (i added that in my own code)

Yes, I'll add that too.
Keep in mind that default_silent is a property of archs, though, not an exvar, so it might not be useful with the default teleporter.
I'll add a check for a "silent" exvar, too.

The problem is : silent = nil and false is the same...
I can set RTSB to put silent = true for all (silent) triggers and teleporters by default, and therefore default_silent is unecessary.

The problem is that RTC and DSB do things in a different way and RTSB is doing a direct translation.
In RTC, pads are just ornamentation and there is one floor trigger type that actually does all the work. In DSB, on the other hand, pads can be triggers too. What I did was made "default_silent=true" for the invisible triggers, but not for the pads. Thus, the default configuration is that if you can see it, you can hear it, and if you can't see it, you can't hear it either.
To me this was perfectly logical and it saved a lot of troublesome setting of exvars... for a dungeon made from scratch for DSB.
The situation in a converted dungeon is a little more complicated. However, dungeon_translate has a little section of code that will check for both a pad without exvars and a trigger with exvars on the same tile, and if it finds both, it will assign the trigger's exvars to the pad and delete the trigger.
This makes the pad behave as DSB expects it to, and the clicking should be completely sensible.
In short, you don't have to do/change anything, dungeon_translate will create the correct behavior in almost all cases.