There is no complete source-verified list of every skin in the material reviewed for this page. The public achievements confirm legendary skins connected to slot-machine play, and Patch 1.0.5 fixed how those skins display in 4K. Names, counts, odds, machines, and complete weapon or boat categories remain pending confirmation.

The direct answer about the complete skin list

A complete skin guide needs the exact in-game name, item type, acquisition source, rarity label, and version for every row. The official store, news, and achievement pages do not expose that full catalog. Trailer frames and community thumbnails are not enough to identify every entry safely.

Pending confirmation: total skin count, full names, complete weapon-skin roster, boat-skin roster, rarity structure, reward odds, and machine locations. This page documents what is verified and provides a capture method. It does not fill missing cells with visual guesses.

Legendary skins and the official achievement

The public Steam achievement list establishes legendary skins as a tracked reward goal. It also connects the goal to slot-machine play. That is official evidence for the category and route, but not for every reward inside the pool.

Check the current achievement description in Steam and compare it with the reward screen. Record the exact skin name only when the live interface shows it. A community claim can guide a test, but the captured result should support the final entry.

Patch 1.0.5 and the 4K display fix

Patch 1.0.5 corrected 4K display behavior for slot-machine skins. This matters when a launch-week screenshot looks cropped, low quality, or visually inconsistent. A presentation bug should not be mistaken for a different skin.

Update the game before capturing a collection. Record resolution only when investigating a rendering issue, not as a rarity property. If an old and new screenshot differ, prefer the current patched display and keep the earlier version labelled.

Weapon skins, boat skins, and tracking demand

Players search for broad skin categories, including weapon and boat customization. Search demand identifies a useful database shape but does not prove a complete set. Each category must be verified through the live customization or reward interface.

Keep item types separate. A skin with a similar theme on two objects should not be merged unless the game uses the same internal name and unlock. Record shared themes as notes after the individual entries are secure.

Fields for a trustworthy skin database

Capture displayed name, object type, rarity if shown, acquisition source, machine or challenge, game version, and a screenshot reference. Add whether the reward registered in an achievement or collection screen. Leave probability blank unless an official source discloses it or controlled testing supports a carefully labelled estimate.

For machine rewards, record the visible wager and result without implying a guaranteed path. For challenge rewards, record the exact requirement text. This makes each row reproducible and separates official wording from community observation.

Check progression before gambling catches

The official game loop lets players sell, collect, or gamble catches. A fish needed for a local task or Fishipedia should not be risked only because the player wants a skin. Confirm quest, collection, and replacement needs before using a machine.

Boss trophies should be returned rather than treated as ordinary meat. Drip creatures can also have separate collection value and may not satisfy normal quests. These verified distinctions make a pre-wager inventory check essential.

Complete names, odds, and locations pending confirmation

Pending confirmation remains the honest state for the complete skin roster and reward model. The reviewed sources do not support exact odds, guaranteed spins, pity rules, or every machine location. A full table must wait for current-game capture and reconciliation.

Date every verified reward and monitor official news for changes. If Patch 1.0.5 or a later update alters display or tracking, annotate the affected entries rather than silently rewriting history. That source trail keeps a future collection database dependable.

To verify completion, capture the full customization list in a current build and compare it with every recorded reward. A skin visible in a video but absent from the live list should remain unresolved. This check protects the final roster from duplicate themes, outdated display bugs, and guessed names.