Chests Everywhere

Chests Everywhere

Every chest you own, from wherever you are standing.

What this does

• []Press B. Anywhere. The chest you used last opens right where you are.

  Press it again to close.[/]

  []Two dropdowns above the chest. One lists every area where you have a

  chest, and marks the one you are in. The other lists the chests there, by name,

  by where they are, and by how full they are. Pick an area and its first chest

  opens; pick a chest and the window is that chest — no closing, no walking.

  A chest you walk up to and open yourself is left exactly as the game made it.[/]

  []Named chests come first. If you called one "ores", it says ores.[/]

  Inspired by Chests Anywhere

  If you have played Stardew Valley you have probably used

  Chests Anywhere by

  Pathoschild.

  ---

  Before you install

  Back up your saves. Not because this mod is known to eat them — it is

  careful, and it refuses to write a chest back if anything about the contents

  does not add up — but because it reaches into saved chest data, and that is

  worth a copy of your save before you find out.

  They live in:

  %USERPROFILE%\AppData\LocalLow\Pixel Sprout Studios\Sun Haven\Saves

  Installation

  • []Install BepInEx 5 (x64) and run the game once.[/]

    []Put ChestsEverywhere.dll into Sun Haven\BepInEx\plugins.[/]

    []Play. Press B.[/]

    Good to know

    • []Works with Bottomless Chest [/]

      []Empty areas are left out. The game pre-places a chest in scenes you

      may never live in, and a list full of places with nothing in them helps nobody.

      Where you are standing is always listed.[/]

      []Hoppers, animal feeders, bank are left out of the list:  There is a setting to

      include them.[/]

      []Not compatible with Senpai's Chest — both mods rebuild the same chest

      window, so use one or the other.[/]

      []Multiplayer has not been tested.[/]

      Something broke?

      Open the settings file at

      BepInEx\config\evilshira.sunhaven.chestseverywhere.cfg, set

      VerboseLogging and LogChestIds to true, reproduce the

      problem, and post BepInEx\LogOutput.log with your report. That log tells

      me almost everything I need.