Super Robot Wars/30/Modding - Revision history

Kalvinis: Added rest of Touroku unit conditions found in [Mission_est010_en.cpk]

2022-06-15T21:10:23Z

Added rest of Touroku unit conditions found in [Mission_est010_en.cpk]

← Older revision		Revision as of 14:10, 15 June 2022
Line 45:		Line 45:

	* [ERASE_ENTRY] -- <To be filled in>		* [ERASE_ENTRY] -- <To be filled in>

			* [ADD_PARAMETA] -- <To be filled in>

	* [PARAMETA_COPY] -- [https://akurasu.net/wiki/Super_Robot_Wars/30/Upgrade_Carryover Copies the stats of one unit and/or pilot to another]		* [PARAMETA_COPY] -- [https://akurasu.net/wiki/Super_Robot_Wars/30/Upgrade_Carryover Copies the stats of one unit and/or pilot to another]
Line 53:		Line 55:

	* [RIDECHANGE] -- Swaps out an existing unit and/or pilot with a different unit/pilot entirely, usually when a pilot receives a brand new unit.		* [RIDECHANGE] -- Swaps out an existing unit and/or pilot with a different unit/pilot entirely, usually when a pilot receives a brand new unit.

			* [EXCHANGE] -- <To be filled in>

			* [RESET_TRAINING] -- <To be filled in>

	* [RIDE_ON_PILOT] -- <To be filled in>		* [RIDE_ON_PILOT] -- <To be filled in>

Kalvinis: Added [ERASE_ENTRY]; Will add more designations later as found

2022-06-14T14:35:44Z

Added [ERASE_ENTRY]; Will add more designations later as found

← Older revision		Revision as of 07:35, 14 June 2022
Line 43:		Line 43:

	* [NEW_ENTRY] -- Adds the unit to the list of player-controllable units, so long as it does not already exist on the player's save file.		* [NEW_ENTRY] -- Adds the unit to the list of player-controllable units, so long as it does not already exist on the player's save file.

			* [ERASE_ENTRY] -- <To be filled in>

	* [PARAMETA_COPY] -- [https://akurasu.net/wiki/Super_Robot_Wars/30/Upgrade_Carryover Copies the stats of one unit and/or pilot to another]		* [PARAMETA_COPY] -- [https://akurasu.net/wiki/Super_Robot_Wars/30/Upgrade_Carryover Copies the stats of one unit and/or pilot to another]

Kalvinis: Added 2 more conditions (EQUIP/EQUIP_HOLD) to TOUROKU_nnn; added "placeholder" text to new conditions

2022-06-12T16:35:58Z

Added 2 more conditions (EQUIP/EQUIP_HOLD) to TOUROKU_nnn; added "placeholder" text to new conditions

← Older revision		Revision as of 09:35, 12 June 2022
Line 53:		Line 53:

	* [RIDE_ON_PILOT] -- <To be filled in>		* [RIDE_ON_PILOT] -- <To be filled in>

			* [EQUIP] -- <To be filled in>

			* [EQUIP_HOLD] -- <To be filled in>

	* [SORTIE_NOT_NOTICE] -- Reserves an existing unit for future spawn, most often used for missions where the Dreisstrager arrives late.		* [SORTIE_NOT_NOTICE] -- Reserves an existing unit for future spawn, most often used for missions where the Dreisstrager arrives late.

Kalvinis: /* TOUROKU_nnn */

2021-11-26T04:24:15Z

TOUROKU_nnn

← Older revision		Revision as of 21:24, 25 November 2021
Line 50:		Line 50:
	* [VERSION_UP] -- Swaps out an existing unit and/or pilot with a different version of the same unit/pilot, [https://akurasu.net/wiki/Super_Robot_Wars/30/Mech_Upgrades usually to upgrade stats or add new attacks.]		* [VERSION_UP] -- Swaps out an existing unit and/or pilot with a different version of the same unit/pilot, [https://akurasu.net/wiki/Super_Robot_Wars/30/Mech_Upgrades usually to upgrade stats or add new attacks.]

	* [RIDECHANGE] -- Swaps out an existing unit and/or pilot with a different unit/pilot entirely, usually when a pilot receives a brand new unit.		* [RIDECHANGE] -- Swaps out an existing unit and/or pilot with a different unit/pilot entirely, usually when a pilot receives a brand new unit.

			* [RIDE_ON_PILOT] -- <To be filled in>

	* [SORTIE_NOT_NOTICE] -- Reserves an existing unit for future spawn, most often used for missions where the Dreisstrager arrives late.		* [SORTIE_NOT_NOTICE] -- Reserves an existing unit for future spawn, most often used for missions where the Dreisstrager arrives late.

Kalvinis: /* SC_ENEMY_SCRAMBLE_MODE2 */

2021-11-24T19:52:47Z

SC_ENEMY_SCRAMBLE_MODE2

← Older revision		Revision as of 12:52, 24 November 2021
Line 93:		Line 93:
	==== SC_ENEMY_SCRAMBLE_MODE2 ====		==== SC_ENEMY_SCRAMBLE_MODE2 ====
	This code uses an enemy table from ''ENEMY_TBL_nnn'' (located in the relevant .lua file) to spawn enemy units into the map. Here is an example code: ''SC_ENEMY_SCRAMBLE_MODE2( ENEMY_TBL_000, ScDifficulty_HIGHLEVEL, ScScramble_ONMAP, SCBIT_SCRAMBLE_NOP, SC_POS(0, 0) );''		This code uses an enemy table from ''ENEMY_TBL_nnn'' (located in the relevant .lua file) to spawn enemy units into the map. Here is an example code: ''SC_ENEMY_SCRAMBLE_MODE2( ENEMY_TBL_000, ScDifficulty_HIGHLEVEL, ScScramble_ONMAP, SCBIT_SCRAMBLE_NOP, SC_POS(0, 0) );''
	'''ENEMY_TBL_nnn''': This determines what enemy table to call from the .lua file.		'''ENEMY_TBL_nnn''': This determines what enemy table to call from the relevant .lua file.
	'''ScDifficulty_xxx''': This determines what enemy table to use from the .lua file, depending on either difficulty selected or average level of units (unsure, needs research). There are 3 determining codes (currently): NORMAL, HIGHLEVEL, NOT_HIGHLEVEL.		'''ScDifficulty_xxx''': This determines what enemy table to use from the .lua file, depending on either difficulty selected or average level of units (unsure, needs research). There are 3 determining codes (currently): NORMAL, HIGHLEVEL, NOT_HIGHLEVEL.
	'''ScScramble_xxx''': This determines how to summon the enemy table on to the map. There are 2 determining codes (currently): NORMAL, ONMAP.		'''ScScramble_xxx''': This determines how to summon the enemy table on to the map. There are 2 determining codes (currently): NORMAL, ONMAP.

Kalvinis: /* SC_GMMAP_INIT( xxx ) */

2021-11-24T19:50:26Z

SC_GMMAP_INIT( xxx )

← Older revision		Revision as of 12:50, 24 November 2021
Line 99:		Line 99:
	'''SC_POS(n, n)''': <To be filled in>.		'''SC_POS(n, n)''': <To be filled in>.

	==== SC_GMMAP_INIT( ~~xxx~~ ) ====		==== SC_GMMAP_INIT( nnn ) ====
	This code tells the game to load a specified map, using a number. The valid map numbers are 1 through 114.		This code tells the game to load a specified map, using a number. The valid map numbers are 1 through 114.

Kalvinis: /* SC_ENEMY_SCRAMBLE_MODE2 */

2021-11-24T19:50:14Z

SC_ENEMY_SCRAMBLE_MODE2

← Older revision		Revision as of 12:50, 24 November 2021
Line 93:		Line 93:
	==== SC_ENEMY_SCRAMBLE_MODE2 ====		==== SC_ENEMY_SCRAMBLE_MODE2 ====
	This code uses an enemy table from ''ENEMY_TBL_nnn'' (located in the relevant .lua file) to spawn enemy units into the map. Here is an example code: ''SC_ENEMY_SCRAMBLE_MODE2( ENEMY_TBL_000, ScDifficulty_HIGHLEVEL, ScScramble_ONMAP, SCBIT_SCRAMBLE_NOP, SC_POS(0, 0) );''		This code uses an enemy table from ''ENEMY_TBL_nnn'' (located in the relevant .lua file) to spawn enemy units into the map. Here is an example code: ''SC_ENEMY_SCRAMBLE_MODE2( ENEMY_TBL_000, ScDifficulty_HIGHLEVEL, ScScramble_ONMAP, SCBIT_SCRAMBLE_NOP, SC_POS(0, 0) );''
	'''~~ENEMY_TBL_xxx~~''': This determines what enemy table to call from the .lua file.		'''ENEMY_TBL_nnn''': This determines what enemy table to call from the .lua file.
	'''ScDifficulty_xxx''': This determines what enemy table to use from the .lua file, depending on either difficulty selected or average level of units (unsure, needs research). There are 3 determining codes (currently): NORMAL, HIGHLEVEL, NOT_HIGHLEVEL.		'''ScDifficulty_xxx''': This determines what enemy table to use from the .lua file, depending on either difficulty selected or average level of units (unsure, needs research). There are 3 determining codes (currently): NORMAL, HIGHLEVEL, NOT_HIGHLEVEL.
	'''ScScramble_xxx''': This determines how to summon the enemy table on to the map. There are 2 determining codes (currently): NORMAL, ONMAP.		'''ScScramble_xxx''': This determines how to summon the enemy table on to the map. There are 2 determining codes (currently): NORMAL, ONMAP.
	'''SCBIT_SCRAMBLE_xxx''': <To be filled in>. There are 3 determining codes (currently): NOP, LAND_FREE, TOP_ADJUST_CENTER		'''SCBIT_SCRAMBLE_xxx''': <To be filled in>. There are 3 determining codes (currently): NOP, LAND_FREE, TOP_ADJUST_CENTER
	'''SC_POS(x, x)''': <To be filled in>.		'''SC_POS(n, n)''': <To be filled in>.

	==== SC_GMMAP_INIT( xxx ) ====		==== SC_GMMAP_INIT( xxx ) ====
	This code tells the game to load a specified map, using a number. The valid map numbers are 1 through 114.		This code tells the game to load a specified map, using a number. The valid map numbers are 1 through 114.

Kalvinis: Start of filling in the TXT file section.

2021-11-24T19:21:46Z

Start of filling in the TXT file section.

@@ Line 30: / Line 30: @@
 ===mission_est010_en.cpk LUA Files===
-This file contains information about the type of units that will exist in a given map, broken down into the entities below.
+These files contain information about the type of units that will exist in a given map, broken down into the entities below.
 ==== SC_DEBUG_PLAYER_ENTRY and SC_DEBUG_CLEAR_ENTRY ====
@@ Line 87: / Line 87: @@
 Creates a scripted battle with pre-determined damage.

Timpkmn89: /* OPERATE_TBL */

2021-11-24T02:48:43Z

OPERATE_TBL

← Older revision		Revision as of 19:48, 23 November 2021
Line 83:		Line 83:

	Configures what strings to display on the mission operations page for victory/defeat conditions and hints. The actual conditions are managed as part of the .txt file.		Configures what strings to display on the mission operations page for victory/defeat conditions and hints. The actual conditions are managed as part of the .txt file.

			==== EVENTBTL_nnn ====

			Creates a scripted battle with pre-determined damage.

Timpkmn89: /* mission_est010_en.cpk */

2021-11-23T05:08:50Z

mission_est010_en.cpk

← Older revision		Revision as of 22:08, 22 November 2021
Line 19:		Line 19:

	===mission_est010_en.cpk===		===mission_est010_en.cpk===
	This file holds the main/non-DLC missions of Super Robot Wars 30. This file is located in [SRW30\pc\data\mission]. The ~~majority~~ of files in ~~this~~ .~~cpk container are structured as such:~~		This file holds the main/non-DLC missions of Super Robot Wars 30. This file is located in [SRW30\pc\data\mission]. The first file (numbered "0") is a table of contents for the game to use. The remaining files are human-readable files for each mission. Depending on the mission type, each mission will have up to 5 files. However some missions with multi-part battles (such as the initial Gridman missions) may have multiple sets of 5. They have been stripped of their names in the encryption process, but their original filename is at the top of each file and they are listed in order of internal mission number.

	~~.lua [contains unit information for battles]~~		In order:

	.txt ~~[contains~~ script ~~code~~ for battles]		* ____.lua - Unit-related data for battles
			* ____.txt - Overall engine script for the mission. Handles dialogue, deployment, special effects, flags, victory/defeat, etc. Despite the file name, it is a valid LUA file.
	~~(3)~~ .pyc ~~files [first 2 contains dialogue for pre-battle\|during battle\|post~~-~~battle, last file contains~~ AI ~~data~~]		* ____.pyc - Non-combat dialogue scripts, for both before and after battles. Generated from cse10_[missionnumber]_SDemo.Cpp
			* ____.pyc - Combat dialogue scripts. Generated from cse10_[missionnumber]_DlgEv.Cpp
			* ____.pyc - Enemy AI configuration. Generated from aie10_[missionnumber].xls

	===mission_est010_en.cpk LUA Files===		===mission_est010_en.cpk LUA Files===