Jump to content

have no idea about triggers


dragonforger17

Recommended Posts

Or go with gmud, its very simple, even I can use it! I only use two for right now, and its for leveling, in pk, I think they can be troublesome in pk, or maybe its just because I have bad triggers set up, on gmud for instance, I have it set for when my client sees that I've been disarmed, It auto types get 1.; wield 1. which i've had trouble with if some weapons are no drop, I've ended up picking up an ear before and wearing it instead of wielding my weapon again heh, but the other i use is for when my char's proficeny goes up, it auto saves, I disable them if I'm going to go into a pk situation though. Aliases on the other hand I find very useful, although I've just started using them a couple of months ago, after reading I think it was L-A's guide to survival or something like that. basically an alias will stack commands for you, like i think L-A's example which I have found very useful was for recalling, keep them all in your sack, and when you type recall, the client will (for mine anyway) enters: open sack;get recall sack;quaff recall;close sack

Link to comment
Share on other sites

I have one for disarm, shield disarm. I have them for highlighting when key spells drop on me and my opponent. I have ones that highlight tells so they're different colors. I have certain mobs show up in color. I have one that tells me my proficiency at a skill when I get better. I have ones that make hunger and thirst show up red. All kinds of stuff. They're cool.

Link to comment
Share on other sites

Triggers are functions that your mud client can automatically perform for you when it sees certain lines of text pop up in the mud window. They can do things like automatically perform an action, make text a bold colour so you can notice it better, or make noises to alert you when certain things happen.

A common example is a disarm trigger. People can set their mud client to react to the phrase 'disarms you and sends your weapon flying' and makes the mud client automatically perform 'get weapon wield weapon'.

Each mud client has it's own way of doing it, I'm not sure how yours works, but that's what triggers do basically ..

Link to comment
Share on other sites

Triggers to actually perform actions for you while you're running around are definately the devil. However, triggers that make sounds and colorize affects that you might not pick up so easily are quite nice.

For instance when I'm disarmed, the line gets colored white and my computer beeps at me. When I flashfire the line that says the mobs/players were blinded by the flashfire is colored blue, the ones that avoided the glare are colored green so I know what I missed alot faster than if I was trying to scan through the text normally. Also when I my spells drop I have those lines colored so that I don't miss them.

And if you client supports aliases I would learn to use those as well. They really make pk less about how fast and accurate you can type, and more about how you react to whats happening.

Link to comment
Share on other sites

If you use ZMud I can certainly help you with triggers. As for whether triggers are good or not, you should definitely setup triggers for things like syntax colouring or beeping when you get disarmed or spell dropping etc. As for using triggers in pk at the beginning you will die A LOT because of crappy triggers, but as you get better at it you will find triggers really do help pk.

Link to comment
Share on other sites

OK - if everyone else hasn't made it clear, triggers look for certain text them enters a command.

The obvious use you probably think of is:

Text: L-A walks in.

Command: bash L-A

Triggers are not the devil - IMHO if you are playing without you are giving away an edge to player (like myself) who use triggers.

Just be CAREFUL with them, if you set the one above you might be fighting a mob, see L-A walk in and you will bash him. Of course, when L-A is trying to run away you can see him try to run past you and lag him to death.

There is good and bad in triggers so be careful.

If you wish to really use triggers, I'd advise usig GMud for a month or two. Its trigger system if very basic. Once you understand the how and why upgrade to JMC (Iave MUD client). It is VASTLY more powerful - but it isn't for newbies either. Most of its functionality comes from teh command line so if you are used to GUI's you will have a learning curve in front of you. I play with it now and I wouldn't use anything else.

L-A

PS - in FL 'life support' (ie triggers that eat and drink for you while you train so you can walk away from your PC etc) triggers are illegal by word of the Imms. I've seen people slain for them so do not set them and walk off unless you want something bad to happen to your character. Kiss your cabal/quest race/class chances goodbye if you get caught doing this as well.

Link to comment
Share on other sites

Eh.. maybe you kids here are retarded, but triggers are useful for multiple things in a mud (that's why all the popular clients have them). Some of the things that they can do include

- program a localized database of ids

- color events that you think are important

- add color and variety to your screen, instead of generic blobs of green text

- autoinitiate on a target when you have the upperhand

- ticktimers

- autologging

- and more.

One thing to note is that triggers, like everything else that you program, should be used securely. You should use general reg ex rules when using them. So if you want to recast sanctuary

Instead of using

Pattern: The white aura around your body fades.

Command: c 'sanctuary'

use

Pattern: The white aura around your body fades.$

Command: c 'sanctuary'

The $ means end of line so it prevents people from spamming you with

Gimp tells you 'The white aura around your body fades.' x 10

c 'sanctuary' x 10.

Here's a basic auto-initiator script with aliasing to enable and disable it (though it still has bugs).

#CLASS {tracker}

#TRIGGER {@mytarget walks in.} {@attack @mytarget}

#TRIGGER {@mytarget limps in.} {@attack @mytarget}

#TRIGGER {@mytarget crawls in.} {@attack @mytarget}

#TRIGGER {@mytarget gallops in.} {@attack @mytarget}

#TRIGGER {@mytarget flies in.} {@attack @mytarget}

#TRIGGER {@mytarget is here.} {@attack @mytarget}

#TRIGGER {@mytarget has fled!} {#ab}

#COND {@mytarget (%w) (%w).} {%2;@attack @mytarget}

#CLASS 0

#alias yestrack {#t+ tracker;#say Tracking Started.}

#alias notrack {#t- tracker;#say End Tracking.}

Anyway ... that's my $0.02 on triggers and scripting. If you really want, you can send me aim messages at shwang1386.

Link to comment
Share on other sites

Eh.. maybe you kids here are retarded, but triggers are useful for multiple things in a mud (that's why all the popular clients have them). Some of the things that they can do include

Question.... why is this prick still here and able to post on our forum? Not one of his whopping five posts has had anything pleasant to say about FL or add to our community.

Link to comment
Share on other sites

Lailanni, no hurting the nerds here. You have to remember that much of our playerbase is not used to contact with the fairer sex, and get excited when they think of a girl playing video games.

P.S. I still think triggers, especially autochasing triggers like the one posted above, are for the weak. They're automating your character, not playing him.

Link to comment
Share on other sites

i strongly advise against tracking triggers. It may help. BUT it definately can get you killed. If you're hurt and being chased' date=' the last thing you want to do is initiate battle (especially against folks with counter).[/quote']

especially when the one your fighitng is a blademaster with mastered twin AND they figure out your using the tracking trigger.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...