Weapons List: Build, Verify & Track Weapons

No verified Mycopunk weapons list exists yet — here's how to catalog, test, and track every weapon you find, with tables you can copy.

Why a Complete Mycopunk Weapons List Is Hard to Pin Down

You pick up something new mid-run, the numbers look decent, and you have about ten seconds to decide whether it replaces what's already in your hands. That decision is where a solid Mycopunk weapons list earns its keep — not as a trophy shelf of names, but as a decision tool you actually trust under pressure.

Right now, a complete and verified Mycopunk weapons list is genuinely hard to come by. Community reference pages go offline for maintenance, recorded footage reflects older builds, and a list that was accurate a month ago can quietly mislead you today. So rather than hand you numbers nobody can check, this guide teaches you how to build a Mycopunk weapons list of your own — one that matches your version, your platform, and the way you actually play.

The core principle is simple: every entry needs a date stamp and a way to verify it against your own screen. A list without a version number is a rumor with nice formatting.

The Fields Every Good Mycopunk Weapons List Needs

Before you record a single weapon, set up the columns. A sheet with the wrong fields forces you to re-test everything later, which is the most common way these projects die.

FieldWhat to writeWhy it matters
In-game nameCopy it exactly as displayed, including any prefixes or tier markersNear-duplicate names are the #1 source of confusing entries
CategoryUse the game's own label verbatim instead of inventing your own bucketsKeeps comparisons apples-to-apples when you sort
AcquisitionWhere and how you picked it upTells you whether you can get another one
Base statsEvery number shown before any upgradesYour only honest baseline
Upgraded statsThe same numbers after investmentShows scaling rather than starting power
Handling notesReload behavior, ammo economy, what you observedExplains why two similar-looking weapons feel different
Weight or slot costOnly if the interface displays itAffects what else you can carry
Version stampBuild string and datePrevents stale data from poisoning the sheet

Two tabs work better than one: a messy "raw" tab where you dump screenshots and quick notes, and a clean "reference" tab you only update once an entry has been tested. If you want a starting cross-check, a community weapons reference can save time on the capture pass — just confirm anything you copy against your own build before you trust it.

Build Your List in Four Passes

Trying to capture, test, and rank everything in one sitting is how people burn out. Split the work.

PassGoalWhat "done" looks like
1. CaptureGet every name you've encountered into the raw tabNo more empty rows for weapons you already own
2. RecordCopy base stats exactly, no rounding, no guessingEvery owned weapon has a complete base row
3. Field testRun each weapon through one identical encounterEach entry has a measured result, not an impression
4. ReviseRe-check entries after every patchNothing in the sheet contradicts what you see in-game

Tips that make each pass faster

  • Screenshot the stat panel, don't retype from memory. Photos are your backup when a row looks wrong three weeks later.
  • Name files by weapon and date so you can find the original evidence instantly.
  • Test in one repeatable encounter. Same enemy type, same distance, same approach angle, every time.
  • Record three clean samples minimum before you write a conclusion. One good run is noise.
  • Write "unknown" instead of a guess. An honest gap is more useful than a confident error.

Comparing Weapons Without Fooling Yourself

Most bad weapon advice comes from tests where two variables changed at once. Keep the following fixed and your comparisons will hold up.

Variable to controlHow to hold it steadyQuick check
Enemy type and countUse the same encounter for every testSame spawn, same order
DistancePick a fixed spot and shoot from itMark the ground if needed
Upgrade levelCompare like with like, base vs. baseNote upgrade tier beside every result
Player setupSame loadout and perks across testsScreenshot the build each session
Hit locationAim for the same body partNote any misses separately
Sample sizeThree runs, then averageDiscard obvious outliers, but write down why

If the game surfaces a damage number on hit, record it. If it doesn't, measure time-to-kill in a fixed encounter with a stopwatch or a recording you can scrub through. Either method beats "it felt strong," and both are repeatable by anyone reading your Mycopunk weapons list later.

Also separate burst from sustained performance. A weapon that wins a three-second exchange can lose a thirty-second one, and a single number in a spreadsheet hides that completely. Add a short note column for it.

A Version Log Keeps Your Mycopunk Weapons List Honest

Balance changes are the silent killer of weapon documentation. Every time the game updates, spend five minutes running the log below before you trust any old entry.

DateVersionEntry affectedWhat changedRe-tested?
2026-10-21Your current build string[weapon name]Damage readout shiftedYes — new row added
2026-10-21Your current build string[weapon name]No visible differenceNo — entry stands
2026-10-21Your current build string[weapon name]Handling feels differentYes — sample of three
2026-10-21Your current build string[weapon name]Can't confirm yetFlagged as unverified

Keep a plain-text export of your sheet somewhere offline. Reference pages and wikis disappear for maintenance more often than anyone expects, and losing months of notes because a site went down is a genuinely avoidable frustration.

Reading Someone Else's Mycopunk Weapons List Critically

You will find lists, rankings, and tier charts. None of them are useless — they just need to be read with the right questions in mind.

  • What version is it from? An undated ranking is a historical document, not current advice.
  • Are the numbers base or maxed? A fully invested weapon beating a fresh pickup tells you nothing about which to choose now.
  • Is the ranking measured or felt? Opinion is fine, but it should be labeled as opinion so you know what you're working with.
  • Is the roster short? A handful of examples is not a complete catalog. Treat anything missing as "not yet documented," never as "doesn't exist in the game."
  • Is the reasoning shown? A tier letter with no explanation can't be checked, so mark it unverified in your own notes and move on.

Five Mistakes That Quietly Ruin a Weapons Spreadsheet

MistakeWhy it skews your listFix
Comparing a fresh pickup to a fully upgraded favoriteUpgrades inflate every numberKeep separate base and upgraded columns
Testing against different enemies each runEnemy health and armor change the resultLock one repeatable encounter
Trusting an undated listA single patch can invalidate everythingLog the build string beside every entry
Reading a short list as the full rosterOmissions look like confirmationsWrite "not yet found" instead of "doesn't exist"
Ranking purely on feelMood and luck swing impressions hardPair every ranking with one measured number

The pattern behind all five is the same: the sheet drifts away from what you can actually verify. Once an entry stops being checkable, delete it or downgrade it to a note. A short, trustworthy Mycopunk weapons list beats a long, fuzzy one every time.

FAQ

Is there a finished Mycopunk weapons list I can just copy? Not one that's complete and verified as of this writing. Reference pages go offline and balance changes move the goalposts, so the reliable path is to build your own sheet and use outside sources only to speed up the capture pass. Confirm everything against your own build.

How often should I update my Mycopunk weapons list? After every patch, and any time the stat panel on a weapon you already own looks different from what you recorded. The version log above takes about five minutes and saves you from making decisions on stale numbers.

Do tier rankings in a Mycopunk weapons list mean anything? They can point you toward weapons worth testing, but a letter grade alone doesn't tell you the range it was tested at, the upgrade level, or the encounter. Treat ranks as a shortlist for your own testing rather than a verdict.

What's the most useful column in the sheet? The version stamp. Every other field can be corrected later; a missing build string means you can't tell whether a number is current or three updates old. Date everything, including your screenshots.