jchance

Which do you prefer- Giant map devouring dirt blocks, or giant map flooding lava pools? Please be detailed in your response.

The working theory is this: 1. Only non-dangerous commands will be allowed through the plugin 2. Only admins may place command blocks 3. Only admins may program command blocks 4. The command block, and the redstone connected to the command block, will be protected from editing by everyone but staff. This I have gathered over several discussions on the subject with Dumbo while in game, IRC, etc.

This is why you were banned: 2014-11-29 20:51:53 | JJFL logged in 2014-11-29 20:52:03 | <JJFL> o/ 2014-11-29 20:52:06 | <The_King1337> Hey JJFL 2014-11-29 20:52:07 | <TokenChineseGuy> yo JJFL 2014-11-29 20:52:11 | <TokenChineseGuy> hey Tex, JJFL is a girl! 2014-11-29 20:52:12 | <JJFL> :) 2014-11-29 20:52:20 | <TexKid> *starts jacking off* 2014-11-29 20:52:23 | <TokenChineseGuy> D: 2014-11-29 20:52:24 | <JJFL> o.o 2014-11-29 20:52:32 | <TexKid> JJFL any pics!?!?!?!? 2014-11-29 20:52:40 | <The_King1337> :/ 2014-11-29 20:52:41 | <AvadaKedavra03> wtf 2014-11-29 20:52:42 | <The_King1337> tex 2014-11-29 20:52:45 | <JJFL> lol I'm good :P And why would I send pics tp people idek 2014-11-29 20:52:46 | <AvadaKedavra03> tex what the fuck 2014-11-29 20:53:07 | <JJFL> o/ 2014-11-29 20:53:08 | <The_King1337> i wish i could show your parents the shit you say online 2014-11-29 20:53:16 | <AvadaKedavra03> hey gabe tex is back 2014-11-29 20:53:31 | <TexKid> Avada..... he was here when I came back..... 2014-11-29 20:54:10 | <TexKid> Okay gtg bai 2014-11-29 20:54:14 | TexKid lost connection: Disconnected This is the second time you have been banned for inappropriate behavior related to female players. You are no longer welcome in this community. I will not unban you. Please find somewhere else to play.

I HAVE TO PEE BUT I DON'T WANT TO GET UP AND WALK THE 30 FEET TO THE BATHROOM.

Added snowball-firefight region flag. Lets you put fires out with snowballs. Why? Because its cool, thats why.

Region Size I'd just like to throw out that we should keep region sizes, for the purpose of discussion and policy, simple. For example, if we're going to set a region size limit it should be something that moderators can quickly grasp and calculate in their head, even with no experience (like for mods that are primarily from S and P) - something like "X + Y = 300 or less" meaning a 150x150 region, 100x200 region, 50x250 region,etc. I understand those are all different sized regions, but even with such an open policy that is easy for players and mods to understand you can never get more than 22,500 sq/m to start.

Added /up command. Usage: /up <number of blocks> Example: /up 10 Moves you up 10 blocks, places 1 glass block under your feet. Useful for when you want to start building in midair, or jump to a specific y level. Removed: // //sp //sp area Because they were not being controlled by the WorldEdit region plugin (unsafe command that would allow anyone to grief). Sorry, nothing we can do about that one.

Creative now has personal time control- /ptime, a custom plugin by Dumbo52. Command syntax: /ptime day = locks it on day /ptime night = locks it on night /ptime 6000 = locks it on a specific time of day, in ticks. /ptime = Command with no setting turns off personal time, returns to server-wide time. Ticks go from 0 to 24000. Each hour has 1000 ticks. Minecraft time is kinda dumb and is based off the start of day being at 0000: 0000 is sunrise, 6AM 6000 is noon 12000 is sunset, 6PM 18000 is midnight

Added //rotate and //flip to available commands. Added created-by and date flags to regions automatically when they are created using the /cregion flag (moderator command).

