MyWorlds tasks

Task guides and troubleshooting for MyWorlds. Check the installed release before changing configuration or data.

Keep an unused MyWorlds map unloaded without deleting its data

MyWorlds remembers loaded worlds for future starts. Use its load state to close an unused event map after checking its players and routes. Preserve its folder and configuration so the next event can reopen the same map with its existing builds.

Work through the change

  1. Record the world name from the MyWorlds listing and inspect any players, portals or scheduled actions that still use it. Keep a verified backup and a safe lobby destination.
  2. Use the documented evacuation or normal player exit route before unloading. Tell participants why the map is closing and avoid forcing an unload while they are actively building.
  3. Run the installed world unload command for that named world and read the result. If it refuses, inspect the reported dependency or player state instead of moving the world directory by hand.
  4. Check the world list after the next planned restart and test that the lobby still works. Hide or label the closed map’s public menu route without deleting unrelated portal definitions.

Check the result

The closed world should remain available on disk but absent from the loaded-world list until you reopen it. Check whether another plugin independently loads the same map. MyWorlds startup behaviour cannot prevent a separate scheduled loader from issuing its own load request.

Confirm nobody is currently building or travelling there before unloading. A quiet player list does not reveal every scheduled integration. Keep the map’s folder and import information intact so the next event can load the same world rather than accidentally create a fresh one.

Recover or stop safely

Use the documented load command for the existing folder when reopening, then verify its landmarks and portal routes before inviting players. Retain any custom generator requirement with the map notes. Do not create a replacement map just because the closed world is currently unloaded.

For the broader setup, read Load an existing world safely with MyWorlds. Check the installed plugin version before applying syntax from the official MyWorlds documentation.

Set a MyWorlds spawn facing away from a dangerous landing edge

A safe position and a useful facing direction both matter at a world spawn. MyWorlds uses the player’s position and rotation when setting a spawn. Prepare the landing surface before changing it so the test does not rely on an unsafe teleport.

Work through the change

  1. Record the existing world spawn coordinates and orientation, then mark the new landing platform. Confirm the world name through MyWorlds information rather than a decorative display alias.
  2. Stand on the safe platform facing the intended path and use the documented setspawn control for that world. Avoid setting the target while flying over an unfinished floor.
  3. Test the world-spawn route with an ordinary account. Remain still after arrival and check whether a portal, last-position feature or another spawn plugin moves the player again.
  4. Repeat from a different source world and inspect the approach in both first-person and third-person views. Keep enough headroom and walking room for players who arrive before the area finishes loading.

Check the result

The player should arrive on solid ground facing the intended route, with the same map identity as before. A valid bed or a return-to-last-position route may intentionally choose another location. Record those routes separately so staff do not undo a correct spawn to fix another feature.

Test the landing without flight and with the same game mode used by visitors. Facing is part of the result: a safe standing block can still point a player toward a drop or a trigger. Photograph the approach route as well as the final spawn block.

Recover or stop safely

Restore the recorded old spawn from its safe position if the trial is unsuitable. Keep a console or staff teleport recovery path while testing. Do not delete player spawn records or rename the world folder to correct a world-specific landing direction.

For the broader setup, read Load an existing world safely with MyWorlds. Check the installed plugin version before applying syntax from the official MyWorlds documentation.

Check MyWorlds world entry permissions without granting teleport administration

Entering a world and teleporting other players are separate permissions in MyWorlds. Give players only the route they need, then test the exact portal or command they use. An administrator’s successful teleport can hide a missing entry permission.

Work through the change

  1. Record the source world, target world and normal player route. Confirm the target is loaded and the test player’s role does not contain operator status or a broad administrative grant.
  2. Read the documented world-enter and world-specific teleport permissions for the installed MyWorlds release. Check inherited grants before adding a narrowly scoped test permission.
  3. Attempt the same route with an allowed test account and a denied control account. Capture the messages and note whether denial occurs before or after a portal action starts.
  4. Grant only the missing approved entry or self-teleport capability to the trial role. Retest another restricted world to confirm the change did not give access beyond the intended target.

Check the result

The allowed role should enter the selected world while the control account and unrelated restricted world remain denied. Confirm that the player cannot teleport other people merely because it can use its own world route. Keep the actual successful grant with your access policy.

Compare entry through the normal public route with a direct staff command. These exercise different permissions and can produce apparently contradictory results. Keep the player’s effective nodes and destination world name together, particularly when the visible world label differs from its internal name.

Recover or stop safely

Remove temporary permissions if the result differs from policy and restore the previous role assignment. A failure at a world-specific portal can need a portal permission rather than teleport administration. Do not resolve a narrow admission problem by enabling per-world operator behaviour for ordinary players.

For the broader setup, read Load an existing world safely with MyWorlds. Check the installed plugin version before applying syntax from the official MyWorlds documentation.

