search

nbusseneau / BetterCartographyTable

Valheim mod that allows precise control over sharing pins and map exploration via cartography tables. Supports private pins, public pins, and guild pins. Supports NoMap runs.
MIT License
1 stars 0 forks source link

Mod Conflict with EpicLoot Bounty/TreaureMap pins created by the Merchant on accepting Bounties/TreasureMaps #4

Closed Jester2020 closed 5 months ago

Jester2020 commented 7 months ago

When installed with EpicLoot the Icon and Name strings are hidden from the Bounty/TreasureMap Indicators on the map. It doesn't break the actual Bounty or Treaure Map just the map feature.

EpicLoot_MissingBounty Treasure_Icon Text

EpicLoot_WorkingBounty_IconandName

OrianaVenture commented 7 months ago

Confirmed the issue is happening on Epic Loot version 0.9.37 and Better Cartography Table version 0.2.0. If you need assistance with fixing mod compatibility please reach out to me as I am currently helping maintain Epic Loot.

nbusseneau commented 7 months ago

@OrianaVenture Thanks! I will have some time to look into this over the next week. I don't personally use Epic Loot, any tips on how to easily trigger / reproduce this situation?

Jester2020 commented 7 months ago

Hi, you will have to locate the merchant first. Then accept a bounty or buy a treasure map. It's consistent every time. You only need to install EpicLoot (turn on adventure mode) and your mod.

Jester2020 commented 5 months ago

any chance we'll see a fix for this? thanks

nbusseneau commented 5 months ago

Yeah I actually started changing how stuff works internally so that's it's less likely that it clashes with other mods (including this specific case here), however I don't have any ETA to give because I'm currently quite busy dealing with stuff happening over at the Hades II modding scene now that the game came out😅

Jester2020 commented 5 months ago

No worries, probably doesn't make sense to finalize the changes until they're verified against the Ashlands release. have fun with Hades II :D

nbusseneau commented 5 months ago

This should be fixed in version 0.4.0.