For members of our build team, we have a number of guidelines and expectations - both in terms of server builds, and in terms of general staff duties. Some of these will differ from typical staff duties and expectations - as such, any current or future members of the build team are expected to adhere and follow these guidelines and expectations. Failure to do so may result in removal from the build team.
If you're looking to join our build team, be sure to read over these guidelines before applying. If you cannot agree to the expectations and guidelines outlined below, then you will not be able to join the team.
Server Build Ownership
Any build created for the server should be considered to be belonging to Chaotic United - this goes for finished spawns and lobbies, minigame maps, and even incomplete works created in our "builder" world (the internal world used to contain work-in-progress server builds). By building within this builder world, you understand that these builds may be used, with or without your permission, for official server use, with or without credit (though we almost always will give credit where appropriate - see the Build Credits section for details). These builds may also be retained indefinitely by the server, and may not be deleted at any point in the future - regardless of whether or not you are a part of our build team.
In other words, the things you build for the server are just that - they belong to the server. If you build something cool, and we want to make use of it officially, you can't come in later on and demand that we don't. And the reverse is true - if you build something for the server, and it ends up going unused (or were to be removed in the future), you don't get to demand us to put it into use.
Similarly, the server ownership and administration reserves the right to modify your builds, with or without your permission, as seen fit based on server needs or desires. As with earlier points, we also reserve the right to not modify a build, even if you desire that it be changed or altered, if we do not see it fit to do so. Whenever possible, however, we will typically work with you when it comes to making any modifications required - and if you see it fit to make changes to a build, we are happy to accept your feedback and consider it, even if you are no longer part of the build team. However, by being part of our build team, you understand that any decisions made are ultimately up to Chaotic United leadership - you don't get to be the one to make the final call on these types of changes.
Archival and Preservation
At Chaotic United, we believe strongly in archival and preservation - and that the more things that we can preserve, the better. As such, builds within the builder world should never, at any point, be removed or deleted. This does not apply to short-term working copies of builds - however, for anything that has been around for any meaningful amount of time, it should not be deleted or altered at that point. If changes need to be made to an older build, care should be taken to copy the original build, and then that copy should be modified instead.
Additionally, once any build is put into use (ie, a spawn is introduced formally, or a minigame map is added to the selection), it generally will not be modified at that point. In extremely rare and severe cases, minor alterations may be made - but in general, once something is in, it's in. As such, we ask that you ensure a build is finished and finalized before it is put into use. Additionally, any signs with any personal messages are not allowed in most cases. If you are uncertain about a particular sign, you should ask an administrator for guidance.
World Downloads
Like many other Minecraft servers, we periodically reset some of our server worlds - such as Survival and Vanilla. Unlike other servers, however, we take steps to ensure those earlier worlds aren't lost - and are instead presved forever. This comes in the form of public world downloads. These download archives contain the entirety of past worlds - including all dimensions, player inventories and builds, and by extension - the world's spawn build.
Since this is (in our opinion, unfortunately) a rare practice, we want to be clear that any build - such as a spawn, generated structure, or any other official build that is used within one of these worlds will included in these downloads. Additionally, once a world is put up for download, it will not be modified any further beyond that point. As such - when building spawns or other builds that will go into these worlds, be sure that anything anything you include is something you're comfortable with being shared and preserved indefinitely.
Build Credits
Build crediting is a particularly sensitive topic - and one that we have had to work to find a proper balance that works well for our build team, without compromising the server's appearance to the general public.
Small easter egg-esque crediting, such as a player head, can be included - as long as the head is either well-integrated into the build or out of normal player sight. In essence, they should be treated as easter eggs - rare, hidden little secrets.
More overt and direct crediting can be achieved via the Credits area of /warp help - which will always contain the credits for any builds that are prominent or newly introduced at the time. Additionally, credits can be added to /warp credits - which acts as a more permanent home for build credits. If your build gets added here, it'll remain there permanently - even if it isn't shown in future iterations of /warp help.
3rd-Party Builds (Build Tutorials)
In general, reliance on external sources for builds - such as build tutorials or designs - is discouraged. If, for any reason, you must utilize a build tutorial or similar for an official build, this usage must be approved by an administrator. Additionally, care should be taken to ensure that the build in question is allowed to be used on a multiplayer server in the first place.
If the source of the 3rd-party build requires that credit be given, this information should also be communicated to an administrator, to ensure this information is properly accounted for in /warp credits.
3rd-party credit signs may be included in a build, if the signs can be integrated in a matter that naturally fits in with the build. This will require administrative approval - so if you have an idea on a means to integrate this, be sure to get approval first.
If a 3rd-party build is used and this information is not disclosed to an administrator, and we encounter a situation where that original author requests that the build be removed, you will be removed from the build team immediately, and you will not be eligible to join the build team again in the future.
Activity
Unlike the rest of our staff team, activity is generally not considered significantly important for members of our build team. We only ask that you contribute when you are able and needed to do so.
If you are repeatedly asked to work on a server build and are continuously unable to do so, you may potentially be subject to removal from the build team. We won't remove you from the team without any sort of notice, though - we'll try and work with you as best as we can.
Note that this does not apply in situations where the builder also holds a separate staff position on the team (such as Moderator, Developer, or Manager) - in these cases, the standard expectations for activity are to be followed instead.
Questions?
If you have any questions regarding this policy, don't hesitate to ask an administrator! We want these guidelines to be as clear as possible, in order to avoid any miscommunication or misunderstandings - we all work more effectively when we're all on the same page.
As such, if you have any questions or concerns about this policy, be sure to reach out and let us know!
Report Topic