Shamarah2007-12-03 21:59:09
QUOTE(Arak @ Dec 3 2007, 04:58 PM) 462010
Here's another good tactic for you to try against dreamweaving druids:
Force embed hallucination Shamarah is great!
It raises morale and might even prevent them from embedding something else (though that last part probably isn't right)
Force
It raises morale and might even prevent them from embedding something else (though that last part probably isn't right)
There are considerably more useful things that you can force if you can manage to catch them on eq.
Xavius2007-12-04 00:03:39
Like BURY DREAMCATCHER, BURY FETISH, or BURY CUDGEL for runists.
Ground elevation stops murder, which is handy. Not swarm. Flying stops swarm.
Ground elevation stops murder, which is handy. Not swarm. Flying stops swarm.
Krellan2007-12-04 03:01:54
you can't bury through selfishness anymore though. My newbie thieving days are over 
Arak2007-12-04 05:14:35
Does that mean that it won't take up balance either? (Referring to being forced to bury while selfish)
Malarious2007-12-04 05:21:36
QUOTE(Xenthos @ Dec 3 2007, 02:51 PM) 461980
It's sure not ineffective, but you can just as easily do a #say instead if you're afraid of it being abused. Still, it's not hard to add in a check or two-- the only real issue would be against a telepath who can force and illusion. Further, that's why you don't do something that's easily noticeable-- they're not going to tell the difference between you typing nstat or having a trigger do it (note: if they're wasting 1s in Choke to make you waste 1s, it's not really going to get them far).
Another alternative would be to "save" the last command you entered if in Choke, and on that force message, just resend it. At most, 1s lost. At worst, a fraction of a second. And yes, it gives the "you are forced to do something" message and then gives you 1s to stop that force.
Finally, to Malarious: No, you'd just put another } at the end of it, after the first one. It's not meant to be real code since I didn't actually go get the dominate/force messages.
Another alternative would be to "save" the last command you entered if in Choke, and on that force message, just resend it. At most, 1s lost. At worst, a fraction of a second. And yes, it gives the "you are forced to do something" message and then gives you 1s to stop that force.
Finally, to Malarious: No, you'd just put another } at the end of it, after the first one. It's not meant to be real code since I didn't actually go get the dominate/force messages.
So he actually meant...
#trigger {forcemessage} {#if (@choke) {#send nstat}} if I have it right.. for those who are curious
Thought you were namign the trigger forcemessage
Krellan2007-12-04 05:43:04
QUOTE(Arak @ Dec 3 2007, 11:14 PM) 462165
Does that mean that it won't take up balance either? (Referring to being forced to bury while selfish)
yeah, it'll be like a check, like you're too selfish to give that way message. or that's what you should get anyways.
