You do use the 64bit JVM, correct ?
CP is command prompt I assume. Why can it not access the jar ? It should be in the same dir, is that the case ? Sounds more like a restriction (read access) issue, please check that.
You do use the 64bit JVM, correct ?
CP is command prompt I assume. Why can it not access the jar ? It should be in the same dir, is that the case ? Sounds more like a restriction (read access) issue, please check that.
One step closer to better mod support
Items are also being imported, after I finally located some stupid bug. Still some more things on the list before it is ready for release though (have to refresh the buffers when switching between mods / databases).
On the Crafting tab, I can create a new item from scratch, give it a prefix, suffix and modifier, place it in my stash, hit the âsave stashâ button, and then go into the game and my character can take possession of this new item. If Iâm still in GDStash => Crafting tab, I can hit the âReloadâ button and the new item is where I left it.
But if I select an item that is already in the stash and attempt to modify it, itâs a no-go. I have my âAffix Combinationsâ settings set to âNo restrictionsâ and I âsave stashâ once I place the modified item. If I âreloadâ the stash the item will stay in the new place Iâve put it, but it will have its old traits. If I go into the game without hitting âreloadâ the item has none of the new traits I have given it.
I wonder if Iâm doing something wrong? Or is there something Iâm missingâŚ?
Aside: thanks for making an excellent tool. : )
I did not allow the modification of existing items to prevent accidental screwups. Only new items can be created.
I assume you can select an item in the shared stash as the base (not just craft from scratch) and change its affixes, but it still is not the same item, so you will have to place that new item in the stash.
Havenât done this in forever, not sure if that works right now or if you always have to choose a base first, either way, changing an existing item is not supported.
Ah, that would definitely explain it. Thanks for the help. : )
Another step closer (the texture files were slightly different in TQ and apparently there is another way for .arc files to store their data that I had to yet support)
Have you never heard of Symantec Ghost or Acronis TrueImage?
Seriosuly, you back your C: drive up to an image file, then if something goes wrong you restore it like it never happened. Makes System Restore look like a joke (not hard, since it is), and even that could probably recover from the problem you are describing.
And tbh itâs not GD Stash, itâs something you did. That is almost guaranteed. In 30+ years of working with computers it is almost always a PEBKAC when something breaks, not a problem with a program that lots of other people use without any problem. Even my own problems, and after this many years I have very few problems anymore, I eventually trace back to something I did in almost every case.
In this case I am hazarding a guess that itâs because you installed both 32-bit and 64-bit Java. Donât ever do that. Just install the 64-bit and leave well enough alone. Still, itâs just a guess and may well not be your problem at all.
Just curious: Does this not recognize the new pet based affixes yet? I had been running 9.7c and upgraded to 9.9i and it doesnât seem to get them right.
Just wondering if this is the case, or if itâs something Iâve done wrong with the installation process.
Thanks.
Did you import the GD database again ?
The tool does not come with a set of data, which is both good and bad
It is good because you can import the new GD database right after a new GD version is out and do not have to wait for me to update anything, it is bad in that updating the tool will not get you the latest items and affixes.
When you say âget them rightâ do you mean âknow them at allâ ie they cannot be selected during crafting and if you have an item in your stash, it does not show it ?
Then you most likely have to import the latest DB.
If you mean something else, please clarify.
Ok, so on the 9.7c version, I had a set of Dominatorâs Isaacâs Spaulders in my transfer stash, which the version did not recognize.
i installed version 9.9i and imported the database and the shoulders were still there in my stash, however they were displayed as just Isaacâs Spaulders. That was where my confusion was coming from. Apparently, somehow the Dominatorâs prefix got removed during the process. Not sure where or how.
Itâs not a big deal though, as I can just craft a new item that matched the old. I was just caught off guard for a moment. This new version is quite awesome, I must say. Thanks for all your hard work!
Odd, the only reason I would remove an affix is if it did no longer exist in the database. Then I do it silently as there is nothing else to do anyway.
Did you save that stash, thereby losing the affix, or do you still have it ?
If you still have it, Iâd be interested in that stash to see what the reason is.
Sorry, I saved the stash already. Though oddly enough, before I updated I made a back-up of the 9.7c version, when I load up that file the Isaacâs Spaulders also have the Dominatorâs prefix removed. So I guess the problem didnât occur during the update process, but before.
I did get an error message on the old version regarding the Isaacâs Spaulders item not being recognized, or something to that effect. Perhaps the affix was removed at that time?
ok, it does make sense that it was not during the update, no idea why it was removed at all though
I did get an error message on the old version regarding the Isaacâs Spaulders item not being recognized, or something to that effect. Perhaps the affix was removed at that time?
probably, clearly the item was recognized or it would no longer exist, so it must have been something with it, affix, component, etc. that was not recognized and got removed.
This will change with the next release, nothing ever gets removed
I removed it so far because during the GD beta some items and affixes were removed, so it made no sense to store them in the tool any more either.
With me adding more mod support, nothing can be taken for granted any more however, i.e. an item in your shared stash may be from a mod that you currently have not loaded in GD Stash, same for affixes etc.
What will happen going forward is that I hide the item / affix / component / ⌠but keep the item intact and in the stash, so saving the stash keeps that item unchanged, regardless of whether it is shown / how it is shown.
You still will get warnings that you do not see everything, but nothing will be lost.
Hi! Iâm using the win32bit exe, version 099g. Working almost flawlessly for me, but at least in the german translation the searchfunction seems to recognize OA as DA and vice versa. No biggie though. Thx for this great tool (and special thanks for providing a 32bit version )
You are right, that is an error in the german text files, thanks
If you want to fix it on your end, open GrimDawn_German.properties and replace the existing definitions (left hand side ID) with the following ones
STAT_DEF_ABIL = Verteidigungsqualität
STAT_DEF_ABIL_SHORT = VQ
STAT_OFF_ABIL = Angriffsqualität
STAT_OFF_ABIL_SHORT = AQ
Found a bug:
Transfer an item in to your shared stash
Click reload without clicking save
Item is gone
So basically I transferred something in, then realised I hadnât clicked reload and so had a dupe in there, so I clicked it and the item I transferred in disappeared.
that is not a bug, it is what you asked it to do⌠This is no different from transfering an item and then closing without saving, the item is gone
Ok, bug was the wrong word, just a bit of an annoyance if you do that by mistake.
Where does GD Stash store the DB it works from? Iâd like to set up an auto backup script.
Thanks
Depends on your version, the recent ones have it in a GDStash dir under your user-dir (C:\Users<username>) before that it was the db subdir in its installation dir.
If you have the user-dir subdir, that is the one, the db subdir in the install dir may still exist from an earlier version but then it is no longer used.
Got it, thank you.