Created
April 19, 2012 17:38
-
-
Save Dinnerbone/2422512 to your computer and use it in GitHub Desktop.
New file formats in 1.3
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#Address, Date/Time, Banned By, Until, For | |
#Exactly the same as banned-players, but with IP addresses. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#Name, Date/Time, Banned By, Until, For | |
#All values are trimmed | |
#<-- these are comments and will be ignored by the parser | |
#The reason field may contain unescaped commas (, <--). It will be loaded as split(line, 5). | |
Hackz0r5001,2012-12-31 12:15:09 CEST,Dinnerbone,Forever,For being unoriginal, I mean really! | |
Hackz0r5000,2012-12-31 12:13:14 CEST,Dinnerbone,2013:01:01 00:00:00 CEST,Being an ultimate badass hacker | |
#Old formats will be converted as the following: | |
OldMan,Unknown,Unknown,Forever,Banned by an operator. | |
#Name field is the person who is banned. Case insensitive. | |
#Date/time field is in the following format: "yyyy-MM-dd HH:mm:ss Z", | |
# or the literal "Unknown". Any values it doesn't recognize will be "Unknown". | |
#Banned by field is the operator who banned the player. Empty values will be | |
# treated as "Unknown". | |
#Until field is the same format as date/time. If this isn't "Forever" then the | |
# player will be unbanned at (roughly) the specified time. Unknown values are | |
# treated as "Forever". | |
#For field is the reason the player was banned. It will be displayed when the | |
# client tries to join. May contain format codes. Empty defaults to | |
# "Banned by an operator." |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#Name, Date/Time, Added By, Comment | |
#All values are trimmed | |
#<-- these are comments and will be ignored by the parser | |
#The comment field may contain unescaped commas (, <--). It will be loaded as split(line, 4). | |
Santa,2012-12-31 12:15:09 CEST,Dinnerbone,He brings me gifts. | |
ReallyCoolDude,2012-12-31 12:13:14 CEST,Dinnerbone,I like this dude. | |
#Old formats will be converted as the following: | |
OldMan,Unknown,Unknown, | |
#Name field is the person who is white-listed. Case insensitive. | |
#Date/time field is in the following format: "yyyy-MM-dd HH:mm:ss Z", | |
# or the literal "Unknown". Any values it doesn't recognize will be "Unknown". | |
#Added by field is the operator who white-listed the player. Empty values | |
# will be treated as "Unknown". | |
#Comment is anything you like. May contain format codes. Empty values allowed. |
@Surfjamaica Nah, the line is split into 5 parts. The ban message is always the last part so no matter how many commas the ban message contains it will be fine. Read this javadoc http://docs.oracle.com/javase/1.4.2/docs/api/java/util/regex/Pattern.html#split%28java.lang.CharSequence,%20int%29 It is the very piece that is being used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Wait, so if the ban message contains commas, it won't screw it up? It just looks a bit confusing, though.