Tablet System Pro — Changelog

All notable changes to this pack are recorded here.

The format follows Keep a Changelog and the pack follows Semantic Versioning.

The version below must always match the one declared in Runtime/AssemblyInfo.cs — that is the version the FOS Hub shows, and the one the Hub compares against the installed Core.

---

[Unreleased]

Nothing yet.

---

[1.1.0] — 2026-08-25

Added

• The role matrix now warns you when the founder role cannot assign roles. That setting locks an instance without a word in game: whoever opens it can hand out no role at all, and the automatic succession does not step in, since it only promotes a player who can already assign roles. It stays a warning, not an error — the setup is fine as long as the people who matter are in the account list with a role that can assign.

---

[1.0.2] — 2026-08-22

Fixed

• No role could be ticked in a role gate. Clicking a checkbox set the value and stopped there: the inspector never wrote it back to the component, so the next repaint read the old value and the box emptied itself again. Nothing was ticked, ever, and nothing said why. The same hole applied to the arrival points, where assigning a Transform did not stick either — nobody had run into that one yet. Reported by a customer.

---

[1.0.1] — 2026-08-22

Fixed

• The role matrix was not being saved. Roles defined in the window came back as the four original ranks, and a role gate offered those instead of yours. A component has two halves — the one you edit in the inspector, and the one that runs — and the windows were writing only the first. UdonSharp periodically copies the running half back over the edited one, notably when leaving Play mode, and that copy erased the matrix. The same applied to the account list and to the example generator. Reported by a customer, and the report was exactly right.

---

[1.0.0] — 2026-08-20

First release.

Requires FOS Tablet System Standard 2.1.0 and FOS Essentials Core 1.1.0.

Pro adds components beside the Standard ones. It replaces nothing on your prefab, so adopting it costs none of the wiring you already did, and everything keeps working exactly as before until you open the role matrix and change something.

Added

• Role matrix — FOS Essentials > FOS Tablet System Pro > Role Matrix. As many roles as your world needs, each with its own permissions, name, translation key and grant ceiling. One row per role, one column per permission.
• Account roles — FOS Essentials > FOS Tablet System Pro > Account Roles. A list of display names and the role each holds, as a floor: arrived with, restored after a crash, promotable above for one instance, never pushed below. CSV export and import, with search.
• Role gate — a component put on the object itself, ticking the roles that may see it. It never touches its own GameObject: a behaviour on a disabled object stops running and could never switch itself back on. Without an explicit target it drives its direct children.
• Role spawn — one arrival point per role. It waits for the real role rather than sending everyone to the arrival point and correcting itself, which would show as a visible round trip on every staff connection.
• Removing a role renumbers the world. Any role can go, not just the last one. A role is an index: removing role 2 slides 3 down to 2, and everything pointing above the gap would start naming its neighbour — the staff gate opening to greeters, the admin arrival point receiving moderators. Nothing would fail and nothing would show. So the window rewrites the grant ceilings, the founder and arrival roles, the account list, and every role gate and arrival point of the open scenes. What lives in another scene, or in a prefab never instantiated, keeps the old numbers — the dialog says so.

Guard rails

The windows refuse or flag what turns against its author. None of these look wrong at the moment they are ticked; all of them only show their consequence in a live instance.

• A role granting above its own rank creates someone more powerful than itself — flagged in red. A role granting its own rank recruits peers without limit — a warning, and only on roles that are not the highest, since that is exactly how a top role delegates.
• No role able to open the staff panel: no moderation possible at all.
• No role able to edit the community settings: rules and adult content locked for everyone.
• Removing a role tells you what it moves before it moves it: how many accounts hold it and which role they fall back to, how many gates and arrival points are rewritten.
• A role gate that shows to nobody, or to everybody, is pointed out.

Known limits

These come from the platform, not from the pack. Both are stated in the windows themselves so nobody meets them in production.

• The account list is baked into the world. Adding or removing someone takes effect only after uploading again. A role granted from inside the game would need to be stored somewhere trustworthy, and VRChat offers a world no such place — player persistence is written by the player’s own client.
• A rename loses the entry. Udon exposes no account identifier, only the display name.