Binding

Kaimetsu · #1 08-25-2002, 08:21 AM

Why can't every command be used in binds as in Quake 3 or whatever? Why can't I say "/bind 1 tag add class" or something like that? Don't tell me it's a scripting problem because it'd be trivially easy to adapt the current system to allow it.

MasterNuke · #2 08-25-2002, 08:34 AM

because your missing something... try: /bind 1 send tag add class

Kaimetsu · #3 08-25-2002, 08:50 AM

That works? But the send shouldn't be necessary - surely it should be the default.

Er1c · #4 08-25-2002, 11:23 AM

Quote:

Originally posted by Kaimetsu
That works? But the send shouldn't be necessary - surely it should be the default.

Trying to find something wrong with it? lol...

When you want to send a command, you need to use the SEND action...

BTW, I added three more keys to bind... 'w', 'e', and 'r' (mostly because I need some more keys for chat commands

)

Kaimetsu · #5 08-25-2002, 01:16 PM

Quote:

Originally posted by Er1c
Trying to find something wrong with it? lol...

When you want to send a command, you need to use the SEND action...

BTW, I added three more keys to bind... 'w', 'e', and 'r' (mostly because I need some more keys for chat commands )

I'm just confused by it. If send interprets a command, then why have the others? Why have the spell and use stuff when you could just make those into normal commands and have send being an implied default?

FFusion · #6 08-25-2002, 06:39 PM

Quote:

Originally posted by Kaimetsu

I'm just confused by it. If send interprets a command, then why have the others? Why have the spell and use stuff when you could just make those into normal commands and have send being an implied default?

Well if someone wanted to say diamond blade and they binded it what would it do? Say 'diamond blade' or equip the diamond blade? This is just an example because I do't know anyone who would want to say diamond blade.

Er1c · #7 08-25-2002, 11:26 PM

Quote:

Originally posted by Kaimetsu

I'm just confused by it. If send interprets a command, then why have the others? Why have the spell and use stuff when you could just make those into normal commands and have send being an implied default?

oh, I see what you mean... send is used to actually send a command to the mudlib, while the other ones do other things before sending any commands.... so I just separated them
In NPCs there's no way to know which commands are already built in, so it's better to just have a separate command for all of them: bind

konidias · #8 08-26-2002, 12:37 AM

Good ol' Kaimetsu... picking apart one script at a time...

Kaimetsu · #9 08-26-2002, 06:03 AM

Quote:

Originally posted by Er1c
oh, I see what you mean... send is used to actually send a command to the mudlib, while the other ones do other things before sending any commands.... so I just separated them
In NPCs there's no way to know which commands are already built in, so it's better to just have a separate command for all of them: bind

Hmm. It'd seem better to establish some kind of uniformity. I just got online to check and it seems like the normal text commands don't include anything to equip items. This is all a little icky. A much nicer system would include the use command in the normal stuff so that I could just bind that instead of using a special bind-only command. Basically I'm saying that to equip an item we should be able to either:

1) type "/use bronze plate mail" in the chat box at the bottom of the screen.
2) Use "/bind 1 use bronze plate mail" and then press 1.

Both would call the same code. And to cast spells, we should be able to do:

1) "/cast burning hands"
2) "/bind 1 cast burning hands"

See the point I'm making? I know it's probably out of your hands, because Unixmad writes all the mudlib stuff? But this kind of standardised form would be greatly beneficial.