Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
It might be the specific mod (Since the error we have seems to be that the asset_unpacker can't recognise the files as normal .pak files or .modpak files), but I have tried multiple different mods and still have the same issue.
I also tried using a batch file made by someone else, as I may have been creating the batch wrong ( The one I used was Dolan's ModPackHelper, http://community.playstarbound.com/threads/all-versions-win-linux-modpackhelper.92473/ ) however in the logs it creates I still get the error. Here is the log for one of the tests I did. I was doing 2 mods at the same time, one was the automatic doors mod V2.0 and the other was the undertale music pack mod V1.0
22/07/2016 22:28:32.10
Exception caught: (AssetSourceException) Packed assets file format unrecognized!
22/07/2016 22:28:32.10
Exception caught: (AssetSourceException) Packed assets file format unrecognized!
Any help on this would be appreciated! The .modpak files I have I wish to convert to a .pak file, however it has been impossible with these errors. Thanks!
----------------------------------------------------------------------------------
EDIT #1:
Also in the log of Dolan's Modpackhelper, it stated:
"The System cannot find the file specified.
AutomaticDoors_v2.0 has been unpacked"
However, it was not unpacked. Maybe this has something to do with it? Probably not, but yeah....
EDIT #2:
Attempted to make a fake .modpak file (Empty) and the log said the following:
22/07/2016 22:52:02.60
Exception caught: (EofException) Failed to read full buffer in readFull, eof reached.
So, it's deffinately something to do with the way the .modpak files are formatted, not just a complete error with the unpacker, at least from what I can tell...