These opcodes' names should be self-documenting.
Client:
Type 1 opcodes (2 bytes, len, data)
Not all of these expects any data, even though they
technically can. Some of them only expects certain types
of data (as string, short, long, char..), but this has not
been reversed yet.
uni_start_stream 00 01
uni_end_stream 00 02
uni_data 00 0E
man_set_context_relative 01 0A
man_set_context_index 01 0B
man_end_context 01 1D
de_data 03 01
// mail
mip_start_message 11 00
mip_header_complete 11 01
mip_end_message 11 02
mip_start_block 11 07
mip_end_block 11 08
mip_addressee 11 09
mip_subject 11 0A
mip_text 11 0B
mip_attr_addressee_type 11 13
mip_attr_data_type 11 14
mip_attr_file_name 11 15
mip_attr_file_size 11 16
mip_preset_message_id 11 2B
mip_change_message_status 11 2C
mip_read_mail 11 31
It should be possible to get all the opcodes that exist by
using the Master Tool (internal AOL tool), but the data file
that specifies the names of the opcodes is encoded in some
way.