Its saying that System cant find way to java.IOException etc.
Save dir isnt protected or anything.
Well, if this were a general problem, I’d see a lot more reports of this, so it must be something local.
The tool creates a new stash file under a temporary name, renames the existing stash file and then renames the temp file to the correct name.
So not sure what would not exist here. The dir and stash file should exist and the new file not existing should not be a problem. It must be something about write access from my perspective.
Can you post the full text (copy & paste it from the window), so I can see the file and line number that triggers this ?
Systém nemôže nájsť zadanú cestu
java.io.IOException: Systém nemôže nájsť zadanú cestu
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(Unknown Source)
at org.gdstash.item.GDStash.write(GDStash.java:642)
at org.gdstash.ui.GDCraftPane$FileSaveActionListener.actionPerformed(GDCraftPane.java:110)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$500(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue$4.run(Unknown Source)
at java.awt.EventQueue$4.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Where is the part of the message that is in the screenshot, the first part of the message is more important than the rest of it
Just going by the screenshot, it looks like file creation was not allowed, still would like the exception text though to hopefully narrow that down
Do you have some antivirus or something that would prevent writing to that dir ?
Message updated.
Now I tested it with turned off ESET and still getting same error.
That is the creation of the new file in the save dir. Its name at that time will always be temp_tmp.tmp (not that it should matter)
File temp = new File(dirPath + "temp_tmp.tmp");
temp.createNewFile();
the createNewFile line fails, that must be some kind of protection for the dir on your end, or possibly some restriction you impose on the Java side
Well, and how I should fix it?
No idea. It is some software you have on your PC, I have no way of knowing what you have installed or how to configure it properly.
At least thanks for effort. Soon I will have new system/PC , so I will try it there.
Some bug: unable add completion bonus on relics.
thanks, unintended consequence of trying to suppress affixes for 2h ranged weapons which pop up due to there being an unused loot table which adds affixes to them
Will be fixed in the next version
Version 1.1.4 released
More expansion support
Minor fixes
Thanks for this, I can finally start cheating again!
er, I mean, storing items I legit found in the game again.
Funny how much you can learn about the expansion by looking through this version. Where those factions already confirmed somewhere else? Must have missed them if so.
Dude you Praetorians are supposed to be pillars of the community, shining beacons for players to look up top, righteous paragons of looting and killing, defenders of cairn.
You just brutally shattered my world.
Sent from my SM-J727P using Tapatalk
I figured it is very little information and the text files had apparently accidentally been leaked a while ago, so there is little harm done even if most people probably never got / saw those text files.
Technically I think two of the factions were known at least, not sure about others
Probably a silly question, but is it possible in Grim dawn to completely configure items with exactly the properties you want like you could do in Diablo 2?
Like say I want to play a 2H physical witchblade but I simply prefer the aesthetics of a two handed sword to those of a two handed mace, so is there a way to ‘create’ some two handed sword that has exactly the stats of the Leviathan?
The expansion allows to to use one item while using the ‘skin’ of the other (transmogrify), vanilla GD does not, but a mod allows for this
im sure youve heard this question a million times
but when i run 1.14 it says java virtual machine launcher an exception has occured and then nothing happens, i was using 1.12 prior with no problem, i noticed that 1.14 was a java file and 1.12 was its own executable installer.
any solution to this? or should i just stick with 1.12?