Slit
Dec 29 2003, 07:29 PM
This script is design to detect someone attacking a buff bot, pause the buff bot, defend the buff bot, and re-enable the bot after killing the attacker.
Granted this is designed for use on Darktide. It is always a work in progress, adding some features. Hopefully l will get some ideas from everyone here.
New version is working much smoother.
DaMOB
Dec 29 2003, 09:18 PM
Be careful if this is simply a sentinel/guard program for when your away you can get banned for UCM. Simply put I was going to do that but its against the CoC.
Slit
Dec 29 2003, 11:47 PM
It is not designed for UCM. It is designed for protecting a buff bot. We have had a few jerks sneak up in middle of night and attack the buff bots. This simple is a way to respond to them. So the buff bots stay online for the rest of the guild members to use. Note the house boot feature, if it is happen inside your house aka monarch char is botting. Then no combat is need, just boots the attacking char safely out of the house.
DaMOB
Dec 30 2003, 04:19 AM
I know what your saying and I was going to write one to protect my buff bot but Turbine would ban me for UCM. See if any bot lifts a finger to attack anything, even in self defense, and its owner is not at the keyboard that is considered, by Turbine, a UCM.
I am just warning about it usage so don't kill the messenger.

Might want to add a disclaimer about its usage because Turbine might ban the bot using it. Its stupid granted because we had some idiot lure monsters on our bots and got my bot and 2 others killed at the mansion but had my bot even tried to defend itself I could have been banned. Would it happen? Maybe if the person turns it in and then shows what happens so I scrapped my idea.
Slit
Dec 30 2003, 11:29 PM
Actually they way UCm has been inforced, this should never result in a ban. They have made if clear the bot macro is fine. The program is not a hunting bot. And will not go out seeking things to kill for exp. Not trying to shot the messager etc, just pointing out that there is not an issue imho.
However. All scripts should be run with the user being aware. Note this is the beta release. I wlil be update the file as I add some features as requested by the other guild mates that run bots.
Thanks
lomega
Jan 21 2004, 05:33 PM
just wanted to correct you on one thing: if it is involved in combat in ANY way, then you *could* be banned. sure, you may not mean for this to be a "hunting' script, doesnt mean it wouldnt classify as a UCM according to current enforcement
by that, i mean if you earn ANY exp from:
- casting a combat spell (debuf, vuln, war, drain...)
- evading/resisting a target
- or (espesially) killing something/anything
***while the player is not attending the account***
could result in a UCM ban.
you may want to put in a logout 'timer' or move the bot to a safer place, like through the mansion's portal, or something instead? just suggestions tho
DaMOB
Jan 22 2004, 05:11 AM
Now that Turbine owns the whole candle factory (more than a ball of wax) they have said they will VERY STRICTLY enforce the CoC and much more than M$ ever did. Tons more admins and general workers so banning will come quickly. Now if they do as they have said the game is about to lose 20-25% with perma bans and Turbine has also said once they perma ban you then you can kiss the baby (para phrased).
AC is now moving in a direction it should have 3 years ago at the minimum in its enforcement but who knows they may also be farting in the wind.
Ahk
Jan 23 2004, 04:13 AM
*shouts* doorknob!
stabaho
Apr 17 2004, 04:33 PM
Iam glad this is a UCM debate, and not a macro development chat.
Personally my friend wrote a plugin that did the @house boot feature you were talking about. But you didnt have to be the monarch, just in your own house. And it made a shit list of people who attacked the bot, and if they were detected coming threw the basement portal, they would get booted again.
Slit
May 9 2004, 05:14 AM
New version that works much smoother.
Also relies on a new tool Crash Helper. To reload AC from those nasty crashes.
Later
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.