triggering touch via collision?

before you say it can't be done, I've now seen 2 objects that do this, but the one i'm most interested in triggers llMapDestination through a collision...

anyone know this trick? the applications are endless, and it's obviously a hack, possibly using volume detect and or pass touches/collisions, but I've yet to work out how it's done. any help would be appreciated, IMs/PM's are most welcome.

wouldn't have believed it if I hadn't seen it in action.

I would like an explanation of this too. I've seen stargate-type devices utilize this technique...

there seems to be some associated jira's about he revers case, ie touches triggering collisions, and state changes not flushing touch_start events... neither helpful so far

Someone's gotta ask, do you mean like the stargate example? Where you touch first, and it enters a loop waiting for you to collide before it calls llMapDestination? In that example I assume it uses llGetObjectDesc or something to receive a message while looping in the touch event

hmm, that would work in that particular case, and I can't believe I forgot that trick considering it's one I used in my single click from an inventory landmark example... but I've seen another one that triggers a touch based on someone elses touching the object first, and the second person getting the touch event functionality.

I did find reference to a hack that would involve knowing the internal names of events in the compiler, but I suspect that will be repaired.

PS. I've seen that stargate system before, but I believe it also accepts chat input, so I dunno if it's using a check loop in the touch handler or not.

ok too tired to mess with this anymore today, good luck to anyone trying to figure it out

not the same thing I know but by using the collision event or the collision_start event (the latter being more accurate unless you want to deal with a "while colliding" situation) and really you can trigger the same thing as a touch easily. An example:

a()
    {
     llOwnerSay("The answer to life, the universe, and everything is 42");   
    }

default
{
    state_entry()
    {
        llOwnerSay("Script activated");
    }

    touch_start(integer total_number)
    {
        a();
    }
    
    collision_start(integer total_number)
    {
        a();   
    }
}

Darling Brody also uses a hack to get around this for her "entirely legitimate" map spammer device so there are ways around this. Unfortunately after doing a bit of testing on all the tricks I know I couldn't figure this one out without llmapdestination choking on the fact that you're not using a touch event to trigger it but this is a bit of a puzzler and I like a challenge so I'll try to keep testing too I guess.

In the case of the stargates you need to be wearing a second object for it to work without touching.

This from the 'Open Stargate Network' site:


It's actually quite easy.
The object you walk into whispers something, and the object you are wearing opens the map upon hearing that something.

That's one way of doing it.

Perhaps this fascinating article I found about llMapDestination will be enlightening.

http://www.slbuilding.com/slkeywords/llMapDestination_(1..htm

Perhaps not.

Ah yes, that explains it all

that almost made my head hurt lol

It didn't compile, what did I do wrong?

Yeah, I've done one with a helping attachment before. Unsatisfying without the right social context, but it works well. Heh.

well the gate example I tested required a touch to dial, so most likely using the check loop (still feel stupid about that one, since I came up with it ages back), but there are a few other items using this... I still think it's gotta be related to the 3 jira's I mentioned... but I can't parse it yet. I may give up on this due to potential for abuse (not that the cat isn't already out of the bag)

Just in case anybody else is confused by this thread, as I was until I hit up the wiki, llMapDestination only works in a touch event or from a script in an attached object..

... and yet somehow people are triggering it w/o a touch... so there's a hack to do it, but I don't have it figured out :hrug::

Anywhere to experience this?

AND without any kind of attachment? You sure?

What are the 3 jira issues?

state changes retriggering touch_start event (ie if you have a state change in a touch start event, touch start will also trigger in the new state from the same touch)

touches triggering collisions in volume detect objects (apparently even if it's an unattached object that intersects the volume detect that is being touched)

and best for last a lil number reported by strife about how the compiler treats events as functions, possibly allowing a correctly named user function to replace the functionality of the same internally named event, allowing it to possibly be triggered outside it's scope.(translation: write a function to replace an event and trigger it from anywhere... possibly)

I can't remember the jira numbers offhand, but all three were active at browse time. the last looked promising, but I expect it'd be repaired for what should be obvious reasons.

as for good examples, I hesitate to say, because of the potential to get a certain person in possible trouble for something quasi legit... but I suppose the map spammer (which I havent actually seen at work) might be a good example... I also saw a collision sitter in action (thought it could be used wonderfully for telepads) but didn't manage to get a source or info.

I just had an idea... I'm not sure if it would work, but what if a jump tag was being used in the collision event to jump to the touch_start event? I don't usually use jumps, so I'm not sure if they need to be in the same event/function... I'll try it as soon as I can log in.

pretty sure they are compiled per event, but i'll test that when I get a moment