[Tool] GD Stash

new patch 1.1.7.0

Full error
Loot Table records/items/loottables/weapons/tdyn_axe1h_b204_cavetroll.dbr contains the same item more than once
The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL200605093129690' defined on 'GD_LOOTTABLE_ITEM'.
 org.apache.derby.shared.common.error.DerbySQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL200605093129690' defined on 'GD_LOOTTABLE_ITEM'.
 	at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
 	at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
 	at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
 	at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
 	at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
 	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
 	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeLargeUpdate(Unknown Source)
 	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown Source)
 	at org.gdstash.db.DBLootTableItemAlloc.insert(DBLootTableItemAlloc.java:120)
 	at org.gdstash.db.DBLootTable.insert(DBLootTable.java:256)
 	at org.gdstash.db.GDDBData.insertRecords(GDDBData.java:321)
 	at org.gdstash.db.GDDBData.insertData(GDDBData.java:213)
 	at org.gdstash.file.ARZDecompress.insertData(ARZDecompress.java:3302)
 	at org.gdstash.ui.GDConfigPane$DBImportWorker.doInBackground(GDConfigPane.java:211)
 	at org.gdstash.ui.GDConfigPane$DBImportWorker.doInBackground(GDConfigPane.java:77)
 	at java.desktop/javax.swing.SwingWorker$1.call(SwingWorker.java:304)
 	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
 	at java.desktop/javax.swing.SwingWorker.run(SwingWorker.java:343)
 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 	at java.base/java.lang.Thread.run(Thread.java:830)
 Caused by: ERROR 23505: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL200605093129690' defined on 'GD_LOOTTABLE_ITEM'.
 	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
 	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
 	at org.apache.derby.impl.sql.execute.IndexChanger.insertAndCheckDups(Unknown Source)
 	at org.apache.derby.impl.sql.execute.IndexChanger.doInsert(Unknown Source)
 	at org.apache.derby.impl.sql.execute.IndexChanger.insert(Unknown Source)
 	at org.apache.derby.impl.sql.execute.IndexSetChanger.insert(Unknown Source)
 	at org.apache.derby.impl.sql.execute.RowChangerImpl.insertRow(Unknown Source)
 	at org.apache.derby.impl.sql.execute.InsertResultSet.normalInsertCore(Unknown Source)
 	at org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source)
 	at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
 	at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source)
 	... 17 more
 

I am waiting for the update to support 1.1.7.0, in the mean time I will avoid using this just to be on the safe side.

@mamba Thanks for all your hard work.

Question, green rings such as living ring or vine ring, if I copy them to the stash and later decide I want to use it on another character, these rings don’t have the “reroll” for higher stats or is that a limitation from GD?

There isn’t an update, you just need to import the database again.

tell Crate that :wink: For GD Stash it makes no difference (which is why this is a warning). It violates a DB key, but does not matter from a functional perspective.

What it means is that the same item is an entry in the loot table more than once, which does not really make much sense (just increase its probability then) and the fact that this so far never was the case to me means it probably is a typo and not intentional.

2 Likes

you are always on the safe side even with the old version of GD Stash. I only need to release a new version of the tool if a) the save format changes or b) I want to add new functionality which may be triggered by new functionality in GD (which usually comes with expansions, not other releases), not because of a patch.

If GD releases a new version, all you need to do is import it into GD Stash, so the data it uses internally is updated.

Not sure what you mean here, no item has a ‘reroll’, the item is what the item is, its stats never change (at least not due to GDS, if the stats or value range changed within GD due to an update, that is another matter). You can craft a new item which then gets its own seed and thereby possibly / probably different stats.

1 Like

Hi Mamba, first thanks so much for your work. 1340 hours on Grim Dawn because I was able to use your tool.

I Uninstalled and reinstalled the 32 executable. However, when I click to start it starts, seems to be doing well in Task Manager for a short moment, then its all 0s except a 71.7 Megabytes of memory usage. It gets stuck there but gdstash does not start.

I have a feeling this maybe a common issue, or a stupid one on my part which is also common, hehe.

Does this problem rings a bell? Thanks in advance and thanks for being there.

No idea, first time I am hearing of this. Since a reinstall did nothing, try deleting the gdstash.ini in c:\users\username\gdstash

I have a Problem.

I deleted my save files from the grim dawn game and the savefiles from the gdstash. So i can have a “ladder reset”.
I started a new char. everything is ok. Now i want to use gdstash to store some items.
Now the problem:

The GDstash software dont see my stash tabs. The stash is empty for the gdstash software. see here: -> https://i.gyazo.com/e26cb7ac4d50b6dd1ef7570d38535d28.png

but everything else is working. The char editor works.
The im/export tab works. I can load items from dir and i see all my stuff.
I importet the database and my config is correct.

How can i get the gdstash stash transfer to work again?

If it sees your char, then the save dir should be correct. This leaves you using a different stash, HC or mod. Does the drop down list show any other stashes ?

That, or you did not actually use the shared stash but the char specific stash…

1 Like

LOL!! OMG. hahahaha … shame on me.

you are right! it was in the personal hero stash. omg :////

I get the following problem with GD Stash - i have no dlc items.
GD Stash starts up with DLC loading screen and database import loads dlc databases but the dlc items can’t be found or loaded from inventory. See below (sry german^^):

What is wrong or what can i do?

The only reason I can think of where the tool says you have the DLC, processes its databases and yet does not contain the items is if you had specified a translation .zip that does not contain names for them.

Now it works - many thanks for the hint.

I just got GD Stash. I have it say the import is complete, but nothing shows up in my stashes. I am using the game through steam and am using cloud saves. Any recommendations to solve this issue?

I think I messed up my database.
This pops up when I open the app

When I Import mod database:

And I accidentally imported database without selecting any mod from the “Selected Mod” drop down.
I don’t see any of the modified affixes for D3 masteries anymore. :cry:
Kindly help me on this. Much appreciated. :pray:t4:

Select the mod in the Configuration window and then re-import the database again.

It still shows the same prompt :cry:

The first image, all the missing affixes say pogd_… so I assume they are from the Path of Grim Dawn mod.

Nothing is broken here, you have a mod stash with affixes that the currently selected DB is not aware of. Switch to the right mod / stash to solve this.

As to the second image, seems like the mod loves verbose descriptions. So will have to decide whether to give the description more than 1000 chars or whether I do not care that it gets truncated, but make sure the entry still gets created and this becomes a warning.

1 Like

The D3 affixes still doesn’t show.
When I select the “blank” from the selected mod drop down option it shows all of my stuff on stash/char transfer and only GD affixes is shown when I try to craft.
But when I select PoGD, it doesn’t show anything. I can’t even click the tabs on your tool. Just the stuff on configuration tab.

In that case you need to import PoGD first, but with the errors you get, that does not work, so… basically you have to wait for a new release of GD Stash

1 Like