Jump to content

Recommended Posts

Posted

I come to suggest something that I think is quite useful.

Instead of using the name of the player in command "#", it was possible to use char_id.

Some players have nicknames with space and stuff, it makes can not perform such an operation.

Posted

It can be done, but not by char id but by account id. Some players use some weird symbols and it account ids can be easily acquired when using a gm account.

What you guys prefer:

#command account_id or charname

Or

#command @account_id

#command charname

Posted

the reason for topic starter to bring this up, its because certain server, player are able to put "symbols" in their char name and some country keyboard are unable to key in these symbols which result the command cant work for them.

i would prefer this

#command account_id or charname

Posted

#command account_id or charname

Or

#command @account_id

#command charname

What should the command do, when there is for example a char named "22356" or "@22356" and also an account with the id "22356"?

  • Upvote 1
Posted

#command account_id or charname

Or

#command @account_id

#command charname

What should the command do, when there is for example a char named "22356" or "@22356" and also an account with the id "22356"?

That's a nice question, the only solution that I see for that is to create another symbol for "account id commands", like $item 2000000 501.

Posted

Another possibility would be to force #commands to use " around the charname, even when there is no space in the name.

So "..." would mean charname, no " around it would mean account_id.

But it could confuse peaple who are used to the old behaviour :S

And another question that came to my mind:

Do the the current #commands work for chars with a " and a space in their name? (for example: some "random\"name)

How would you write it? Escape it? If it also has a \ in the name, escape also the escape char?

Or does it break for such a name?

Posted

I don't see what's the problem with this, if you're having problems because of your keyboard or whatever, then don't allow those symbols to be used in char names. Easy as that, this is not really necessary at all.

And if you're not the server owner to make that call, then, figure it out, that's why you were "chosen" to be part of the Staff. So you can "work" it out.

Posted

Agreed, I can potentially see the use of allowing a character ID property in the # command, but implementing a new command altogether seems a bit of overkill. It'd be more efficient to allow integers (such as #item 123456 501 1) in-place of character IDs, and when the character has a name of explicitly numeric values, detect whether the entered integer has quotation marks around it.

IE: character named 1234, #item 1234 501 1 would fail, however #item "1234" 501 1 would work.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...