安装 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...