[Tool] GD Stash

that one is easy, there is no component with that tag in the .dbr files

and none of them are called Venomous Fang

Okay, the problem is now clear. There’s no data for the item ā€œVenomous Fangā€ in the database; it only exists in the text. Sorry, I might have missed one when crafting items one by one.

A separate search on GDS for Silvercore Bolts has already filled in the missing one. :blush:

So, I’d like to suggest adding a sequence number to the beginning of each row in the item list on the left. This would prevent confusion and omissions, and also make it easier to find items.

The item texts are taken from GD, so as long as they do not have a sequence number in GD, GD Stash will not have one either… a workaround would be to have them in a custom language file and use that instead of the vanilla one during the GD Stash import

1 Like

OK, thank you for your guidance. I’ll try it.

Perhaps my English isn’t good enough, and I haven’t expressed myself clearly. My intention was to add a sorting function to the GDS software, just to sort the searched items, not to add numbers to the item names, which seems unrelated to GDS data.

Ah, I thought you were talking about R## and S## in your picture, my mistake

Sort by what? Also, you already can sort…

Just a number to count from 1 to N so you can restore the initial order?

1 Like

Yes, that’s roughly the idea. This way, can also clearly see the total quantity of a certain type of item. For example, searching for all Component items will directly list 107, reducing the probability of errors from manual counting.

Especially for blueprints. According to my incomplete statistics, there are currently 750 craftable blueprints that can be learned in GD. :stuck_out_tongue_winking_eye:

My use of ā€œsortingā€ seems inappropriate; it should be ā€œstatistics.ā€ Fortunately, you basically understood what I meant.

Stopped working again with the latest patch update. Is it just me?

After updating 1.3.0.0 (b21936108), there was also an issue with my GDS 1.8.2. The components were not displayed when placed in the repository, or in other words, they could not be placed in the component repository page.


that is just you

1 Like

that page is not actually part of the stash file, there is a separate file for the components now (reagents.gst)

Haven’t looked into that format at all yet

1 Like

The reason was that it was displayed as if it were stored on the right edge of the monitor after startup. I don’t know why it happened, but there are no problems with the function. Thanks.

Actually, craft function doesn’t work on PT for some reason

you are in game with the character, GD is not going to read that from disk and replace the one in memory / in game with that… instead it is going to overwrite your change the next time it saves the char, which is maybe a second later, as it continuously saves

Just to clarify: it worked that way (ā€œhotā€ r/w) with GDS 1.76+ and with the current live game ver. It stopped working with 1.82 and with the current PT game ver.

it’s GD that’s changed
Mamba said earlier when the issue arose that v1.3 changed something so now GD is loading the file on startup and that’s it, then it’s in memory from there/not reading direct from the file while ingame anymore [Tool] GD Stash - #8316 by mamba
(almost like how the game handles stuff with steam save folder/cloud on prior to v1.3)

1 Like

That’s the answer, ty.

Could GDS add a feature to display the DBR path of the item? Like DPYes displays it in the game.


image

It never worked for the character, it did work for the shared stash however. That it no longer does is due to GD, i.e. much like the character, it now also keeps the shared stash in memory, rather than reading it from the disk each time you open it. So any changes you made to the file are never picked up by the game.

@mamba hey there. I faced a very weird bug and I’m not sure what’s causing it. basically I copied the char’s save, removed it, renamed the original and then returned the duplicate to the save folder.
and then this happens and I’m not sure why.