2 /env bugs. + server command disabled bug
Posted: July 3rd, 2012, 12:06 pm
1st bug.
When I use /env with variable 'fog', 'sky' or 'clouds' the only thing that happens is something in the text says "Usage: /Env <worldname> <variable>" and I type "/env test (fog/sky/clouds) red", I'm only following what is said in help which is "/Env <worldname> (fog/sky/clouds) <color>".
2nd bug.
When you make a world and have env settings on the world, when you load the file in an other world name, it removes all the settings. This is bad for world templates.
The server disabled command bug is:
When a command is disabled on the server it will still show the command options in "/commands all" and the rank required would be the color of the default rank, this would be misleading at first if you don't check the "/help <command>" on the disabled command
When I use /env with variable 'fog', 'sky' or 'clouds' the only thing that happens is something in the text says "Usage: /Env <worldname> <variable>" and I type "/env test (fog/sky/clouds) red", I'm only following what is said in help which is "/Env <worldname> (fog/sky/clouds) <color>".
2nd bug.
When you make a world and have env settings on the world, when you load the file in an other world name, it removes all the settings. This is bad for world templates.
The server disabled command bug is:
When a command is disabled on the server it will still show the command options in "/commands all" and the rank required would be the color of the default rank, this would be misleading at first if you don't check the "/help <command>" on the disabled command