[chaditParticipant]

I leverage the scenario engine like crazy, every 60 mins I switch zones and do something else. I also created ACT alerts for some of the GM messages, almost all the youtube videos start with “Greetings <Your CharacterName>) that way I can do work and let ACT use text to speech to alert me.

Lately housing has probably been the biggest way bots have been caught, the frustration of trying to get a house has caused a renew hatred for bots. If anyone suspects you, they probably report it. I wouldn’t put it past the RMT botters to report others in order to try and lower competition.

[chaditParticipant]

And this person is the example of why new features are slow to be released

[chaditParticipant]

Get Blue mage and self destruct. Keep an eye out in party finder there have been groups doing that in Kugane since the reddit post went out a week ago.

1. Lamp post need one person, blue mage runs up to the lamp, self destructs, get rezzed, done
2. Top of the tower is harder takes 4 people that can rez, blue mage self destructs at each level gets rezzed to the next.

I have characters on a variety of servers and someone is almost always doing the lamp post, at least once a day a group is doing the tower. on large servers this is probably more common.

• This reply was modified 5 years, 2 months ago by  chadit.

[chaditParticipant]

sorry if these have already been asked,

would it be possible to add a finally style block to scenarios. It could work similar to try/catch/finally, a step that is run no matter success/failure. What I would like to use it for, if a scenario finishes successfully and or the kill switch is triggered I could have a finally step that ports me to my house and allows me to AFK out in there instead of out in the open.

also are there plans to expand the functions, maybe allow for someone to create custom functions of their own. using my example above, allot of my scenarios end with going back to my house, would be nice to add that to a function and then in my step I would just do goHome().

[chaditParticipant]

I think there is a rogue thread in miqobot_v1.3.17_beta.exe, if I open it, use it, click the X to close out of the application. Reopen it later, it gives me the errors that only one miqobot can be running at a time. miqobot_v1.3.16_beta.exe can be opened right after that without any issues. to clear the error, I have to reboot the PC. As far I can see if the task manager there is no miqobot process running unless it is using another name. This might also be what is causing Anti-viruses to go nuts.

[Author]

Posts