//rotate and //flip have been added.

World Edit has been enabled on C for protection owners in their own protection. We've also expanded the map by 50%. https://nerd.nu/forums/index.php?/topic/2739-creative-now-has-world-edit-and-the-map-expanded/

WorldEdit has been released on creative: https://nerd.nu/forums/index.php?/topic/2739-creative-now-has-world-edit-and-the-map-expanded/#entry20859

I’m happy to announce that after many weeks of testing and policy discussion World Edit is now available to region (protection) owners on Creative. World Edit Details: You can use World Edit within regions (protections) you are an owner of. You have the following World Edit commands available: //cut //copy //paste //rotate //flip //undo //redo //drain //fixwater //fixlava //cyl //hcyl //sphere //hsphere //faces //line //stack //walls //overlay //set //replace //move //expand //contract //inset //outset //shift //snow //thaw //setbiome For help with command syntax, here is a handy PDF The server uses Asyc World Edit, so multiple edits happening at the same time may be queued to prevent lagging the server. You’ll need to wait for your current operation to complete before starting more. There is a limit to the number of blocks you can change at one time, which is going to be adjusted over the next couple weeks as we assess the load on the server. World Edit is limited to Cuboid regions. If you have a Poly region (a region with more or less than 4 corners) it will continue to be protected, but you will not have access to World Edit in that region. This is a limitation of the plugin and not nerd.nu. New Protection Policy for Creative: With this change we’re also changing the protection policy on C so that you can request a protection before you have actually built something. This will let you use World Edit to clear land and build. Here is how it works: You mark out a new region (protection) with a complete rectangle around the area. New regions will not be created with just the 4 corners marked as previously. You must create a complete rectangle around your region (like land claims on other servers). Do a /modreq for protection from the area you have marked. Make sure the mod knows what color border is yours- Example: “/modreq please protect the area marked in sponge” You can start building (without world edit) while you wait on a mod to do your protection. You do not need to wait online for a /modreq, we can do them even if you log off. A moderator will do your modreq and set you as the region owner. Once you have a region with you set as owner you can use World Edit within that region. We have a plugin in place to prevent your World Edit edits from leaving regions you own. You can add more owners to your region if you like using the “/region addowner” command. However, you are responsible for the actions of other owners in your region. You can modreq to have an owner removed. We will not remove the primary (first) owner of a region. You can add members as normal, or modreq for child regions as normal if you are building a city. Members do not have access to world edit in your region. Owners of child regions do have access to world edit in their child regions. Moderation Policy Changes: ModMode is Required on Creative Now: Moderators will have access to world edit in their own regions just like default players when not in ModMode. Moderators will have access to global world edit when in ModMode to help other players (like Admins do now). Moderators must not do regular gameplay / building while in ModMode because this will let you bypass region restrictions on World Edit. This puts other players builds and potentially the server at risk from accidental commands. This policy will be actively enforced on C for the protection of the community. Mods not following proper Mod Mode policy (only using Mod Mode for moderator duties) will be warned, and continued warnings will lead to loss of mod status. Note: Do not make world edit selections before switching to modmode. The permissions are run when an area is selected, so if you select something and switch to modmode then the selection is still using the non-modmode permissions. Regions and Such: Regions now have two new flags that are automatically added: created-at and created-by. This shows when a region is created and who (which mod or admin) created it. Making new Regions: All new regions need to be cuboid (by setting two points). Players can not world edit in Poly Regions. All new regions with no builds in them need to have a complete border around them to mark the region. Do not create protections for regions where just the 4 corners are marked. This is for a number of reasons: 1. It keeps players from just marking 4 blocks and making huge regions 2. It shows region borders so we can resize regions that are under utilized 3. It shows other players where regions begin and end so they plan their area accordingly You can still protect already built structures as normal. The above only applies to “new” regions that are created before anything is built. Don’t Overlap Regions: When regions overlap both owners can use world edit in the overlap area, leading to disaster. Avoid it. /region-intersects is a useful command that tells you if your current selection intersects an existing region- use it! Region Naming: All region names must follow this format: regionowner_regionname This is so anyone can tell who is the primary (first) owner of a region. The primary (first) owner of a region should never be removed. In special cases where this needs to happen (transferring the ownership of a region to someone else, etc.) then you can elevate the modreq to admins. Adding / Removing Region Owners: Moderators should never add region owners. Instruct players how to /region addowner <playername> if they want to add owners. Moderators can remove region owners as long as they’re not the primary (first) region owner that is in the region name. If this needs to happen for some reason, elevate to admin. Renaming Regions: There are many existing regions on creative right now that do not follow this format. Moderators can /region-rename <old region name> <new region name> at the region owner’s request. Land Disputes, Resizing of Regions, Clearing of Derp Regions: Land disputes will still be handled at a C admin's discretion. Resizing of existing regions and clearing of derp regions, of which there will probably be many, will be handled at a C admin's discretion. A derp region, for example, would be one where some player joins, makes a giant sponge or lava cube, and then abandons it never to return. These can be submitted in an admin mod request for removal and will be removed based on the last /seen time for the player and last edit time in the region. For more information about moderation changes as well as policy discussion please see this mod chat thread: https://nerd.nu/forums/index.php?/topic/2729-opportunity-for-comment-world-edit-changes-on-c-and-new-policies/