Measure the effect of keeping a MyWorlds spawn area loaded

Keeping a spawn area loaded can trade faster arrival for ongoing memory and tick work. Test the option on one map with comparable player activity. A quiet server at one timestamp does not show what will happen during a busy event.

Work through the change

  1. Record the current spawn-loaded setting, online player count and a short baseline of memory and tick measurements. Identify farms, entities or redstone around the spawn that could keep doing work.
  2. Read the keepspawnloaded behaviour for your installed MyWorlds and Minecraft versions. Choose a low-traffic interval and change only the named world’s setting through the documented control.
  3. Wait for measurements to settle, then have one ordinary player leave and return to the world. Compare arrival behaviour and server metrics with the baseline under similar conditions.
  4. Repeat the observation without new terrain generation or a map render running. Record the result over several samples so a backup or garbage collection pause does not dominate your conclusion.

Check the result

The measurements should show whether the change helps this particular spawn enough to justify its cost. Do not claim that less reported memory automatically means smoother play. Version-specific server loading rules can limit the option’s effect, so retain the installed versions in the notes.

A lower memory reading after changing spawn retention is not sufficient proof on its own. Compare the same observation window and player population. Current Minecraft and server implementations can change spawn-loading behaviour, so confirm what the installed MyWorlds build actually supports before promising a resource saving.

Recover or stop safely

Restore the original world setting if arrival worsens or background work rises. Keep the area’s farms and entities unchanged during the trial. If the setting has no effect on your server version, investigate its current loading rules rather than changing several performance plugins at once.

For the broader setup, read Load an existing world safely with MyWorlds. Check the installed plugin version before applying syntax from the official MyWorlds documentation.

Lock time in one MyWorlds lobby and verify other maps keep their cycle

A lobby can use a fixed daytime scene while survival maps keep normal time. MyWorlds provides a world-specific time control, but a scheduled command or event plugin can still change the visible result. Record each actor before applying a lock.

Work through the change

  1. Identify the lobby’s managed name and record its current time policy. Check for existing day-cycle gamerules or schedules that would make a short trial misleading.
  2. Read the installed MyWorlds time command and its documented lock syntax. Apply the intended fixed time to the lobby, explicitly naming the world when the command supports that target.
  3. Wait through an interval long enough to observe a normal day-cycle change. Compare the lobby with a survival control world while keeping weather and resource-pack settings unchanged.
  4. Test after the next planned restart and through the normal player arrival route. If only one client sees a different time, inspect client-specific or region time features before reapplying the world command.

Check the result

The lobby should retain the chosen time and the control world should continue its prior cycle. Check both the reported world time and the view from ordinary accounts. A clear sky alone does not prove that time is fixed, since weather is a separate property.

Check a neighbouring map at the same real time to establish that the lock is local. If a personal-time plugin also affects the account, repeat with an ordinary visitor. Keep cosmetic sky appearance separate from mechanics that depend on the server’s actual world time.

Recover or stop safely

Restore the documented previous time policy when the lock no longer serves the lobby. Remove only a temporary schedule you added for the trial. Keep the original value in the event notes so a future staff member does not need to guess how to resume the cycle.

For the broader setup, read Load an existing world safely with MyWorlds. Check the installed plugin version before applying syntax from the official MyWorlds documentation.

Set a MyWorlds admission limit for a small event map

A per-world player limit can keep an event area manageable without changing the server’s overall slots. Check how MyWorlds handles additional arrivals and reconnects before relying on the limit to protect a live competition.

Work through the change

  1. Record the world’s current limit and choose a safe lobby for players who cannot enter. Inspect the bypass permission for staff roles and use ordinary accounts for capacity tests.
  2. Apply a small trial limit using the documented MyWorlds playerlimit control. Keep the main server slot setting unchanged so the result tests only this world’s admission rule.
  3. Fill the event map with test accounts and attempt one extra entry through its normal portal. Record the denial or fallback destination rather than assuming it matches a direct command test.
  4. Test reconnect behaviour and then an authorised staff bypass. Check that the lobby and another event world remain accessible under their existing limits.

Check the result

The world should admit only the intended ordinary participants while staff access follows your recorded bypass policy. Confirm that rejected players land safely rather than becoming stuck in a portal loop. A world limit controls admission; it does not reserve CPU or RAM for the map.

Test denial through the event’s real entrance rather than only by command. The player must have a safe place to remain when capacity is reached. Record what happens on reconnect too, because a world admission cap should not leave an existing participant stranded without staff assistance.

Recover or stop safely

Restore the earlier limit after the trial and remove temporary bypass grants. If you need to lower a live limit, announce the change and use a documented evacuation path where necessary. Do not kick everyone or unload the map without checking ongoing player progress and saves.

For the broader setup, read Load an existing world safely with MyWorlds. Check the installed plugin version before applying syntax from the official MyWorlds documentation.