Basically, I want to use GDStash and said external file to communicate with Archipelago. So that if something happens in-game that causes a change in GDStash (like for example a waypoint being activated or a shrine being purified), it makes GDS write that into a file; and also if something changes in said file due to Archipelago writing something itself, that GDS reads that change and does something in the game (like giving a devotion point or skill points). Thanks!
without speaking for Mamba/in terms of what GDstash is capable and not capable of
you need to remember that GDstash is manual, while it can most certainly read/write to the player files, it does not do stuff automatically/without being prompted to, nor is it (at this program version) running and automatically interacting with the game âconstantlyâ updating stuff/files in the background
^whether or not it can do that youâd have to ask Mamba, but atleast atm GDstash interaction is manual
(and canât update certain files while they are being used actively in game afaik like player.gdc)
2 Likes
if it results in a change to GD Stash, this means it results in a change to the GD save file. So you do not really have a need to write that to a separate file.
This part wonât work. If you play the char in GD and then make a change via GD Stash, that change is lost, as GD has a copy in memory and does not check the file. GD will eventually (very soonâŚ) overwrite the save file with a new copy of the in-memory char, and the change is lost for good.
1 Like
Do I have to do anything with this after an update happens in game like re-importa database or something?
Re-import the database to pick up the changes made by the new version.
Yes, re-import the GD data to update it
I have been encountering a recurring crash with GD Stash which has resulted in lost items and general inability to use the program reliably, which is immensely frustrating. Since thereâs no source code for me to investigate it myself and submit a pull request to resolve the problem, here is the rather sizeable console output full of stack traces when the program crashed most recently: GD Stash Crash Log
This intermittently occurs when changing the parameters of the search and hitting search, at which point the application hangs and becomes entirely unresponsive requiring killing the process.
I am using GD Stash 1.60 and running it on Java 8u372 (OpenJDK with Hotspot JVM) in Linux. Not sure what happened since itâs the same GD Stash install folder I was using previously for a long while without any such issues.
while being a temp fix for losing items and not a crash solution; hit the save stash button after making any stash alterations/pulls/storage
even if GDstash crashes because of search bug, the items will be saved
not sure why this would crash / occur, but I added a few checks to the model just in case.
It still does not explain any lost items to me. What items are you talking about? Items stored in GD Stash, items in the shared stash?
alright so this might be a bit weird/obscure, and possibly totally my fault/my pc related
but for some reason interacting with GDstash ânowâ keeps prompting the "default windows beep"sound, which besides being weird is also annoying 
aside from turning off the windows sound/ânotificationâ entirely, any ideas as to why or how this is or getting it to stop?
no idea how you manage that, sounds like there is maybe some hidden popup you would need to click that gets in the way, but that should not survive starting the program again
Any updates regarding the new stuff coming in 1.2?
Importing the database of the v1.2 playtest throws these errors:
Index: 0, Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(Unknown Source)
at java.util.ArrayList.get(Unknown Source)
at org.gdstash.ui.character.GDCharFactionPane.initReputationLevels(GDCharFactionPane.java:202)
at org.gdstash.ui.character.GDCharFactionPane.updateConfig(GDCharFactionPane.java:1060)
at org.gdstash.ui.character.GDCharDataOverviewPane.updateConfig(GDCharDataOverviewPane.java:272)
at org.gdstash.ui.character.GDCharEditTabbedPane.updateConfig(GDCharEditTabbedPane.java:142)
at org.gdstash.ui.character.GDCharEditPane.updateConfig(GDCharEditPane.java:450)
at org.gdstash.ui.GDConfigPane.initData(GDConfigPane.java:1435)
at org.gdstash.ui.GDConfigPane.access$800(GDConfigPane.java:78)
at org.gdstash.ui.GDConfigPane$DBImportWorker.doInBackground(GDConfigPane.java:295)
at org.gdstash.ui.GDConfigPane$DBImportWorker.doInBackground(GDConfigPane.java:80)
at javax.swing.SwingWorker$1.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at javax.swing.SwingWorker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
GDstash still seems to work fine after this, but after closing the program it wonât start up again, itâs stuck at the splash screen forever. The only way to start it up again seems to be deleting the c:/users/username/gdstash/db folder. But then I have to import the database again, which again results in the errors above.
Luckily I made a backup of my stash so nothing is lost, itâs just a mild inconvenience that I have to keep GDstash running all the time if I donât want to delete and import the db everytime I want to use the tool
Donât do that, that also deletes your collected items
Can reproduce the issue and have it fixed on my end
Havenât looked at it yet, not expecting it to affect GD Stash, is there something you are thinking of in particular? Havenât really followed what is new in 1.2
Stash is breaking if you import the database for v1.2 it seems. devloek on the GD discord in mod-discussion channel said heâd imported the database, got a load of error messages although it seemed to work okay, but when he closed it he couldnât reopen it again. Had to delete the gdstash db folder to get it to open properly and then got the error messages again.
GDStash crashes loading the new the DB like Volek posted. I donât see anything about faction reputation in the change logs though.
Yes, as I wrote, I have a fix for that, was just wondering if you were expecting support for some new features on top of that.
Version 1.7.0 has been uploaded, it fixes the GD 1.2.0 beta import issue
2 Likes
thank you for the fix! The runeofhagarrad.dbr errors still persist but the launch lockup has been resolved 