tompreuss

Relevant lines from the logs posted with smiler100's permission: 2013-09-28 13:58:16 | princessugly logged in at ([world] 63.5, 111.0, -27.5) 2013-09-28 13:58:16 | - 2013-09-28 13:59:07 | <princessugly> Damn nigger, so many fags up in this shit nigger 2013-09-28 13:59:09 | <princessugly> nigger 2013-09-28 13:59:11 | <princessugly> nigger 2013-09-28 13:59:12 | <princessugly> fag 2013-09-28 13:59:13 | <princessugly> nigger 2013-09-28 13:59:14 | <Rokku117> uhh 2013-09-28 13:59:15 | <princessugly> nigger 2013-09-28 13:59:16 | <princessugly> nigger 2013-09-28 13:59:16 | <Zuziza> wtf pugly 2013-09-28 13:59:16 | <Skynet2029> oh boy 2013-09-28 13:59:17 | <WaterSlide> lol, wow 2013-09-28 13:59:17 | <drtmv> um 2013-09-28 13:59:18 | <princessugly> nigger 2013-09-28 13:59:18 | <josephrooks> wow 2013-09-28 13:59:19 | CH: Running original command on player smiler100 ----> /ban princessugly homophobia; racism on P 2013-09-28 13:59:19 | princessugly left the game. 2013-09-28 13:59:19 | [MCBouncer] smiler100 banning princessugly - homophobia; racism on P nerd.nu/appeal 2013-09-28 13:59:19 | User princessugly has been banned by smiler100. (homophobia; racism on P nerd.nu/appeal)

When I saw the 1.7 announcement post, I threw together a quick icon for P that would serve as a temporary placeholder until we could get a better one: I like the idea of a contest, and I like the idea that each person makes a set.

We deal with builds that are too close to other builds on a case by case basis. Unbanned.

You are responsible for the actions of your account, regardless of if you remember them or not. Read nerd.nu/rules and reply here saying that you have done so and agree to abide by them from this moment forward to be unbanned.

Thank you slide. Hi protoxyn, On 2013-05-13 you edited several sections of rails on P. One series of edits redirected player minecarts into lava another redirected them to a location different than the one intended by the rail builder and another like the previous you also destroyed some other rail and someone's bed. Does this record of your edits on the day in question spark your memory? Do you have any explanation for your actions?

Locking and archiving for edk.

I'm curious now, is it possible to compare this number to that of another week? Perhaps the week immediately preceding the hard mode week? I tried a few times to come up with a number, but it's not easy to comb through the older dataset. I'll try again on Tuesday in an attempt to get a number for the week after hardmode. There were 2094 total deaths in the week after hard mode that we were back on normal. Oh, and per the results of this poll, we're back on hard mode, as of now. Thanks everyone for voting and participating in the discussion!

I'm curious now, is it possible to compare this number to that of another week? Perhaps the week immediately preceding the hard mode week? I tried a few times to come up with a number, but it's not easy to comb through the older dataset. I'll try again on Tuesday in an attempt to get a number for the week after hardmode.

