Before you connect
A little preparation makes the first visit more useful. Work through these five checks before committing to a large project.
- PvP, stealing and griefing are allowed on JustVanilla. Read the rules for the limits, and make sure friends understand them too. The Overworld, Nether and End never reset, with no exceptions, but there are no claims: builds and belongings are not protected from other players.
- Check your edition and version. JustVanilla currently runs Minecraft 26.1.2. Players can also join using older versions and the newest version. The team updates as soon as it is able. Identify whether you are launching Java or Bedrock and note the exact client version. If connecting fails, include those details when asking for help.
- Check allowed mods. Use the published Allowed Mods list; anything not listed must be approved by management before use. Read feature limits as well as client names.
- Copy the correct address. Java Edition: mc.justvanilla.net. Bedrock Edition: bedrock.justvanilla.net, port 19132. Use the joining guide for the menu steps; leave out https:// and website paths.
- Choose one small first-session goal. Explore a manageable area, collect supplies for a small shelter or decide what you would enjoy building. You do not need to finish a permanent base on your first visit.
After joining: make one manageable plan
Food can be hard to find around spawn. Watch your hunger and make finding food an early priority before travelling farther.
Take stock before committing to a long trip or a large build. What do you already have, what will your next task need, and how will you get back? There are no teleport commands to skip the return journey.
Keep the first goal small enough to change if the surroundings or other players make it impractical. Adjust your plan to what you actually find.
- Watch your hunger and prioritise finding food before travelling farther. Plan around the supplies you actually have.
- Choose a finish line you can recognise: gather the supplies for one part of a shelter, look around without committing to a base site, or write a short plan for a later build.
- Check what you need for that goal before leaving: useful tools, food and any materials the task depends on. Take account of what you actually have rather than assuming supplies will be waiting along the way.
- Decide what you are willing to carry and lose. Other players may attack or steal within the rules; carrying everything does not make the trip safer.
- Keep a private note of how you intend to return. Do not post base coordinates or screenshots that reveal them publicly.
- Stop and reassess when the task changes. Missing an essential item is a reason to reduce the goal or make a deliberate supply trip, not to turn a short visit into an unplanned expedition.
Choose your next step from what happened
You do not have to solve every problem in one session. Use the next step that matches the problem you actually encountered.
| What you notice | A useful next step |
|---|---|
| Your small goal is finished | Note one next task and the supplies it needs. Leave the larger project for a planned session. |
| You are running short of supplies | Make the goal smaller or plan a return trip before carrying on. Avoid relying on a teleport command. |
| A player attacks or takes belongings | PvP and stealing are allowed. If you think a specific rule was broken, check the relevant rule and ask staff. |
| You are unsure about a mod or planned action | Check Allowed Mods and the full rules. If the answer is still unclear, ask staff before using it or acting. |
| You cannot stay connected | Record the exact error, edition and version. Use the connection checklist rather than guessing that you were banned or the server is offline. |
Travel options can wait
You can plan a first visit without knowing how to access the Nether roof. Nether-roof travel is optional; before using it, know where an existing usable return portal is or carry the materials needed to build and light one. This checklist does not teach roof access.
Ask for help without exposing private details
For a rule question, say what you intend to do and which rule is unclear. For a connection problem, include your edition, exact client version and the error message. Keep passwords, account tokens, sign-in codes and private base locations out of the report.
Use the JustVanilla Discord for player help. The website’s Support page is about funding the server; it is not a troubleshooting form.
Leave a useful note for next time
Write down: what I completed; the next small task; supplies I need; and any rule question to resolve first. Keep location notes private. A clear next step is more useful than committing to a huge project before you know whether this style of survival suits you.