stefan-kolb / aoc-mgx-format Goto Github PK

Hi!

I'd like to do some parsing of your text files, could you please license this repo under MIT or WTFPL maybe?

I'm working on figuring out what changed between the MGX and MSX format (AOE2HD v4.3). Will you be working on this too?

Hey, I'm doing a full analysis on the AoC network protocol over here and I might have some info for you.

1. 0x00 is also used for boarding a transport ship.
2. The value 0xff for selected_unit_count is meant to be a reference to previously selected units. Whenever this turns up, it translates to "Do that action with the units from the previous command". This construct saves a lot of bandwith.
3. The action 0x67 is used for diplomacy (allied, neutral, enemy), but is also used for cheats and maybe other action like "resign". In the network protocol it looks like this

67 — command
00 — context (different values for cheat, diplomacy, etc.)
01 — player_id_1 (who sends the offer)
00 — zero
02 — player_id_2 (who receives the offer)
00 00 00 00 00 — zero
40 40 03 — relation
00 00 00 — attacker id

The values for relation can be 00 00 00 (allied), 80 3f 01 (neutral) and 40 40 03 (enemies). When using cheats, the player_id_2 field is used. Cheats start at value 0x65.

EDIT:

4. Action 0x7e is dropping a relic.
5. Action 0x1b is Save & Exit.

def Research
    int8 :command
    int24 :zero?
    int32 :object_id
    int16 :player_id
    int16 :technology_id
    int32 :constant?
end

Most actions (related to units?) always start with 4xint8 data, int32 object_id, ...