How to Build for Free
Link your Discord for 25 credits, earn up to 75 more every day by being active, and make every credit go further with small, specific prompts.
You don't need a card to build your first mod. Credits come from being part of the Discord, and they never expire. Here's every way to earn them, and how to stop wasting them.
#Link your Discord
Join the Player Games Discord and link your account. You get 25 credits the moment the link completes. That's enough to build and test a small mod.
Start from the Free credits button in Creator Hub, or go straight to the Discord link page. Your Discord account has to be at least 30 days old, which keeps people from farming throwaway accounts.
#Earn every day by being active
Once you're linked, the bot watches the server and pays you for taking part. You can earn up to 75 credits a day, every day.
What counts:
- Showing off a build in the showcase channel with a screenshot or clip
- Commenting on other people's showcases
- Helping someone who's stuck with a real answer
- Introducing yourself when you join
- Sharing a mod idea or joining a conversation
What doesn't count: one-word replies, spam, and reposting the same thing. The bot pays for the kind of activity a good server member does anyway.
A screenshot is worth the most
Showcase posts pay the most of anything on the list. Build something, take a screenshot of it in-game, post it. You'll get feedback and credits in the same move.
#Giveaways and weekend events
We run giveaways in Discord and bonus-credit events on weekends. They're announced in the server. If you're active anyway, you'll see them.
#If you do have a card
Linking a payment method adds 150 credits. Nothing is charged, now or later, unless you decide to buy a pack. It's there for people who want a bigger first project without waiting on daily credits.
Credit packs start at $8 if you outgrow the free path. Most people building a few commands and items never do.
#Make credits go further
The free path gives you plenty if you don't burn it on vague prompts.
- Ask for one feature at a time. A small, specific prompt builds faster and comes out right more often than a five-system wishlist that has to be redone.
- Iterate in the same project. Fixing a build with a follow-up message is cheaper than regenerating from scratch. What to say when the first build isn't right shows how.
- Test before you regenerate. Put the build in a test world and confirm what's actually wrong. Half the time the prompt was fine and the install wasn't.
- Pick Weft for simple command mods. It's our own model and the cheapest option in the picker. For a /home or /kit plugin it's the right choice. For big original mods, use the standard option.
- Write the numbers down. Every cooldown, chance, and stat you specify up front is one less follow-up message.
Free-path checklist
Build it yourself
Turn an idea into a working Minecraft mod
Describe it in plain English. Download the build. Drop it in your mods folder. No coding.
Start building