Better Shell Owner options

[Panthanaea]

It would be nice to have a functionality that would allow us to auto-boot people from a shell that are using over a certain number of triangles or a certain ram threshold. It was something I really wished I had more control over in Mare.

It would also be nice to be able to hard deny things on a shell like VFX and Animations rather than just "suggested" settings.

[HorribleBee]

Problem:
User at his own house alone testing mods and getting kicked out of Syncshells for putting on a mod without compressed textures, even if a timeout is implemented there will be situations where the user is complying with limits in one syncshell but still getting warnings from another.
It will be horrible to be in multiple syncshells at the same time if they all have different rules.

Behavior idea:
Auto-boot doesn't auto-kick, user receives a notification in chat and in toast that he is above threshold, the yellow triangle icon is placed in the same area where the "guest" icon is right now to notify the user he is beyond limits, it overwrites the guest icon.
In the admin panel, users above threshold also have the yellow triangle.
Users that go past the threshold are not synced, effectively paused by the entire syncshell.

Mods/Admins will receive a warning and the triangle but won't be paused.

[Panthanaea]

Behavior idea: Perhaps instead of boot, pauses their access to that shell? Shell members who are paused due to ram/triangles reset after admin-defined time? Default of 6hrs. Admins can manually unpause before timer is up if user adjusts counts.Behavior idea 2: Autolimiter off by default when creating Shell, and has to be manually turned on via the Shell Menu like the custom passwords or recommended perms.Behavior idea 3: Encourage mod makers to pause their shells when testing? Paused shells should not recieve data, allowing people to not get booted/paused.Sent from my T-Mobile 5G Device -------- Original message --------From: HorribleBee ***@***.***> Date: 9/21/25 10:44 AM (GMT-07:00) To: universalconquistador/MareSynchronosClient ***@***.***> Cc: Panthanaea ***@***.***>, Author ***@***.***> Subject: Re: [universalconquistador/MareSynchronosClient] Better Shell Owner options (Issue #104) HorribleBee left a comment (universalconquistador/MareSynchronosClient#104) Problem: User at his own house alone testing mods and getting kicked out of Syncshells for putting on a mod without compressed textures, even if a timeout is implemented there will be situations where the user is complying with limits in one syncshell but still getting warnings from another. It will be horrible to be in multiple syncshells at the same time if they all have different rules. Behavior idea: Auto-boot doesn't auto-kick, user receives a notification in chat and in toast that he is above threshold, the yellow triangle icon is placed in the same area where the "guest" icon is right now to notify the user he is beyond limits, it overwrites the guest icon. In the admin panel, users above threshold also have the yellow triangle. Users that go past the threshold are not synced, effectively paused by the entire syncshell. Mods/Admins will receive a warning and the triangle but won't be paused. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>