Jump to content

Welcome to Obsidian Forum Community
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!

Loot on Shipwreck location yields nothing

  • Please log in to reply
1 reply to this topic



    (4) Theurgist

  • Members
  • 360 posts
  • Steam:Kill it with fire!
  • Deadfire Backer

Sometimes loot you find in Shipwrecks don't yield what they say they do.


  • Wrapped up Poko Kohara and saw a Shipwreck off the coast. I went to it and got a few items, including a cannon
  • There was just the top line of the description, though, missing the "has been added to your stash" (or similar wording) and missing the clickable link to the found item
  • I checked the ship (H) before and after, and I had 2 Iron Thunderer cannons both before and after (no others), so I can't have gotten a new one
  • Tried to reload to see if it would reproduce, since I quicksaved just prior (I quicksave ALL.THE.TIME.EH!), but these things are very random. However, after a few tries a similar situation repeated, though this time with what was called an "adventurer supplies". No idea what that is. But I couldn't see anything new in the inventory of either my packs or the ship, so I reckon nothing 'popped up'.
  • It was the same here, as you can see from the screenshot. The first line is present, but not the second with the clickable link

Download the savegame and try, and quickload until this happens for you.

Savegame (expires in 7 days): https://we.tl/Z1WcJid2pZ


Attached File  Advcenturing supplies.jpg   79KB   0 downloads



Btw, in one of the reloads I got both lines when finding a cannon, which was an Iron Thunderer, so apparently it does work - some of the time.



    QA Tester

  • Developers
  • 802 posts
Thank you for taking the time and notifying us regarding this issue :) I do believe this to be fixed in the most recent patch 1.1. Should you have any additional questions let us know!

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users