How many total deaths? About 2604 totals deaths, so less than five percent were due to starvation. ("About" because this number was generated via a large regex query of all possible death messages over the past week, then subtracting chat lines that weren't death messages (but just talking about death messages.)

Statistics: there were 117 starvation deaths recorded during our week long test.

I don't feel granting any additional WorldEdit permissions outside of the way they are set up now is a good idea. Like totemo says, WorldEdit is one of the easiest ways to take down a server. It seems like the information wanted is a total number of blocks in a build. In addition to a method as simple as counting the blocks as you place them, there are client side modifications that can do this. Schematica is one. My LogBlock queries take long enough and put enough strain on the server as it is and I don't feel having a few hundred more people having access to querying that database is in our best interest. Also, it seems like the reported total number of blocks created in a LogBlock query wouldn't even accurately report the number of blocks in a build anyway, since builds have plenty of create/destroy/create happening. The best way to get that information is //count or //distr, and as I said, I'm not comfortable giving out WorldEdit permissions to anyone who does not currently have them. That all being said: totemo, if you think a watered down or wrapped version of /lb me wouldn't be too bad on us lag wise or query wise, I'm interested in hearing more about how you could go about implementing that.

Sorry this question wasn't answered sooner. From what I've seen in the previous nomination round there were a number of factors for people being chosen / not chosen after the voting thread ended. People who received an overwhelming majority were a natural choice for the moderating team, I'm not aware of a set percentage that is enforced for people to meet as a criteria though it has been based on the majority of the votes and looking further into how people voted for each nominee, such as people who clearly have never interacted with the person being voted upon, as opposed to others who have. There are instances where a detrimental piece of information comes to light from one of the nominees which raises a discussion before confronting the person in question for clarity before making a decision. I imagine the other head admins who have been involved with more nominee threads may be able to provide more of an insight. It might behoove us if you disseminated to the mods here some of the information Ludeman posted about back in this thread in the admin-chat archives. It's about a year old, but I think the goal of this thread and his original head-admin-chat thread are the same. There's some stuff there that he says should be shared at the next mumble meeting, but I don't believe it was ever written down anywhere mod-accessible afterward. The notes I took (and note that I wasn't even a mod yet) just say "mod nomination process changes". I couldn't find anything in the mod-chat or mod-chat-private archives, though another thing to remember is that we aren't adding new mods to the archives forum anymore anyway.

Buzzie has been taking me through his updates every few days in game, and everything has been looking amazingly good so far.

I'm not even sure if the one under the base had a library, since it seemed oddly cut off. I'll load the map on singleplayer and try to find it, because I'm worried about poking around the final map this close to launch. =P I'll take care of those bits/pieces of stronghold and end portal this evening (right now).

They can't be pushed by pistons. And they're already in individual 1x1x1 obfuscatedly named protected regions, so we're set.

For reference, the collection of /r/minecraft CTF posts that I could find: June 2013 CTF attempt November 2012 CTF April 2012 CTF / April 2012 CTF followup

Ban information: Mumble account Grayman banned 2013-08-19 20:27:53 with reason "Player/Channel Disruption" Please be patient and CharGB will be with you as soon as she can. If no one has attended to your appeal after 48 hours have passed, please feel free to bump this thread to bring it to the top of the list. Previous ban: 1) Ban for graymansnel for Exhaustive misuse of staff time and resources; ban result of cumulative incidents. nerd.nu/appeal by Tharine on 2013-06-06 06:28:39 Notes: 1) Note #27757 for graymansnel on c.nerd.nu: minor rail grief on P, warned via mumble by tompreuss on 2013-02-04 18:01:47 2) Note #31610 for graymansnel on c.nerd.nu: Further warned that rule breaking in the absence of moderators is still not allowed (warned via mumble) by Tharine on 2013-05-30 20:49:19 3) Note #31848 for graymansnel on c.nerd.nu: Extensively warned about rules at length. Do not tolerate any rule breaking from this user. by Tharine on 2013-06-06 02:59:08 4) Note #32643 for graymansnel on c.nerd.nu: claims of using x-ray. on creative. by boredeth on 2013-06-28 08:47:42 5) Note #32945 for graymansnel on c.nerd.nu: Formally explained to and warned about doxing. Do not tolerate in the future by kitcatbar on 2013-07-24 11:46:24 6) Note #33447 for graymansnel on c.nerd.nu: Explained alt doxing and that it is not allowed over mumble by kitcatbar on 2013-08-18 19:55:44

I put them together last time, I can do it again per these specifications.

A suggestion if possible to implement at this stage would be to auto add players on each team to groups g:red and g:blue and to auto-lock placed chests to those groups. Last November we didn't use LWC (so we did things like place blocks surrounding chests to protect them from theft) but this past attempt we did have LWC and locking things to different people/groups was cumbersome and difficult to coordinate, especially with such large teams. Those look like penises. Well done.

You then went and destroyed some claim markers and didn't replant when you took some crops and you destroyed this player's flowers A complete summary of your edits Oh, and I would be remiss if I left out the swastika you carved It sure doesn't seem like this was, as you describe, "just digging around". Is there any other explanation you'd like to offer for your actions?

Thank you Mrloud. Hi EvanFucksTeemo, Your grief started when you took these quartz blocks from another player's base you added a sign and broke a torch all pretty minor stuff so far, but still very much not allowed. You then moved on to a bit more general grief of the base in a nearby area, as seen in the following images

If you do want to actually remove it (so it doesn't show up like it does here), you can follow this tutorial: GitHub Help: Remove sensitive data. :D

Ban for #11822145 indestruct1ble on c.nerd.nu for crop grief on s.nerd.nu nerd.nu/appeal by totemo on 2013-06-30 21:42:31 (no more bans, 1 notes) Note #32686 for indestruct1ble on c.nerd.nu: Warned for minor grief on C. by barlimore on 2013-06-29 18:59:32 xXNjordXx asked me to comment here with relevant information: The minecrafter523 ban was first, so the indestruct1ble ban will be permanent for ban evasion. Njord, when you handle the minecrafter523 here take into account that he evaded the ban (long enough to get both a note about grief and a ban for grief) in addition to the ban reason for the minecrafter523 account.

Leads breaking on chunk unload is a known issue on Mojang's end. A lead API has only recently been added to CraftBukkit and as far as I can tell WorldGuard has not yet used it to fix the other issues you mention.