Modding Help unpack.bat broke batch files for me.

Trying to figure out what went wrong but here's what I know:
I'm on windows 8.1 on a new laptop, trying to get everything set up again so I can continue working on mods.

I downloaded the unpack batch file from the guide threads (same one I used originally on my other computer), and tossed it in my starbound/win32 folder and ran it to unpack the assets, and it worked fine.

Then I tried it in unstable (nightly) and it didn't work.. And now I can't even unpack the stable branch a second time.
Attempting to run a .bat file tells me "Your computer can't run this app", and tries to direct me to the windows store thing and gives me empty results.

Running as administrator prevents this error, but the .bat file doesn't actually do anything. I've searched for several hours online and I can't find a fix for this specific situation.

What I need, ideally, is something to reset my ... whatever it is that controls batch files? I don't really know this stuff that well.

I would appreciate any help, tremendously. As this is necessary for me to begin modding again from this new computer.

Thank you for your time.

 

Try this.
If this doesn't work, are you sure you didn't do anything at all to the batch file itself?

 

I attempted to use the link you sent me, whatever that was it ran fine. But I still get the error.

I may have changed the path of the unpack.bat file attempting to unpack unstable. But the unchanged one doesn't work on stable branch (which did work earlier).


___________
I'll check that out, swatelite, but I still need to fix my issue for if I ever need .bat files again.

 

I wonder, can you run this file specifically per manual commandline?
As in, run cmd and execute the file itself in there.
And if yes, what happens if you do?

 

Windows tells me my computer can't run that app, and the cmd prompt says access denied.


Also that thing xxswatelitexx sent me to doesn't work for me.. I'm gonna try restarting my computer (much facepalm, I didn't even consider restarting).

Edit: No change from restarting.

 

If that doesn't work, I researched a bit in the meantime.

There's one last thing to check:

• Delete the already unpacked stable assets (or change the folder they should be written to)
• Execute the bat as an administrator again

Next steps depend on what happens:

• It works
  • Something went wrong with changing the directory for unstable and
  • Your security settings are too strict to let it overwrite files (Win 8.1 security is a pain)

• It doesn't work
  • Security settings might still be an issue, however a quite different one

If case 1 applies, try to find out how to set the I/O security settings for your user account (yes, even if it's admin) -- I'm not using Win8.1 (anymore) so I can't help much there (if I did at all).
If case 2 applies, try to completely rewrite a batch file, it can be doing the exact same thing, I'll give you an example below.

Code:

asset_unpacker.exe ../assets/packed.pak assets_stable
@pause

In case you've got absolutely zero experience with .bat files:

• Create a new notepad file
• Paste that text
• Save it, rename the file "xxx.bat"

 

Running what you gave me as admin:

That's rather odd.. Why is it pointing to windows/system32?

if I don't run as admin, it gives me the same error as before and the same text I just copied.

 

You ran that in the win32\win64 starbound dir?
If so, try this:

Code:

"C:\Program Files(x86)\Steam\steamapps\common\starbound\win64\asset_unpacker.exe" "C:\Program Files(x86)\Steam\steamapps\common\starbound\assets\packed.pak" "C:\Program Files(x86)\Steam\steamapps\common\starbound\win64\assets_new"
@pause

(This is all one line, in case forum formatting screws up)

 

Yes I ran that in starbound/win32...

And the new longer file....
That seems to be working (had to remove the extra spaces in each instance of "Program Files (x86)" however.).. Thank you!

Now I just need to attempt it for unstable, should just be switching "starbound" to "starbound - unstable", correct?

Edit: I seriously can't wait until windows 10 comes out. 8.1 is annoying, clunky, and won't do what I want nearly as easily.

 

Huh, so the filepaths changed in Win8.
Yeah, as long as the thing is in doublequotes spaces shouldn't matter, so just add the "- unstable" part and you should be fine.

 

Looks like the unstable (nightly, actually) is unpacking properly finally. Thank you so much!
Modding is what keeps me interested in Starbound at this point in time, so your extensive assistance has been absolutely fantastic.
Thank you. ^_^

 

You're welcome. :P

And... since this problem might come up again with another batch file, here's what I highly suspect was going wrong:

:: The more (useless stuff) you know! ::

For some reason windows 8.1 tries to run batfiles in a standard location, this being C:\Windows\whatever.
Problem with that is that you have absolutely NO write access to that folder, even your read access might be limited.
So, if this comes up with any other bat file just make sure you point them to the global location, since it'll (again) try to execute it in the internal root directory.

 

Well that... that helps a lot actually.

 

You should be moving away from using .bat and .cmd batch scripts and possibly look into using powershell on Windows 8 and up (especially on 10) due to security and execution policies.

It is trivial to change Powershells execution rules compared to all the security bs Microsoft has continued to lay on top of batch preventing it from writing files to the primary system drive in most scenarios.

You can also run most of the contents in a batch file through powershell anyway. Just be sure to switch the ps execution policy back to some restriction level or learn how to locally sign scripts.

Just like batch in the win xp days powershell can screw up your day badly if a rogue script slips onto the system and runs. But at least an elevated cmd prompt or powershell can change the ps execution policy with a one line command, so it isnt a total pain.

You should also be able to make a batch file that changes the policy from cmd, then execute powershell from the same batch file, and then set the policy back to the desired level of execution restrictions.

Just food for thought, powershell is awesome when used for mod debugging and packaging

*edit* - Fixed the formatting so its easier to read since tapatalk butchered it >.<