|
View unanswered posts | View active topics
|
Page 1 of 1
|
[ 5 posts ] |
|
Author |
Message |
Walrus Prince
|
Posted: Wed 13 Jun, 2012 - 2:37 am |
|
Joined: Mon 05 Mar, 2012 - 3:34 am Posts: 286 Location: Beaverton, OR
|
I think we should include a command called /disguise [rank name] This command will change the users name to the color of the rank, the person will get his block count temporary block count to a number between the block count needed for the previous rank and the block count for the next rank. Also, you're name would be temporarily set into the category of your rank.
E.g You /disguise blockmason Name is changed to blockmason gold color Block count is between 100,000-200,000 Someone types /players You are displayed in blockmason section
The permission would be for Hop+ and would be useful for patrolling as a lower rank without being detected.
_________________ ^ All credit is given to Belg for one heck of a sig :3
TEAM RED Members: EnderKing (FloatingFatMan) Walrus Prince (TheJamMammoth) jazzi
Castellan of the Timelords
|
|
Top |
|
|
Belgeran
|
Posted: Wed 13 Jun, 2012 - 3:11 am |
|
Joined: Thu 17 Feb, 2011 - 1:31 am Posts: 2301 Location: Colorado
|
/hide works too?
interesting idea
_________________
|
|
Top |
|
|
Walrus Prince
|
Posted: Wed 13 Jun, 2012 - 3:21 am |
|
Joined: Mon 05 Mar, 2012 - 3:34 am Posts: 286 Location: Beaverton, OR
|
I know /hide works, but that makes you invisible and that's kind of weird if you're new to classic and everything like that.
_________________ ^ All credit is given to Belg for one heck of a sig :3
TEAM RED Members: EnderKing (FloatingFatMan) Walrus Prince (TheJamMammoth) jazzi
Castellan of the Timelords
|
|
Top |
|
|
Walrus Prince
|
Posted: Wed 13 Jun, 2012 - 2:39 pm |
|
Joined: Mon 05 Mar, 2012 - 3:34 am Posts: 286 Location: Beaverton, OR
|
What I meant for that is if there is a guest who is building then suddenly, someone says, "Nice build." If the guest saw the name and typed /players making sure they were in the same map and the person was reffering to the guest, the guest wouldn't see the name and kinda get freaked out. That happened to me once and I got pretty scared.
_________________ ^ All credit is given to Belg for one heck of a sig :3
TEAM RED Members: EnderKing (FloatingFatMan) Walrus Prince (TheJamMammoth) jazzi
Castellan of the Timelords
|
|
Top |
|
|
Zion Fox
|
Posted: Wed 13 Jun, 2012 - 6:07 pm |
|
Joined: Wed 15 Dec, 2010 - 9:06 am Posts: 1769 Location: Surrey, England
|
With the current permissions system, faking a rank would be impractical due to said Op needing to re-gain their previous rank to use moderation commands. The downside with this being that once set to a rank lower than Operator, they will not be able to use promotion or setrank commands (regardless, they cannot use the command on themselves).
Internally, HawkServ sets each player to three constructs. The Players construct, the Groups construct, and the Level construct. In each of these constructs, every single piece of information is gained about the player, from their block count, to how many times they have visited the server, to their exact location in a map, to what block they are holding, and if they last created or destroyed a block.
When a user executes a command, several parameters are checked before the command is even sent to the part of HawkServ which deals with the request. These parameters range from checking what group they are in, checking the group's Permission Level, seeing if they can perform the command in a particular level (try cuboiding in a museum, for example.) and a few other things.
Since faking a user group, we would need to add extra variables for the users block count, permission level, rank name, times online, and so forth, which would all consume memory. Then we would need to add a Player variable to set whether the user is faking another rank, and that variable will need to be checked in so many different places that it would not really be worth the effort put into it, which could go into making the software more stable, and secure.
Initially I thought it was a good idea, but as other Operators+ have pointed out, there is always /hide. We could improve on the Hide command which can force their normal chat to Opchat, to prevent freaking out users, or we could have it where it will unhide them after so many minutes if they add that to the variable (/hide 10 - will unhide after 10 minutes), etc.
|
|
Top |
|
|
|
Page 1 of 1
|
[ 5 posts ] |
|
Who is online |
Users browsing this forum: No registered users and 3 guests |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|
|