Comments - civ_mamba

That sounds right, but the Salamander does have a skin (and if it were missing you would get a checkerboard pattern, not something invisible, so more must be missing), so you must have done something wrong. Try installing again

If the Zenith and D2 masteries crash your game when you select them, you are on a really old GD version that does not support that many masteries. Time to upgrade.

Devotion points: these cannot be set based on Zeke level, also you can change that level at any time...

Difficulty with Zeke: there are many ways to get very OP in this mod, so you do not need more devotion skills to keep up with Zeke.

Iron drops have not been changed from vanilla, Zeke should help there on top of that.

Armor not shown on the selection screen and freezes are due to GD, not the mod.

Assuming this is not meant as a joke (given how many masteries the mod already has)... I am not aware that I am missing anything important ;) Yes, there are some old single mastery mods out there that I did not include (or different versions for the Cataclysm masteries than the ones I use), but the former are not important and lack gear and the latter are just similar variations.

No enemy should be invisible, they all have skins, sounds like you installed something wrong

They drop whenever a legendary item would otherwise drop, which is at level 50 but depends on the level of the area, not yours.

Sounds like you need to import the GD data on the Config page

There is no update needed for any GD release as the tool does not come with the data.

You need to import the GD data again on the Config page.

Yes, if you play some Cataclysm masteries, it might be worth deinvesting a few points from the 15 point skills, as for some the number of points were reduced

Full list of skill point changes here:

Forums.crateentertainment.com

Sounds like some kind of authorization issue to me.

When saving your stash (which you are doing here I believe), the tool creates a new file and this file creation fails.

java.io.WinNTFileSystem.createFileExclusively

The only reason this should fail should be a missing authorization

Pretty much what you see above.

If you are using Grim UI, then this adds matching themed screens for the DoM specific screens, which mostly is the class selection screen shown in the screenshot (there are more, but the others are minor changes compared to the vanilla GD screens).

Grim UI: Forums.crateentertainment.com

Not a bug, checked with the Zenith author

Grim Quest updated to 75b, Zenith masteries added

0.9.6b:
Added Frost Knight mastery

0.9.6a:
Update for Grim Dawn 1.1.6.0
Added Monk and Necromancer from NCFF
Added additional cosmetic auras from Path of Grim Dawn

0.9.6:
Update from Grim UI Hoarder to to Grim UI X-Mod
Added cosmetic auras from Path of Grim Dawn
Fix for unique token drops

0.9.5 update to latest GrimUI to allow switching of GrimUi ‘skins’ by placing the textures in the settings folder and replacing the Grim_UI_X-Mod.arc in the mod with the ine of the chosen skin. Required the mastery selection screen to be resized to vanilla size.
Bugfixes to Cataclysm player scaled pet (Hive Queen and Harbinger), +1 to mastery components

You can find that on the mod's thread at
Forums.crateentertainment.com

Here is what happened so far:
- 0.8.0: initial release
- 0.8.1 - 0.8.6: bugfixes
- 0.9.0: Grimmest FG added
- 0.9.1: bugfixes
- 0.9.2: additional wings added, Cataclysm augments now drop, NCFF armor values updated to current standard
- 0.9.3: Grim Quest updated to Grimarillion 74a
- 0.9.4: Stasher mod replaced by Grim UI - Hoarder mod, bugfixes

The fix very much depends on whether you have items stored in GD Stash or not.

If you have NO ITEMS stored, simply delete the entire db dir and start the tool again.

If you do have items stored, copy the following files to a separate directory, as they contain your collected items.

db\seg0\c4b0.dat and db\seg0\c4c1.dat

Then delete the db dir and create a new DB / import the GD data in the tool. Once that was successful, exit the tool and copy the above two files back into the new db/seg0 dir.

Ok, so I wnet to the shrine and unlocked it in Normal. The flag is reflected correctly in GD Stash. When I reset the flag in GD Stash, the shrine is correctly locked again in game. So as far as I can tell the problem is Grim Tools, not GD Stash.

If you take a char that did NOT have that shrine unlocked in game, e.g. in Normal difficulty, set the shrine's flag in GD Stash and then visit the shrine in game, is that shrine unlocked in game or not ? That is what the question boils down to. You can take Grim Tools out of the equation completely.

Or the reverse, you unlock the shrine in game and then check if the flag is set in GD Stash.

It sounds like if you did that, the shrine would not be flagged while Grim Tools shows it as unlocked.
If so, they changed the shrine's ID sometime (was always a bit odd that it had two IDs for different difficulties, when no other shrine ever did), then I would need a new char that has the shrine unlocked recently (have no such char), to check the ID. I am reluctant changing the ID based on what was discussed here so far without actually seeing it reflected in a savefile.

A better place to continue this (and maybe pst the char) is the official forum

Forums.crateentertainment.com

That could be an error in GrimTools or GD Stash. Did you visit the shrine in game ?

Looking at my source code, I have a different GUID for the shrine in Elite compared to Normal and Ultimate, it is the ONLY shrine that does not have the same ID in all three difficulties, so clearly something was/is off about this shrine.

My assumption is that GrimTools does not have that distinction as it bases its logic on the evaluation of GD data, while I looked at the actual IDs in the savefile and found this difference that way.

Unless that was fixed since, mine should be fine. The only way to verify this is to actually visit the shrine however / check if it shows up and is unlocked on the map (assuming it shows up on it, not all shrines do...)

Hi,

I don't think there is any error here, at least I do not see one in what you are describing, I think this is simply a misunderstanding of what that number (197) means...

The 197 is the number of items you collected and stored in GD Stash. It is not the number of item definitions which the tool imported from the GD data.

GD Stash always imports ALL item definitions, it simply does not mention how many these are - unless you got some error messages (which you did not).
It then updates the information it stores with your collected items (to help with the search) and that is derived from the item definition, like item level, strength requirements, etc. That is where the 197 is from - which again is the number of all items you collected.

I never tested it, but see no technical reason why it would not work. All it does is write the updated file, there is no interaction with GD.

This is an odd one, basically you failed at creating a new temporary file in your save dir, because supposedly the save dir the stash file is in does not exist.

Clearly the dir does exist, as it contains the stash file you are editing... so to me this seems to be some kind of Windows authorization issue

Mostly smaller improvements and fixes

Version 1.43 (04/15/2019)

- Displays additional set completion info

Version 1.42 (04/01/2019)

- Cooldown time now has decimal places
- Updated ID for Shrine in Sanctuary of Horran
- Changes to ARC extraction logic to accommodate Grimarillion / Grim Quest

As the tool makes a backup before writing the changes, you can get your stash back. Check the includes FAQ in dir docs for details. Make sure you do not have GD running at the time to prevent cloud save from wiping the stash again. If you have questions, feel free to ask.

Yes, the last few versions do, if you have an older version, you need to update. In either case, you need to import the GD data after installing FG to see the new items.

Are you trying to import some mod ? If so, which one (this should be an error in the mod though) ?

If you are trying to import vanilla GD, verify your game files.

That is an issue that sometimes happens with cloud save. For some reason cloud save sometimes gets confused by the stash changing outside of GD and then resets it to an initial stash.

The same can happen to the char, including map and quest files which the tool does not even touch, so it clearly is cloud save causing the issue.

To minimize the risk, only change files when GD is not running. To completely remove the risk, use local saves.

The import was successful, but two of your chars (I assume, filename is not fully shown in the picture) have an unknown format, which should mean they are either very old (from the EA days of GD) or corrupted, or you are not on the latest version of GD Stash. In the latter case, update. In the former case, check if GD can still load them. If not, delete them.