Yum Posted August 18, 2012 Group: Members Topic Count: 13 Topics Per Day: 0.00 Content Count: 27 Reputation: 3 Joined: 02/17/12 Last Seen: December 15, 2014 Share Posted August 18, 2012 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. Quote Link to comment Share on other sites More sharing options...
EvilPuncker Posted August 18, 2012 Group: Members Topic Count: 19 Topics Per Day: 0.00 Content Count: 713 Reputation: 71 Joined: 11/08/11 Last Seen: December 25, 2024 Share Posted August 18, 2012 just use quotes for spaced names o.O 1 Quote Link to comment Share on other sites More sharing options...
GreenBox Posted August 18, 2012 Group: Members Topic Count: 9 Topics Per Day: 0.00 Content Count: 303 Reputation: 101 Joined: 11/13/11 Last Seen: October 11, 2023 Share Posted August 18, 2012 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 Quote Link to comment Share on other sites More sharing options...
clydelion Posted August 18, 2012 Group: Members Topic Count: 17 Topics Per Day: 0.00 Content Count: 754 Reputation: 186 Joined: 05/22/12 Last Seen: October 15, 2022 Share Posted August 18, 2012 Not really necessary though. For example the character's name is: Renji Abarai the proper command would be: #item "Renji Abarai" 501 1 Quote Link to comment Share on other sites More sharing options...
Emistry Posted August 18, 2012 Group: Forum Moderator Topic Count: 93 Topics Per Day: 0.02 Content Count: 10018 Reputation: 2369 Joined: 10/28/11 Last Seen: 10 hours ago Share Posted August 18, 2012 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 Quote Link to comment Share on other sites More sharing options...
saithis Posted August 18, 2012 Group: Members Topic Count: 2 Topics Per Day: 0.00 Content Count: 40 Reputation: 20 Joined: 12/31/11 Last Seen: May 10, 2013 Share Posted August 18, 2012 #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"? 1 Quote Link to comment Share on other sites More sharing options...
GreenBox Posted August 18, 2012 Group: Members Topic Count: 9 Topics Per Day: 0.00 Content Count: 303 Reputation: 101 Joined: 11/13/11 Last Seen: October 11, 2023 Share Posted August 18, 2012 #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. Quote Link to comment Share on other sites More sharing options...
saithis Posted August 18, 2012 Group: Members Topic Count: 2 Topics Per Day: 0.00 Content Count: 40 Reputation: 20 Joined: 12/31/11 Last Seen: May 10, 2013 Share Posted August 18, 2012 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? Quote Link to comment Share on other sites More sharing options...
clydelion Posted August 19, 2012 Group: Members Topic Count: 17 Topics Per Day: 0.00 Content Count: 754 Reputation: 186 Joined: 05/22/12 Last Seen: October 15, 2022 Share Posted August 19, 2012 Hi, I made a diff for this.. It inherits the group permission for charcommands It uses '!' as char command symbot if you want to use account_id/char_id. id_charcommand.diff Quote Link to comment Share on other sites More sharing options...
Sneaky Posted August 19, 2012 Group: Members Topic Count: 10 Topics Per Day: 0.00 Content Count: 392 Reputation: 47 Joined: 11/18/11 Last Seen: July 8, 2024 Share Posted August 19, 2012 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. Quote Link to comment Share on other sites More sharing options...
Panallox Posted August 19, 2012 Group: Members Topic Count: 12 Topics Per Day: 0.00 Content Count: 117 Reputation: 169 Joined: 11/10/11 Last Seen: April 10, 2024 Share Posted August 19, 2012 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. Quote Link to comment Share on other sites More sharing options...
Vianna Posted August 19, 2012 Group: Members Topic Count: 0 Topics Per Day: 0 Content Count: 47 Reputation: 8 Joined: 12/06/11 Last Seen: January 13, 2013 Share Posted August 19, 2012 (edited) @edit: removed because it could possibly be exploited in production servers, see bugreport:6509 Edited August 19, 2012 by Vianna Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.