The switch of a button creating mood swings.

intruder on 16/1/2010 at 16:26

Emit_Online and Emit_Offline are 2 new projectile-archetypes, derived from the standard broadhead, equipped with the new Sources "Bot_Online" and "Bot_Offline".

Beauty-Man on 16/1/2010 at 16:55

That was definitely the problem. . .(took about 12 tries) :o

You're about the only one with patience enough haha.

I appreciate it definitely!

Now to have many many robots with that same property. . :sweat:

intruder on 16/1/2010 at 17:30

Create a new robot-archetype! Just derive your new class from an existing one and add the receptron, save the gamesys and you're done. So you only have to do the work once, not once per AI you want to place in your mission.

If all robots in your mission should be linked to that "device", it's getting even easier:
Add the receptron to the Robot-archetype (-1783), save the gamesys and you're done :D

Beauty-Man on 16/1/2010 at 17:37

you're right ha I'll use that procedure. Thanks again because this had me beyond stumped yet more to come. . :eww:

Ottoj55 on 16/1/2010 at 22:53

you want to change the state of the robot via a "button" according to the question, right? easiest way is nvrelaytrap, use this script to send a stim to the robot or robots, the robots have the receptron to the stim to then enact the effect. its all described in the documentation for the scripts. no idea what all this emitter, and custom gamesys talk is about, way easier way to do this.

intruder on 16/1/2010 at 23:34

The custom gamesys is needed for the changed archetype, since he doesn't want to add the receptron "by hand" to each single robot in his mission. And without custom gamesys, there is no custom stimuli too.

Ottoj55 on 17/1/2010 at 00:50

that makes sense, but only if there are a lot of robots. you don't need to link them all from the trap, it can control classes of objects, the "wireless" switches yandros uses for instance.

john9818a on 17/1/2010 at 01:59

When you have a metaproperty added to an AI by using a conversation, you may also have to put a short delay in the next step. I had mine set at 50 ms. Also make sure that the concrete object does not have the Team property added to it

There is something that needs to be taken into consideration. If the bot is already attacking you, changing the team of that bot won't necessarily stop it from attacking right away. It may appear that it is still attacking. If the attacking continues for longer than one or two seconds, then use the delay mentioned above.

Beauty-Man on 18/1/2010 at 06:13

Thanks for the suggestions OttoJ and John.

Although the layout had worked out at first, I continued building and so happened to move the bot into a different room. I tried to fire the switch again and back to disobeying the command. I made sure everything is linked up correctly. Yes, everything is still in the same place as far as links. However, the bot doesn't listen to the metaproperty any longer.

I'm going to have to test out the other solutions to see if they hold.

intruder on 18/1/2010 at 09:46

Perhaps the radius for the source is too small.
I've set the radius to 400 DU, just for testing purpose (on the projectile that gets fired by the emitter).
You could try to increase the radius, so that it covers your whole mission and see if it works again.