Join Discord first
Open the Bindspire SMP Discord. You can install the pack before posting, but the whitelist step happens in Discord.
Bindspire SMP main server
Homestead
Build a cozy life in a beautiful survival world with voice, claims, chunkloading, and distant horizons.
Critical server info
Server details
- Minecraft version
- 1.20.1
- Loader
- Fabric
- Recommended client version
- Homestead 1.3.6
- Server pack version
- Homestead 1.3.6
- Latest known pack version
- 1.3.6
Server address
Where to go in Discord
- Server channel
- #homestead
- Whitelist channel
- #whitelist
- Help channel
- #join-help
- Introductions
- #introductions
- Arrivals
- #arrivals
Whitelist is staff-mediated. Post your Java username in #whitelist and a human will pick it up.
Install
Install the Homestead pack
Use the version listed above. Newer is not always better on a multiplayer server.
-
-
Install the pack
Use the CurseForge App if you don't already have a launcher. Prism Launcher and the Modrinth App are also officially supported by Homestead.
-
Choose the Bindspire-approved version
Match the recommended client version above. Do not auto-update past it unless staff confirms the server has updated.
-
Allocate memory
Give Minecraft 6 GB minimum, 8 GB recommended. Lower allocations will cause stutters and crashes on Homestead.
-
Launch once
First launch can take a few minutes while shaders, mods, and assets compile. Let it finish. If it crashes immediately, check Java 17 and your launcher's memory setting.
-
Post your Java username for whitelist
Post your exact Java Edition username in #whitelist on Discord. Staff handles whitelisting; do not run any commands yourself.
-
Join the server and say hi
When staff replies, the server address is shared. Connect, then post in #arrivals so we know you're in.
Before you ask for help
Common mistakes
Most join issues are one of these.
- Updating the pack past the server version. Newer files do not always match what the server is running.
- Allocating less than 6 GB of RAM. Homestead is heavier than vanilla Minecraft.
- Posting a username with a typo or stylized characters. Whitelist is exact.
- Trying to connect before staff replies. The server address is shared after whitelisting.
- Using Java 8 or 11. Homestead expects Java 17.
Troubleshooting
When something breaks
If you're already stuck, find your symptom below.
Issue
Cannot connect / "not whitelisted" message.
- Likely cause
- Your username is not on the whitelist yet, or the server address you used is outdated.
- Fix
- Confirm staff has whitelisted you in Discord, double-check the server address shown for your status, and try again.
Issue
Wrong modpack version / missing mods on join.
- Likely cause
- Your installed pack version does not match the server's current version.
- Fix
- Match the recommended version listed on the Homestead page. Do not auto-update unless staff confirms the server has updated.
Issue
Whitelist not active because of a username typo.
- Likely cause
- The Java username posted in #whitelist did not exactly match your real Mojang/Minecraft username.
- Fix
- Post your exact Java username again in #whitelist so staff can re-add it. Capitalization counts.
Issue
CurseForge or launcher won't launch the pack.
- Likely cause
- Corrupt install, account not signed in, or invalid install folder path.
- Fix
- Repair the install from the launcher, confirm your Minecraft account is signed in, and avoid install folders with special characters or OneDrive sync.
Issue
Wrong Java version (Java 17 required).
- Likely cause
- The launcher is using a bundled or system Java that is not Java 17.
- Fix
- Set the pack profile to use Java 17. Homestead's official guide calls out Java 17 for startup crashes.
Issue
Memory allocation too low (allocate 6-8 GB).
- Likely cause
- Default 2-4 GB is not enough for a modded pack like Homestead.
- Fix
- In your launcher's per-pack settings, allocate 6 GB minimum, 8 GB recommended for the Homestead client.
Issue
Shaders or low-end device causing crashes/lag.
- Likely cause
- Shaders, ultra render distance, or outdated GPU drivers on a low-end device.
- Fix
- Disable shaders, lower render distance, and update GPU drivers. The pack should be playable without shaders.
Issue
Server appears offline because it just restarted.
- Likely cause
- Modded servers can show online before they are fully ready after a restart.
- Fix
- Give it a minute or two and try again. If it stays unreachable, check Discord for a status note.
Stuck? Send these in #join-help.
A complete first message saves a dozen follow-up questions. Post these in one go.
- Minecraft username
- Launcher used
- Pack version
- Screenshot of error
- Latest log or mclo.gs link
- What you already tried
FAQ
Quick answers to the questions we get most.
Why Discord first?
Discord is where staff whitelists you and where you can ask for help. You can install the pack before joining Discord, but the whitelist step happens there.
Why whitelist?
Whitelist protects builds, inventories, and server performance. We want new players. We just don't want anonymous chaos.
Can I use Prism Launcher?
Yes. Homestead's official guide supports Prism Launcher, the Modrinth App, and the CurseForge App. Pick whichever you already use.
Can I use the Modrinth App?
Yes. The Modrinth App is officially supported by Homestead. Match the recommended version on this page.
Do I need Java 17?
Homestead's official install guide calls out Java 17 for startup crashes. Use Java 17 for the client.
Can I update the pack to the latest version?
Not automatically. Match the version listed on this page. Newer is not always compatible with the running server. Staff updates this page when the server version changes.
Where do I ask for help?
In #join-help on Discord. Bring your username, launcher, pack version, and either a screenshot of the error or a log link.
Still stuck?
Post in #join-help with your username, launcher, pack version, and a screenshot or log link. Staff will pick it up.