To answer to your questions : yes, I'm going to add a trigger to detect if a player is following/targeting the bot. I'm developing a class which manage all units/players around the bot and store them. It will be useful to determine who killed the bot when he dies too. I think also add an option to emit a beep when a trigger fires (for example a death, a stuck, etc.). It would be useful for profile developers who traced some paths and want to test them. Maybe these people want to do others tasks during the bot is testing their profile, but they need to know when the bot has a problem. With this option, they will be warned when a problem occurs without staying behind their screen. I don't think it's my work to do this. See with the author of BuddyCenter instead. Again, thanks for your precious feedbacks.
Awesome plugin, only seems to be missing one feature... Could you implement a feature that checks all chat channels (i.e. /s /y /battleground /1 /2 ) for a keyword (such as character name, or user-defined keyword) and once criteria are met, exit? So very similar to the number of whispers received, except it's not looking for whispers and looks for keywords instead? Thanks very much mate, love your work.
@gk0r : Glad you appreciate my work. A channel scanner seems be a good feature, but I don't know when I'm going to implement it in LogMeOut!. Anyway, I add your idea to the todo list. I think add a new feature that checks if there is a new version available of the plugin too. With this, you will be always informed of new releases.
Well it would show on buddycenter if u somehow could make the events (followed by player x, stuck ,...) get whispered to urself. this way the other plugins will send that whisper to the phone. Hope u can to that pretty plz
but i think whispering to the own char with such information is dangerous. if you get marked in any way bliz will check your chat.
I also think that pass this kind of information by whispering is not a proper method to do that Actually, I don't know how I can send notifications to BuddyCenter properly. So I keep in mind your idea but I don't know if it is possible.
Blizz can check all your whispes/channels at any time When you create a new Battle.Net account, you must accept their chat agreement that specify you agree they can read your messages to eventually detect potential violations of their terms of use (cf https://eu.battle.net/account/creation/tos.html). I don't want to take the risk they can spot all the bots using LogMeOut! just by a chat scanning.
logmeout cant be the cause. Its only job is to log you out. Something else is. Maybe some idiot player saw you doing something bot like. Maybe you bot got stuck, and that alone will get you reported. But to be banned on first report, you must of have done something else before to get banned.
Never mind about this guy... With a name like Darkevin, it's one of my friends who says me Hello in his way x) He should reroll a troll.
How about, if a Quest isnt possible to Turn in, and sometimes the Toon is staying there and always want to turn it back in. Possible to implement something that say if x times not turn in logout? btw. the Whisper logout... is a GM Whisper the same? or is there such another routine how GM talk to a Toon?
I think it's a good trigger to implement too LogMeOut! can count a GM whisp, but actually, it cannot see the difference between a player whisp and a GM whisp. In my opinion, if you get a whisp of a GM, he already knows what you are doing. So, I don't know if it's useful to add a trigger about that.
Good news today ! I'm proud to present you the version 1.1 of LogMeOut!. With this new version, two new triggers have been added. You now have the possibility to detect if a player follows/targets you and you can ajust minutes before logout for these. You also have the possibility to add a beep when triggers fire. The plugin can ignore to count the number of death during a battleground when you active the trigger for the death. About death... The plugin will show who killed and where the bot was killed into the Log console. I implemented an updater, so in the future, you will be informed when there will be a new release directly into the Log console. Some of you had some troubles when the bot was stucked on a fly mount. This problem is solved by adding a timeout. And finally... the new killer feature... Each time honorBuddy logs out by LogMeOut!, the reason of this logging out will be shown during the next starting in the Log console ! ---- You can find all downlods links and patchnote in the first/second post of this topic. Here is a screenshot of the new interface of the bot : Don't forget it motivates me a lot if you click on the star button at the bottom of this post to give +rep to this project. ---- What's next ? I will add a whitelist for the two new triggers and I will implement a channel scanner to detect some specific keywords. I will eventually add a trigger Quit on Loot a specific item too. Don't hesitate to post your comments and feedbacks !