✅
What this page is for
Send in useful information that helps players actually do something: install the game, find a spawn, fix a problem, understand a system, choose a server, or avoid wasting time. That is the bar.
What We Want Most
Not every contribution needs to be a full article. Some of the best submissions are a correction, a better route, a cleaner explanation, or a screenshot that makes a confusing mechanic obvious. The common thread is simple: it needs to make the site more useful for real players.
High priority
Corrections
Wrong version info, outdated mechanics, bad spawn advice, broken links, or anything that could mislead someone.
High priority
Missing practical detail
Spawn conditions, item sources, loader quirks, mod conflicts, command changes, or steps people always get stuck on.
Wanted
Good screenshots
Clear in-game screenshots showing the mechanic, menu, block, path, or result people need to see.
Guide ideas
New page concepts, comparison pages, utility pages, FAQ pages, item guides, route pages, setup pages, or addon roundups that would genuinely help players.
Server and addon tips
Hidden gems, compatibility notes, setup gotchas, quality-of-life addons, or honest warnings about stuff that sounds good but is a pain to use.
Player-tested methods
Fastest ways to do something, efficient hunt loops, breeding shortcuts, route improvements, or ways to avoid common waste-of-time mistakes.
Clarifications
Places where the official info is vague, the community is confused, or multiple systems overlap in a way that needs a cleaner explanation.
The Quality Bar
CobbleDex is not trying to be a messy wiki clone or a generic SEO dump. The goal is clean, practical, readable pages that answer what a player is actually trying to do. That means the best submissions are specific, grounded and player-focused.
“Use Poké Snacks” is weak. “Use Electric Poké Snacks in plains at dusk for Pikachu hunts because the spawns stay cleaner” is useful.
🧪
Only send things you’ve actually tested or verified
Guesses, rumours, or “I think this works” are fine as ideas, but label them clearly. Don’t send theory as fact.
🧭
Explain the player goal
Say what problem the info solves. Is it faster, easier, safer, cheaper, more consistent, or just less confusing?
📷
Screenshots should prove something
Best screenshots show the actual menu, biome, block, item, route, or result. Pretty screenshots are nice, proof screenshots are better.
No filler intros, no padded fluff, no “ultimate complete best ever” language unless the page genuinely earns it.
💡
The easiest way to make a contribution good
Write it like you’re helping a mate who is already in-game and trying to solve the problem right now.
What Not to Send
Not every submission helps. Some things actually make a guide worse by bloating it or muddying the answer. These are the kinds of contributions that usually do not make the cut.
Long intros that say nothing, obvious filler, or paragraphs that sound dramatic but do not help the player do anything.
❌
Unverified numbers stated as fact
If rates, odds, compatibility or mechanics are estimated, say that clearly instead of presenting them as nailed-on fact.
Useful interpretation beats copied information. The site should explain things better, not just repeat them.
❌
Server drama, callouts, or gossip
Keep it about gameplay, setup, clarity, quality, and player usefulness — not personal beef or community nonsense.
The Best Kinds of Contributions
If you’re not sure what to send, start with one of these. They fit the site best and are easiest to turn into genuinely good pages or upgrades.
Crash fixes, install problems, mod conflicts, bad settings, broken mechanics, missing items, or setup mistakes players keep making.
Best places to do something, fast loops, efficient routes, and methods that save time versus wandering around blind.
A vs B decisions, best starter choices, loader decisions, modpack choices, server types, addon alternatives, or trade-offs people actually care about.
Breeding, evolution, snacks, apricorns, balls, drops, berries, held items, friendship, utility blocks, or anything that needs a cleaner explanation than the average wiki page gives.
How to Submit Something
You do not need to package it perfectly. Just make it easy to understand, easy to verify, and easy to turn into a page update or a new guide. The cleaner you make it, the faster it can become something useful.
Step 1
Say what it is
Start with the page name, mechanic, problem, server, addon, or guide idea you’re submitting.
Step 2
Explain why it matters
Say what player problem it solves or what it improves compared to what is already on the site.
Step 3
Add proof or detail
Include version, loader, server name, screenshot, route note, or exact steps so it can be checked properly.
📌
You can also send partial stuff
A rough note, a screenshot with context, or a “this section is wrong and here’s why” message is still useful. It does not need to arrive polished.
Good Submission Examples
These are the kind of submissions that are actually worth their weight because they can become a better page almost immediately.
✅
“Your Shiny Hunting page says X, but on 1.7.3 Electric Snacks worked better for me in this biome because the spawn pool stayed narrow. Here are two screenshots.”
Specific, version-aware, and backed by proof. Great submission.
✅
“This server’s custom gyms are good, but their listed IP changed and your page is out of date.”
Simple correction, very useful, easy to fix.
✅
“Apricorn farming is much easier if you do this route first. Here’s why it beats the random wandering method.”
Player-tested improvement with a clear reason it helps.
✅
“You should make a Held Items guide because these five items keep confusing new players, and here’s the short version for each.”
Strong page idea because it is anchored to real player confusion.
Where to Send It
This page is designed so you can drop in a contact method later without rewriting the whole site. Use whatever channel you want to make primary — email, Discord form, Google Form, or a direct site form.
Form option
If you want cleaner submissions, replace one of the boxes above with a Google Form or site form link and keep the same submission format.
Correction option
You can also add a simple “Report a correction” button to big pages later and link it back here.
Found something useful?
Send it in. The best contributions are the ones that save other players time, confusion, failed installs, bad routes, or wasted grinding.
Quick Questions
❓
Do I need to write a full article?
No. A correction, route note, screenshot, or page idea is enough if it is useful.
❓
Can I send a server or addon suggestion?
Yes — especially if you can explain why it stands out, who it suits, and what makes it better or different.
❓
What if I only know one small thing is wrong?
That is still worth sending. Small fixes keep pages trustworthy.
❓
Can I suggest a whole new page?
Absolutely. Just explain the player intent behind it so it is clear why the page should exist.
