I remember Purus mentioning that when he started making the current (only fan forked/maintained) version of Purus Pasta, Multi-session was the first thing he implemented on top of the Default. This way everything else will have to be fundamentally implemented in a way that works with the multi-session.derkami wrote:I'll look into the zoom stuff.. It happens because of UI scaling.
Multi-Session Support is not easy, because there is stuff that will prevent it from running or will crash every so often.
But that's on my bucket list...
Adding multisession to current Kami could be the equivalent of trying to swap the foundations for an already-built skyscraper.
Lesser pitfalls include the having to choose between
A) "Every instance blasts their entire audio simulaneously" (which granted, is the case when running the entire clients in multiples.)
B) Non-active session are muted. Implies a chance that you come back to a neglected session(s) to find dead character(s).
The latter option could be alleviated if the Session widget had support for status symbols or something to indicate that there's combat etc. going on.
