Fix typos and update warp rules: correct spelling, adjust offline removal threshold from 30+ to 45+ days, align warp check frequency to bi-weekly, and extend issue resolution timeline to 2 weeks.
This commit is contained in:
1 parent
a4adff3845
commit
0c0fc8a8fb
1 file changed
+8
-7
@@ -47,7 +47,7 @@
|
||||
<h2>Warp Requirements</h2>
|
||||
<p>You need to be the owner of the claim your warp is placed in. It should look good, and be as finished as
|
||||
your warp type allows you to have it. Safety is an important aspect as well, visitors should not be
|
||||
accidently dying by falling in dangerous areas or having mobs spawn on them. Phantoms are an exception to
|
||||
accidentally dying by falling in dangerous areas or having mobs spawn on them. Phantoms are an exception to
|
||||
this rule as you can't easily prevent those spawns. Your warp should be in one claim*, and divided with
|
||||
subclaims if you need to allow different levels of trust in different areas (house plots in towns, shop
|
||||
plots in malls, etc).</p>
|
||||
@@ -64,8 +64,7 @@
|
||||
chunkloaders.</p>
|
||||
<p>It's important to make sure your warp is as lag friendly as possible. Our rules on lag can be found here on
|
||||
the <a [routerLink]="['/lag']">lag</a> page. If we find your warp creates more lag than necessary for its
|
||||
function
|
||||
we will deny the application.</p>
|
||||
function we will deny the application.</p>
|
||||
</div>
|
||||
<div class="columnContainer">
|
||||
<div class="columnParagraph">
|
||||
@@ -115,16 +114,18 @@
|
||||
<p><span style="font-family: 'opensans-bold', sans-serif;">-</span> Smaller shop warps are limited to 1 shop
|
||||
per type. For example, only 1 warp for redstone-related shops.</p>
|
||||
<p><span style="font-family: 'opensans-bold', sans-serif;">-</span> In order to always keep our warps fair
|
||||
and updated, we will automatically remove a warp if the warp owner has been offline for 30+ days. We need
|
||||
to be able to contact our warp owners in a timely manner incase any issues with the warp happen to pop up.
|
||||
and updated, we will automatically remove a warp if the warp owner has been offline for 45+ days. We need
|
||||
to be able to contact our warp owners in a timely manner in case any issues with the warp happen to pop
|
||||
up.
|
||||
If we notice that a player is fairly inactive and another warp application comes in for a similar warp,
|
||||
the application will be more likely to be accepted if the warp meets all of our requirements. If you plan
|
||||
on being gone for an extended period of time, 14+ days, you can let a staff member know and they will note
|
||||
it down and try to work with you.</p>
|
||||
<p><span style="font-family: 'opensans-bold', sans-serif;">-</span> The staff team does weekly warp checks
|
||||
<p><span style="font-family: 'opensans-bold', sans-serif;">-</span> The staff team does bi-weekly warp
|
||||
checks
|
||||
to make sure our warps continue to stay up to meet our requirements. They will mail a warp owner if they
|
||||
notice an issue (low stock, sudden lighting issue, farm isn't working, etc.), and we expect all issues to
|
||||
be fixed within a week of receiving that mail. If an issue goes unfixed, we will remove the warp due to
|
||||
be fixed within 2 weeks of receiving that mail. If an issue goes unfixed, we will remove the warp due to
|
||||
the lack of upkeep. If the issue is something you need help fixing or you're unable to work on it during
|
||||
the week, you can reach out to any member of the staff team and they will work with you!</p>
|
||||
</div>
|
||||
|
||||
Reference in new issue
Block a user