安装 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 works :D And it's incredibly fun. Thanks for the support.
@metro.rebel3 Lucky! It looks fun.
As far as I know, that zip file should be functional.
I went as far as unsubscribing, deleting mod files in said locations, booted and it comes up with "Disabling BlocksFromAbove.rte" in the LoadingLog 2nd line, then rebooting CC once again so that it was clear, restarting steam, resubscribing, and then running CC. Result;
CortexCommand.exe has stopped responding.
Although, what I was getting at with my first statement is that the workshop doesn't appear to be downloading any workshop content. However, when I boot the game with the mod subscribed (and yeah, I wait long enough for it to download) - it DOES start the log off with
Downloading data module: workshopmods/blocksfromabove.rte.zip, 100 percent complete
Done downloading that module!
Unzipping blocksfromabove.rte.zip
Extracting: blocksfromabove.rte/Activities.ini
Extracting: blocksfromabove.rte/Antidote.bmp
Extracting: blocksfromabove.rte/Antidote.lua
etc.
So yeah I have no idea.
1. Unsubscribe
2. Go to your Cortex Command directory and delete BlocksFromAbove.rte
3. Go to Cortex Command/WorkshopMods and delete blocksfromabove.rte.zip
4. Subscribe again, then run the game
If that doesn't do it, I'm not sure what's going on. Never heard of that happening before. :/
I can also try sending you the zip file directly and see if you can run that.
Scenes.rte loading:
Index.ini - done!
Metagames.rte loading:
Index.ini - done!
(the last two files that are loaded, which is odd because it seems to check them just fine and results in the 'done!' print) Then it comes up with "Cortex Command is not responding" error window.