VintagePC
GodModePC
VF4-S (Server Operator)
Forum Operator
Minecraft Operator
Global Moderator
Staff Member
How To Apply:
This is the official whitelist thread for the new B-Team minecraft server. The rules are re-posted below for reference.
Here's how it will work: To get white-listed, there are three steps that may be completed in any order:
1. You need to have an existing whitelisted member vouch for you in this thread.
2. Reply in this thread and explicitly state that you have read the rules and agree to follow them.
3. FILL IN YOUR MINECRAFT USERNAME IN YOUR FORUM PROFILE.
I realize that #1 is dependent on an existing list of whitelisted people, so here is what will happen:
Those that previously replied to the B-team announcement (and any of our existing game admins) may be instantly whitelisted without vouch by completing step 2 above to get the pool started, as these seem to be our most interested members.
Hopefully that will be sufficient to get the whitelist vouch system rolling. If not, operators reserve the right to whitelist additional people as we feel necessary. We also reserve the right to deny whitelist applications if we feel it necessary as a result of someone's history.
Rules and Info:
(Modpack info here: http://www.technicpack.net/attack-of-the-bteam)
We know our minecraft servers have had some issues in the past and we hope this iteration irons out most of those issues with regards to griefing, performance, and us having to micromanage everything.
Below is an outline of the new rules and how things are going to work to keep it fun and friendly for all. An official whitelist thread will follow within a day or two - we are just finalizing some things - and I wanted to give you all a chance to read over and understand the rules BEFORE things go live. If you have questions about these rules, please feel free to ask below and we will attempt to clarify.
RULES:
Some more details:
Rollback setup: 10 complete world backups, new one taken every 12 hours. Rollback and logging plugin to cover interim time. (Rollback plugin _may_ not support all modpack blocks. If a significant # of blocks are not properly restored you can request a rollback of your region to the nearest 12 hour backup)
WorldGuard: There is NO worldguard on this server. It is not supported on Forge based installs, and while we are aware it can be made to work with things like BukkitForge, there are two reasons we're not going to try:
a. Mods. They break worldguard protection, so better to have proper rollback than try to prevent every possible type of circumvention.
b. Stability. If the support layer necessary for WG breaks... no more WG and we're just as far from home. If we don't rely on WG in the first place, we can just remove the support layer and the server should be functional again with minimal impact. Coupled with the new admittance rules (below) we hope the lack of WG won't be a problem.
This is the official whitelist thread for the new B-Team minecraft server. The rules are re-posted below for reference.
Here's how it will work: To get white-listed, there are three steps that may be completed in any order:
1. You need to have an existing whitelisted member vouch for you in this thread.
2. Reply in this thread and explicitly state that you have read the rules and agree to follow them.
3. FILL IN YOUR MINECRAFT USERNAME IN YOUR FORUM PROFILE.
I realize that #1 is dependent on an existing list of whitelisted people, so here is what will happen:
Those that previously replied to the B-team announcement (and any of our existing game admins) may be instantly whitelisted without vouch by completing step 2 above to get the pool started, as these seem to be our most interested members.
Hopefully that will be sufficient to get the whitelist vouch system rolling. If not, operators reserve the right to whitelist additional people as we feel necessary. We also reserve the right to deny whitelist applications if we feel it necessary as a result of someone's history.
Rules and Info:
(Modpack info here: http://www.technicpack.net/attack-of-the-bteam)
We know our minecraft servers have had some issues in the past and we hope this iteration irons out most of those issues with regards to griefing, performance, and us having to micromanage everything.
Below is an outline of the new rules and how things are going to work to keep it fun and friendly for all. An official whitelist thread will follow within a day or two - we are just finalizing some things - and I wanted to give you all a chance to read over and understand the rules BEFORE things go live. If you have questions about these rules, please feel free to ask below and we will attempt to clarify.
RULES:
- Standard Vault Server rules on behaviour apply.
- PVP is off. Don't be a douche and steal/destroy stuff that might belong to someone. If it's labelled and NOT marked as abandoned (see #8.3) it belongs to someone.
- Label your shit. If it's a small outpost, workshop or storage hut... put a sign on it to distinguish it from autogenerated stuff. Same goes for your main base.
- Griefing damage is dealt with on a regional basis. That means no individual item refunds - we will select a cuboid region and roll it back, but we are NOT going to entertain extensive requests to roll back the contents of 30 chests scattered here and there throughout your base. Either the entire encompassing cuboid gets rolled back within the capacity/parameters of the rollback plugin, or nothing. That said, the plugin is rather flexible depending on the situation - so we'll do our best but no guarantees. Overall, we want you guys to be happy and have fun, but we refuse to be micromanaging the server/players 24/7 and having it sap all our time.
- Griefs should be reported within a reasonable time frame for action, esp. if restoration affects others. If you come back after 2-3 weeks of absence to find your house destroyed, we'll do what we can, but no guarantees.
- If the affected region also has somebody else's stuff too... you need to work it out with them (i.e. give them a chance to move stuff they don't want to lose out of the region to be rolled back).
- Whitelist by vouch only. To gain access you must be vouched for by an existing whitelisted player. Ergo, don't vouch for people you don't know well enough to say they won't cause problems. Established community members may apply without a vouch initially, just to get this list started. Keep it reasonable - you can vouch for 1 or 2 friends at a time but we will likely not consider requests to have 10 friends whitelisted at once. Start with one or two and once they're established regulars you can vouch for some more.
- Preventing friend of a friend griefs: New admittees can't vouch for others until they are a reasonably-well known community member (i.e. they play regularly and have made some friends with the existing regulars)
- Try to keep our server resources in mind when building. If you plan on spending 4 days journeying 23,487 miles from spawn, then please don't make our map unmanageable and go play single player. Sure be 200-300 blocks away from the next guy, but if nobody can make it to your house to visit, then why are you playing on a multiplayer server?
- Land claims/how close is too close. (You can build a 50x50 wall (with signs) around your shit. If you want more than that... finish your 50x50 first. (i.e. no claiming massive chunks of land for a mega-base that you may never end up finishing.)
- Player spacing: Be respectful of others. Before you move in, talk to them and come to an arrangement about how far they want to expand vs. where you plan to build. Both sides are expected to be reasonable and accommodating BUT if a dispute ensues the following rule will be enforced: Allow a MINIMUM of 50 blocks between the edge of your desired area and that of a neighbour. We feel this is reasonable to allow for expansion but countermand land hoarding.
- Unless otherwise arranged, after 30 days of absence operators (and operators only) reserve the right to publicly declare your property abandoned. Abandoned property is free for raiding and/or squatting. This does not mean it becomes abandoned at 30 days and 0.00001 seconds automatically. We will still evaluate it on a case-by-case basis. 30 days is simply a written deadline we feel is reasonable.
- Vouching punishments to reflect the incident level:
- Vouch for a griefer, your vouching right is revoked.
- If someone you vouch for causes minor problems: temporary revoke.
- If someone you vouch for completely trashes the server... you could well be banned yourself.
- At the very least, stop and think about who you are vouching for.
- Vouch for a griefer, your vouching right is revoked.
- No free teleports and stuff. (This kinda falls under micromanaging but lava wants to say so explicitly)
Some more details:
Rollback setup: 10 complete world backups, new one taken every 12 hours. Rollback and logging plugin to cover interim time. (Rollback plugin _may_ not support all modpack blocks. If a significant # of blocks are not properly restored you can request a rollback of your region to the nearest 12 hour backup)
WorldGuard: There is NO worldguard on this server. It is not supported on Forge based installs, and while we are aware it can be made to work with things like BukkitForge, there are two reasons we're not going to try:
a. Mods. They break worldguard protection, so better to have proper rollback than try to prevent every possible type of circumvention.
b. Stability. If the support layer necessary for WG breaks... no more WG and we're just as far from home. If we don't rely on WG in the first place, we can just remove the support layer and the server should be functional again with minimal impact. Coupled with the new admittance rules (below) we hope the lack of WG won't be a problem.
Last edited:
If it doesn't work, then it's on the user.
