Display mission_MasterTables.lua or download file.
Display misc_lua-utilities.lua or download file.
Display user_Events.lua or download file.
Display mission_AIProductionUnit.lua or download file.
Display mission_AIScriptFunctions.lua or download file.
Display mission_SetupAI.lua or download file.
Display mission_Main.lua or download file.
Display mission_Economy.lua or download file.
Display mission_AITeams.lua or download file.
Display user_Reinforcements.lua or download file.
Display mission_AIProductionBase.lua or download file.
Display mission_AIProductionGeneral.lua or download file.
Display mission_SetupBases.lua or download file.
Display mission_SetupPlayers.lua or download file.
Display user_ScripterOverride.lua or download file.
Display mission_UIDisplay.lua or download file.
Checkout documentation
Description:
Allies 10a: Suspicion
Kosygin has indicated that this is the sight of Stalin's main atomic weapons plant. Use extreme care in approaching the Soviet base -- we don't know if any atomic bombs are armed yet. Take the facility off-line and then destroy any atomic weapons that exist.
----------------------------------
Original mission by Westwood Studios
Mission AI is derived from the Fourth Trial
(http://resource.openra.net/maps/19878/ )
Currently has a bug where the nukeup animation cycles through the map after it is launched.
Please report any bug or error (with information from lua.log or exception logs where possible) in the comments.
Enjoy.
Edit map info
Reports of 10a: Suspicion
Lint check for release-20161019
Lint check for release-20160508
OpenRA.Utility(1,1): Error: The map allows 1 possible players, but defines only 0 spawn points
Errors: 2
Previous revision | Revision | Next revision |
---|---|---|
Nothing found | 1 |
It's the latest |
Fun map, crashed second time I played when I did capture stuff: https://gist.github.com/kyrreso/804068d84c99827a911a99aaccbb61f7
Can you give more details on the crash, a.k.a:
Are you playing on release-20161019?
What did you capture?
Which objectives have you already completed at the time of the crash?
An approximate in-game time of the crash?
(If you have more time for replicating the crash, you can try setting the following on the first line of mission_Main.lua:
bdebug = true
This will replace the mission text with realtime function calls can may be helpful to find the root of the error.)