Since 3423df1 the server followed an animal switch ("as") with that
animal's "ad" and full "il". The client swaps animals partway through the
transform animation: at "hideAvatar" it copies the in-world avatar into the
switcher slot being left, then loads the new animal onto the in-world one.
The extra "ad" arrived before that frame, had no request waiting for it, and
so was applied to the in-world avatar, and the "il" then matched it too. The
slot got a copy of the new animal, the old one was gone from the switcher,
and the other slots drew blank until the next login.
This reverts 3423df1. A newly bought animal's editor not opening until the
next login comes back with it and needs a fix that goes through the
client's own "ad" request.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Switching animals ("as") changed the active animal, but the client keeps
an editor model of each animal and was never sent the new one's data or
clothes, so an animal bought this session showed in the switcher and its
editor would not open until the next login. The switch is now followed by
its "ad" and its full item list.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Ping on prod jumped to seconds because node's main thread was busy most
of every second.
- accounts.save(account, ...) names the changed accounts, which are
written within a second; the rest are looked at a few at a time
(10 ms a save for those in play, 5 ms for the others). One save under
prod-like load: 289 ms before, 16 ms after.
- an asset the CDN does not have gets a cacheable 404 and is logged once
- the proxy's own connections no longer count against the web cap, which
had node reset requests nginx had already let in
- a repeated client error is written once in ten minutes; the panel's
log buffer trims in batches
- the daily backup uses sqlite's online backup off the main thread