diff options
| author | Freeyorp <TheFreeYorp+github@gmail.com> | 2018-03-23 21:09:32 +1300 |
|---|---|---|
| committer | Freeyorp <TheFreeYorp+github@gmail.com> | 2018-03-23 21:09:32 +1300 |
| commit | 6e559e0a621030b51c3590b5e163b4d9554b410a (patch) | |
| tree | eaf66831ae7ebc90b60b8aa9c8d72f7c2cac733e /README.md | |
| parent | 190672e6da2f3fd3bb740ba886693b0e3c3727ba (diff) | |
| download | tmwa-6e559e0a621030b51c3590b5e163b4d9554b410a.tar.gz tmwa-6e559e0a621030b51c3590b5e163b4d9554b410a.tar.bz2 tmwa-6e559e0a621030b51c3590b5e163b4d9554b410a.tar.xz tmwa-6e559e0a621030b51c3590b5e163b4d9554b410a.zip | |
Fix NPC script softlockv18.3.22
When an NPC called destroy; from an attached script, npc_id, and
associated state, was not properly cleared. This meant that the
server considered the PC to still be in conversation, preventing
many actions including walking, but with an invalid NPC.
This clears state for the specific case of the a PC attached to
the script instance that called destroy. It is still not safe to
call destroy; if other players may be attached to it.
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions