Author Topic: [bug][pack toolkit]I literally can't save my pack!  (Read 1798 times)

0 Members and 1 Guest are viewing this topic.

Offline GigaLem

  • The Dog That Brought Lemmings to Avalice
  • Posts: 1417
    • View Profile
[bug][pack toolkit]I literally can't save my pack!
« on: September 19, 2018, 06:46:34 AM »
When I try to save my pack it give me an error even when im doing something intended.
its gives me the "Path not supported error" even when I press cancel >:(>:(>:(
I'm selecting a folder but it just spits out this error

Offline IchoTolot

  • Global Moderator
  • Posts: 3612
    • View Profile
Re: [bug][pack toolkit]I literally can't save my pack!
« Reply #1 on: September 19, 2018, 08:10:45 AM »
Ok, let's first be sure you are saving in the right places:

1.) Load the pack by clicking on the packs folder.
2.) When saving you are already in the packs folder and only need to press save.
3.) When a saving error comes due to problems accessing a level, it can usually be solved by just saving again.

But as I never seen this error and it points to the program not being able to identify the packs format, my bet would be on some added content changing a file unexpectedly.

I think it would be best if you send Nepster the pack as a whole so he can identify which part changes the format to something unknown.

Offline Simon

  • Administrator
  • Posts: 3877
    • View Profile
    • Lix
Re: [bug][pack toolkit]I literally can't save my pack!
« Reply #2 on: September 19, 2018, 12:47:24 PM »
What exact folder?

Since the toolkit doesn't like that path, have you tried saving elsewhere?

Nepster's explanation and workaround:

Quote
until I get around to fix this bug, I suggest trying to save the pack into some folder that does not contain "Desktop", "Favorites", "Users" or "Libraries" in it

-- Simon
« Last Edit: September 19, 2018, 12:57:42 PM by Simon »

Offline Nepster

  • Posts: 1829
    • View Profile
Re: [bug][pack toolkit]I literally can't save my pack!
« Reply #3 on: September 19, 2018, 05:00:44 PM »
IMPORTANT: PLEASE DO ALWAYS INCLUDE THE VERSION OF THE TOOL YOU ARE USING!!! There are some known bugs in older versions, and without this info I can neither rule them out myself or point you to them, if there is a possibility you are encountering them.

In addition to what Simon said, please make sure that you don't have any prohibited characters ("/",  "*", ":", "?", <", ">", "|") in the file path you selected to save your pack to. This should have been caught by the file browser for choosing the folder, but you never can be certain with them. :P

If none of this helps, then please try the following two things (one after the other):
1) Remove any of these prohibited characters from your pack name. I have dealt with these characters in rank and level names, but I am not sure about the pack title.
2) Remove any special sprites from your pack and then try to save it again. The usual sprites usually work fine, but I haven't tested it much with custom lemming sprites and the like. So there might still be some problem with them trying to be copied to a non-valid path.
I don't think it likely that either of them is the problem, but one can never know for certain...

If none of this helps, I'll try to release the next pack toolkit version tomorrow or so, and you try whether it works with the updated version. For the next version I replaced the file browser to select the folder to save to (among other things), so there are chances that the bug will magically disappear.
If not, then the next version will at least save the error message together with a stack trace to the file "ErrorLog.txt", which will help me immensly to determine the actual problem. Unfortunately I forgot to add this logging in the current version. :(

And yes, I still haven't gotten around to deal with these special folders like "Desktop", "Users", ...

Offline GigaLem

  • The Dog That Brought Lemmings to Avalice
  • Posts: 1417
    • View Profile
Re: [bug][pack toolkit]I literally can't save my pack!
« Reply #4 on: September 19, 2018, 08:45:12 PM »
Sorry for not including the Version number, its the current version. 1.5