Poly Regions still work for protecting things. Players just won't be able to use world edit in poly regions that they own like the standard cuboid ones. We'll be adding /region rename to mod perms with the update also. I have Slide lined up to get the config moved from C-Dev to C and help me double check perms and settings. We're aiming for a release tonight as long as everything goes well.

Yeah, I was speaking from the perspective of mod permissions though. Its a fairly simple operation for a mod to /rg select regionname, /cregion new_regionname player name using the same selection, then /region remove old region.

There is nothing we can do about existing regions other than to recreate them (to my knowledge its impossible to rename regions). We can shorten usernames- we just need enough to be able to identify the primary / first owner or a region for moderation purposes. DL123 is pretty obvious thats Diamond_Lover123. However, Taco_something wouldn't be good enough since there is SirTacoFace, TacoDude, xX_Taco_Waffle_Xx, etc.

More information on the change- This is what players will have access to. Some commands will be limited in radius or size TBD by tech admins. - worldedit.clipboard.cut - worldedit.clipboard.paste - worldedit.drain - worldedit.fixlava - worldedit.fixwater - worldedit.generation.cylinder - worldedit.generation.pyramid - worldedit.generation.sphere - worldedit.history.redo - worldedit.history.undo - worldedit.navigation.jumpto.command - worldedit.navigation.jumpto.tool - worldedit.navigation.thru.command - worldedit.navigation.thru.tool - worldedit.region.curvy - worldedit.region.faces - worldedit.region.line - worldedit.region.move - worldedit.region.overlay - worldedit.region.replace - worldedit.region.set - worldedit.region.stack - worldedit.region.walls - worldedit.selection.* - worldedit.selection.contract - worldedit.selection.expand - worldedit.selection.hpos - worldedit.selection.inset - worldedit.selection.outset - worldedit.selection.pos - worldedit.selection.shift - worldedit.snow - worldedit.superpickaxe - worldedit.superpickaxe.area - worldedit.thaw - worldedit.wand Of course, if any of these cause major problems or lag we'll have to remove them. This is all pretty new for everybody.

Oh, and one other thing: For those who do not know, we use Async World Edit on all Nerd.nu servers. This should noticeably decrease the impact of using world edit by multiple people (at the expensive of slower edits as needed- it automatically queues jobs). I'm pretty sure we'll crash the server a couple times figuring out the right limits. You can't make an omelette without cracking a few eggs.

World Edit policy has been posted for moderator comment: https://nerd.nu/forums/index.php?/topic/2729-opportunity-for-comment-world-edit-changes-on-c-and-new-policies/

