With the 1.2 and 1.3 updates, the basic observation is that the Minecraft_server.jar is severly lacking some basic commands and functionality, like something as simple and basic as /sethome and /home
So this thread will be about what the community (and server owners) would like to see added to the Minecraft_server.jar
i'll take the 1st stab at it: add a server option to use a MySQL database because the basic server.log is severly lacking... One of the problems is rampant griefing, and kids know they can get away with it, but with Block changes being logged, then #1. it would be a deterrent to would-be griefers and #2. Admins can rollback damage.
(i know i can't be the 1st one to observe the problems with Minecraft_server.jar, but my search on the subject didn't return any significant results)
With the 1.2 and 1.3 updates, the basic observation is that the Minecraft_server.jar is severly lacking some basic commands and functionality, like something as simple and basic as /sethome and /home
So this thread will be about what the community (and server owners) would like to see added to the Minecraft_server.jar
i'll take the 1st stab at it: add a server option to use a MySQL database because the basic server.log is severly lacking... One of the problems is rampant griefing, and kids know they can get away with it, but with Block changes being logged, then #1. it would be a deterrent to would-be griefers and #2. Admins can rollback damage.
(i know i can't be the 1st one to observe the problems with Minecraft_server.jar, but my search on the subject didn't return any significant results)
Please fix this, I would like to use the basic commands. Especially there should be a chat filter implemented, due to children play this game. Please make some changes quick, Thanks
The problem is that, because Minecraft is a building game, the server would be logging, even on a small server, hundreds if not thousands of block updates, too many to scroll through.
Now, let's assume that the average player mines one block a second. These updates aren't a lot unless you have a lot of players building at the same time. A griefer will most likely use TNT to do their dirty work. This causes a lot of updates at one time, so depending on how the log is designed it could be good or bad.
Now, aside from the number, there's how the changes are logged. The game cannot tell that "Steve's house was destroyed", as the game cannot tell player-placed blocks and player-made caverns from natural ones. So, the only way to tell which blocks were altered is the coordinate system which, although neat and organized for a computer or a math major, is a giant thorn in the side of players who base things off landscape. You, the responsible server admin, would have to first locate and find out (or just ask for) the coordinates of the griefed structure. Upon getting them, you have to look for the exact (or incredibly close, in case the player you asked or you yourself was mistaken in reading the coordinates for some reason) coordinates that were changed, then reverse these. This would be hell for most medium server admin, and large-scale server admin would probably just not bother with it entirely.
So you see, because of the number of block updates an average server has, this would just be pointless tedium that, quite frankly, no one would bother with, even to get rid of griefers and/or reverse damage. It would possibly do as a single-player "undo" command, since there aren't going to be as many block updates in single player as multiplayer, but it wouldn't work in multiplayer.
Rollback Post to RevisionRollBack
[quote=Badgerz]You have to keep in mind that people are stupid.
[quote=Catelite]Just because you don't understand how something works, doesn't make it broken or pointless. >_<
Neo, i'm not sure i understand what the heck you're talking about. I'm asking for a more detailed server log in the form of a database, which by the way, these are available for Bukkit servers in the form of Hawkeye, LogBlock, and CoreProtect plugins. Now...
Hawkeye has over 93,000 downloads
LogBlock has over 56,000 downloads
CoreProtect has over 34,000 downloads
A simple left-click or right-click (in-game) returns results from the database... it's not hard. Mojang can even include options in the server.properties file (default off). So those who for whatever reason, don't want a more detailed database log, can opt out.
The Minecraft_server JAR doesn't even have /sethome or /mute or /tpa... that right there should tell you something is VERY wrong... And it needs improvements.
A simple left-click or right-click (in-game) returns results from the database... it's not hard. Mojang can even include options in the server.properties file (default off). So those who for whatever reason, don't want a more detailed database log, can opt out.
You're missing the point, which is the amount of logs that would be created in the database.
Assume, like you said, every right/left click in the game returns a result, now every result you have to scroll through. Those plugins may work for small servers, where there aren't as many results, but not for large servers, where there's, like I said, a lot of results coming back every second.
Rollback Post to RevisionRollBack
[quote=Badgerz]You have to keep in mind that people are stupid.
[quote=Catelite]Just because you don't understand how something works, doesn't make it broken or pointless. >_<
I don't see what you're saying. I hoped you could see what I meant, I meant it wouldn't work well in multiplayer except on small servers; servers that are 10 people at the maximum, and aren't "build" servers (servers specifically for people building a large project, which would have a lot more block updates than a normal server).
Rollback Post to RevisionRollBack
[quote=Badgerz]You have to keep in mind that people are stupid.
[quote=Catelite]Just because you don't understand how something works, doesn't make it broken or pointless. >_<
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSo this thread will be about what the community (and server owners) would like to see added to the Minecraft_server.jar
------------------------------------------------------------------------------------------------------------------------
i'll take the 1st stab at it: add a server option to use a MySQL database because the basic server.log is severly lacking... One of the problems is rampant griefing, and kids know they can get away with it, but with Block changes being logged, then #1. it would be a deterrent to would-be griefers and #2. Admins can rollback damage.
(i know i can't be the 1st one to observe the problems with Minecraft_server.jar, but my search on the subject didn't return any significant results)
Please fix this, I would like to use the basic commands. Especially there should be a chat filter implemented, due to children play this game. Please make some changes quick, Thanks
Now, let's assume that the average player mines one block a second. These updates aren't a lot unless you have a lot of players building at the same time. A griefer will most likely use TNT to do their dirty work. This causes a lot of updates at one time, so depending on how the log is designed it could be good or bad.
Now, aside from the number, there's how the changes are logged. The game cannot tell that "Steve's house was destroyed", as the game cannot tell player-placed blocks and player-made caverns from natural ones. So, the only way to tell which blocks were altered is the coordinate system which, although neat and organized for a computer or a math major, is a giant thorn in the side of players who base things off landscape. You, the responsible server admin, would have to first locate and find out (or just ask for) the coordinates of the griefed structure. Upon getting them, you have to look for the exact (or incredibly close, in case the player you asked or you yourself was mistaken in reading the coordinates for some reason) coordinates that were changed, then reverse these. This would be hell for most medium server admin, and large-scale server admin would probably just not bother with it entirely.
So you see, because of the number of block updates an average server has, this would just be pointless tedium that, quite frankly, no one would bother with, even to get rid of griefers and/or reverse damage. It would possibly do as a single-player "undo" command, since there aren't going to be as many block updates in single player as multiplayer, but it wouldn't work in multiplayer.
[quote=Badgerz]You have to keep in mind that people are stupid.
[quote=Catelite]Just because you don't understand how something works, doesn't make it broken or pointless. >_<
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHawkeye has over 93,000 downloads
LogBlock has over 56,000 downloads
CoreProtect has over 34,000 downloads
A simple left-click or right-click (in-game) returns results from the database... it's not hard. Mojang can even include options in the server.properties file (default off). So those who for whatever reason, don't want a more detailed database log, can opt out.
The Minecraft_server JAR doesn't even have /sethome or /mute or /tpa... that right there should tell you something is VERY wrong... And it needs improvements.
EDIT: http://i334.photobucket.com/albums/m438/Badnarik/exceptions.jpg
And what's up with so many exceptions ? this never happened with my Bukkit server
You're missing the point, which is the amount of logs that would be created in the database.
Assume, like you said, every right/left click in the game returns a result, now every result you have to scroll through. Those plugins may work for small servers, where there aren't as many results, but not for large servers, where there's, like I said, a lot of results coming back every second.
[quote=Badgerz]You have to keep in mind that people are stupid.
[quote=Catelite]Just because you don't understand how something works, doesn't make it broken or pointless. >_<
Note. This account is deprecated due to past bigotry in posts that cannot be deleted.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI don't see what you're saying. I hoped you could see what I meant, I meant it wouldn't work well in multiplayer except on small servers; servers that are 10 people at the maximum, and aren't "build" servers (servers specifically for people building a large project, which would have a lot more block updates than a normal server).
[quote=Badgerz]You have to keep in mind that people are stupid.
[quote=Catelite]Just because you don't understand how something works, doesn't make it broken or pointless. >_<