Hideout

"
Matt_Snow wrote:
Thanks a bunch, this cleared up my annoying issue! I started to get torqued as the map device being reverted would often eat maps I temporarily left. This exile is now sane.

My pleasure.
Actually, GGG (almost) fixed it since, so you can also go to another area right after having imported the hideout, it forces a copy from the instance to the database.
PLEASE QUOTE ME IF YOU ARE EXPECTING A REPLY
Last edited by xhul#1978 on Jan 17, 2020, 6:16:19 PM
This is still happening, even if you manually adjust the Masters. Now, if you load up a different Hideout (for example change to the Glacial Hideout from the Enlightened Hideout), when you switch back to the first Hideout all the masters and utility items (map machine, bench etc.) are reset to default locations.

Confirmed today, 29-3-2020.
Last edited by t0lkien#7048 on Mar 29, 2020, 8:21:10 AM
I would like to raise the profile of this problem.

It's clearly not new and the fix appears simple...
When a hideout is imported write the default object locations to the hideout database for that base.

Xhul also gave me the solution and I refined it (thank you Xhul)

After importing the hideout file reclaim all the decorations.
This leaves just the default objects.
Go around each object and move it left/right (or up/down) with the cursor keys.
This writes the object location to your hideout database.
Reimport the hideout file and hey presto they will no longer move between relogs or instance resets.

The reason for the reclaim reload steps is that it can be very difficult to select the default objects with a full loadout of doodads in your hideout.

This is not a viable solution if you have multiple hideouts on the same base.
For example I have 2 hideouts on the Coral Hideout base (and will eventually have 3).
Between switches I would have to move every default object and that does not allow for quick switching.

I have contacted GGG support directly on this problem and encourage that if you experience this problem to do the same.

Given the apparent age of this problem, the number of people reporting it and the apparent lack of a fix the bug report forum is ineffective in influencing change in this instance.
Only by making noise about the problem will we get it fixed.
Last edited by Simrien#6487 on Jun 4, 2020, 7:50:05 AM

Report Forum Post

Report Account:

Report Type

Additional Info