We will soon be adding WorldEdit to C that is limited to regions that you are the region owner. This change will require several changes in policy and general moderation procedure on C. A few key points need to be addressed: Region / Protection Policy: Players want to use WorldEdit to build in their region, so we can't just issue protections after something is already built like current policy states. Moderation Policy: Moderators will have access to much broader permissions, so we need a way to prevent (for the most part) relatively inexperienced mods from doing major damage to the map. Region naming nomenclature needs to be standardized for all regions and shape and size considerations must be made. Region / Protection Policy: Old Policy: We will only protect things after they are built- no protecting empty land. New Policy: We will create world guard regions for areas, with the region outline clearly marked with a border rectangle, before something is built so that players can use WE to clear land, build, etc. Players can remove the rectangle once they've have actually built in the region. The rectangle (not just 4 corners) is important- it keeps players from just flying around placing 4 blocks to mark a huge area. They at least have to put the time in to making a border. It marks the area so other players know something is going there. Protections without builds and without a marker rectangle around the region would just piss people off It makes moderation easier. Less risk of overlapping regions. Easy to see when land is utilized. Griefing / Region Ownership Policies, etc: When a region is created the player is set as owner and their player name is part of the region name as outlined below in moderation changes, making them the primary owner. Owners get world edit permissions in their own region. Members do not get World Edit permissions. If they add another owner then that is 100% their decision that they have to live with. Mods should never add new owners to a region and should instead instruct the player how to use the /region addowner command. Primary Region owners (the person with their name in the region) can make a modreq to have other owners removed. The primary region owner is the ONLY person who can have another owner removed. There will be no exceptions to this policy. If your name is not in the region name you can not remove owners. If a player gives region owner permission to someone else and they do something the primary owner doesn't like, be it World Edit or otherwise, then that is on the region owner. This is not grief. This is the primary region owner making bad decisions. The same goes for if you add another owner and that owner adds more owners- again, bad decision making on the primary owner's part. In short, once a region is given to the primary owner it is theirs to manage (and deal with the consequences) as they see fit. We're bringing personal responsibility back to Creative. Parent / Child Regions (Cities): The plugin that limits World Edit to regions works like this: Parent region owners (mayors of towns) can world edit in both the parent and child regions. Child region owners (plot owners) can only world edit in their child region. The same rules that have always applied to parent/child regions still apply: If you have given a child region to someone else you do not get to modify other people's builds in that child region. Parent region owners (city mayors, if you like) may make a mod request to have a build that does not fit their city style moved out of the city. Parent region owners are not allowed to just remove or modify builds they don't like. You gave the child region owner the reasonable expectation of ownership of their plot and freedom from interference. New Moderation Policy: Modmode Procedure is now Required on Creative: All Mods on C are expected to use Modmode only for moderator duties and not to use Modmode for regular gameplay. This is in line with policy on other servers. Moderators outside of Modmode will have the same permissions as default players in respect to World Edit. (meaning they can use WE inside regions they are owner) Moderators in Modmode will have global world edit permissions to help players, do mod duties, etc. (meaning they can use WE outside of regions they own) This change is necessary to prevent moderators from accidentally using World Edit outside their own regions and overlapping in to others protections. A mod, using mod mode, and using world edit in regular building gameplay is a risk to other players since they can override region limits. This policy will be actively enforced on C for the protection of the community. Mods not following proper Mod Mode policy (only using Mod Mode for moderator duties) will be warned, and continued warnings will lead to loss of mod status. Region Creation: Regions must follow the playername_regionname format. This is important so we know the original, primary owner of a region. This used to be standard operating procedure on C, but I've seen new mods move away from it. We need to bring the standard region name format back. Regions will have the new created at flag added that shows the date the region was created. This will be added to the /cregion command and automatic. Unused regions may be removed or resized smaller after 2 weeks by mods or admins. Everyone will be able to check the created at flag on the region using /region info. We're also adding a "Created by" flag to regions so we can see who created what region. Land Disputes, Region Resizing, Clearing of Derp: Land disputes will still be handled at a C admin's discretion. Resizing of existing regions and clearing of derp regions, of which there will probably be many, will be handled at a C admin's discretion. A derp region, for example, would be one where some player joins, makes a giant sponge or lava cube, and then abandons it never to return. These can be submitted in an admin mod request for removal and will be removed based on the last /seen time for the player and last edit time in the region. Things that Must Be Avoided: Overlapping Regions Bad. Both region owners can world edit in the overlapping area. Don't make them. Protip: the "/region-intersects" command tells you if any regions intersect your current selection. Thanks Denevien for the reminder! Poly Regions can no longer be used The world edit / world guard plugin we are using does not support poly regions. Only cuboid regions can be used on C once the new plugins are activated. Poly regions still work for protection, but you can't use world edit in poly regions you are an owner of- only cuboid regions. Some Questions that have been brought up already (and answers!): We don't have a maximum size now so I don't really see the need to set one. I combined the land claim policy (make a rectangle around the area to claim land) and the region policy so that they can't just put out 4 wool blocks and claim a huge area- they actually have to spend the time to mark a large area if they're going to claim it. Having a max size makes it too ambiguous- How do you determine the max size? Is it by volume? What if they use //expand vert, does that count the air? Is it by X and Y length (requiring mods to do math based on the coordinates)? Then, what are the criteria for getting larger than a max size? How do you determine, before anything is built, if something deserves a bigger than normal region? It just seems like it would open mods and admins to claims of favoritism like "You gave Bob a 300x300 region but you only gave me 100x100!" and be hard to regulate and administer. This has had some discussion amongst admins. I don't have a strong opinion one way or the other as I believe that if you are a moderator you can be trusted to make your own regions. However, there have been issues on other servers in the past. I'd like to leave it as "If you have any doubt about what you are about to do and if it may be seen as mod abuse, then ask another mod or admin for their opinion and/or to do it for you." Some say its better to ask for forgiveness than to ask for permission. I do not agree and I will not look favorably on a mod who does something that is clearly against policy or abuse. When in doubt ask somebody. For players who don't want to use WE to build they can just build like normal- We can always protect structures as we've always done. The new policy changes proposed above only apply to new "empty" protections. We can limit the size of edits by user group (default, mod, admin) and block problem items from world edit completely. I did not include those settings in this discussion since Its not really something we will expose to mods or the community to discuss per se- I will have to sit down with a tech admin and determine what they think is safe for Creative, and it will probably have to be modified once its actually been in use and we've seen the impact.

smiler100 added /ignore to C as well as S and P. http://www.reddit.com/r/mcpublic/comments/2lk47d/ignore_is_now_available_on_pve_creative_and/ This was a popular request that is now marked as finished.

Since this ban appeal is 5 days old and Cyotie is unavailable I'll handle this ban. You were indeed banned for being an alt of another banned player / Ban evasion. It makes sense that you would have the same IP address as your brother. Luckycharms25, please read the rules at http://nerd.nu/rules and have fun. Unbanned.

The new survival rev should have Potato as the official tuber of S. If that was the case I'd play on S again. Russet 3:16

The cadmins and head admins have agreed on trying to add restricted World Edit for everyone to creative. Creative Dev is up and I'm working with the Tech Admins to test async world edit + a region restriction plugin for world edit for default (regular) players. There are a lot of errors right now and we'll have to sort them out with the other nerd plugins, but we're working on it!

I talked to slide- Evidently LogBlock and log WorldEdit. This plugin is designed to do exactly what I outlined above, limiting WE to a region's owner: http://dev.bukkit.org/bukkit-plugins/wrg/ Slide is going to get a c-dev server set up for testing when he can. I'll update when he gets it done.