Archive: 5 posts

---

I have created an enemy sackbot that is supposed to be in ACT mode like he is typing at a computer, then sense the player at a certain distance, and switch to FOLLOW behavior chip, follow the player, and when close enough perform a slap ACT. I am nearly positive I have the wiring all correct for this. I have done the research and tested other bots with similar actions, but this doesn't seem to be working. The problem is he stays in the very first ACT mode (looking like he is typing), but doesn't switch to FOLLOW when the player is in range of awareness. I am using the sackbot circuit board with all the logic on that for initial ACT behavior - then the the FOLLOW behavior and slap are placed in chips on that sackbot board. everything is wired up so that no two behaviors are triggered at once. He is supposed to ACT by default, FOLLOW player in range and slaps (ACT) when next to player. That's it. I am NOT using the SEQUENCERS method because i wasn't sure if I could keep him in one action (like following) with using sequencers. Anyone know why isn't the ACTING behavior switching over to the FOLLOW behavior when I checked logic and the ACTING stops when player is in range and FOLLOW behavior is lit up...but the bot just doesn't do it.

2011-02-14 02:00:00 Author: ghostingalong Posts: 17

---

On your sackbot, put two player sensors at the distance your wants to follow and slap. Keep the follow and slap on the main board. Wire the player sensors to their desired action. Should work.

2011-02-14 02:39:00 Author: RSQViper Posts: 302

---

yeah, i've done that (except for keeping them on the main board). i'll have to put them there and see if it changes it, but I did drag the behavior chip for FOLLOW onto the main board and didn't change anything. i have it wired so that one behavior deactivates the other and that way no two behaviors are activated at one time. i seriously haven't been able to figure out why this isn't working. i may need to take a picture and put it on here or draw up a diagram. because as far as i can tell it should work.

2011-02-14 03:12:00 Author: ghostingalong Posts: 17

---

try an inverted not gate between typing executor and the actual act behavior chip, so that when its disengaged he'll go back to typing.

2011-02-14 03:43:00 Author: reiko57 Posts: 115

---

Yeah, I think a picture would be helpful. I have never wired anything to deactivate another, though and have had success. I wonder if that is the problem.

2011-02-14 03:43:00 Author: RSQViper Posts: 302

Posts: 1077139    Threads: 69970    Members: 9661    Archive-Date: 2019-01-19

Aus dem Archiv wurden alle persönlichen Daten wie Name, Anschrift, Email etc. - aber auch sämtliche Inhalte wie z.B. persönliche Nachrichten - entfernt.
Die Nutzung dieser Webseite erfolgt ohne Speicherung personenbezogener Daten. Es werden keinerlei Cookies, Logs, 3rd-Party-Plugins etc. verwendet.