diff options
| author | Thorbjørn Lindeijer <bjorn@lindeijer.nl> | 2025-02-26 10:35:48 +0100 |
|---|---|---|
| committer | Thorbjørn Lindeijer <bjorn@lindeijer.nl> | 2025-02-26 10:39:56 +0100 |
| commit | bc9a68bd584e572386ef8d21179d1c1eac513775 (patch) | |
| tree | 2869a9836e25af4d4817b94e9938eb2d76b52857 /include | |
| parent | 2d32c37a5639d76f34f83d3a929677efa46962a5 (diff) | |
| download | tmwa-being-spawn-message.tar.gz tmwa-being-spawn-message.tar.bz2 tmwa-being-spawn-message.tar.xz tmwa-being-spawn-message.zip | |
Re-enable SMSG_BEING_SPAWN (0x007c) with additional fieldsbeing-spawn-message
This packet was disabled with the comment "manaplus is skipping this
packet". In fact, that isn't entirely true: M+ uses this packet to set a
"spawn ID" so that it can later trigger the spawn action after the being
is created.
Rather than just re-enabling this packet, I've added some additional
data (hp, max_hp, attack_range and sex) using previously unused fields,
which makes sending SMSG_BEING_VISIBLE (0x0078) obsolete. Starting with
client version 9 (M+ and Mana are currently on version 8), we now send
either SMSG_BEING_SPAWN or SMSG_BEING_VISIBLE.
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions