Mar 7 2016, 9:32 pm
|
|
Somepotato
 |
Understandable. Not sure how the server handles appearances so was just throwing out baseless ideas.
|
In broad strokes:
- Any time a movable is sent to the client and it is marked as having changed appearances, its appearance is sent if it hasn't been already. - Any time a turf or area is sent to the client, its appearance is sent if it hasn't been already. - Appearances that are part of any animation relevant to the client are sent, if they haven't been sent already. - Any time an atom is sent as part of output or a statpanel, its appearance is sent if it hasn't been sent already. A flag of the kind you suggested would be very much at odds with the above behavior, requiring more in-depth checks any time an appearance was sent. | |
It'd only need to be checked for sending the map to clients, but then it might be better as a non-appearance flag.
| |