Action Button Script

Description

Action Button (Click / Collision / Universal Command Controller) Version 1.7.1 Unified interactive command controller Turn any object into a powerful interactive trigger with MPP – Action Button. Featuring a fully unified command system, this script lets you create anything from simple one-action buttons to complex multi-state interactive systems — all with a clean and intuitive setup. Each button can hold 1 to 4 commands, sent either as chat messages or Script Events, enabling a wide range of use cases: lighting systems, mechanisms, gameplay logic, environment control, and more. Supports both click and collision activation, as well as remote control via Script Events, allowing synchronization and automation across your entire scene. Enhanced with advanced visual feedback (tint + emissive), users always clearly understand the current state. Choose exactly who can use each button (everyone, owner only, owner + whitelist, or everyone except a blacklist), and visitors are politely told how long to wait while the button is cooling down — no more "is it broken?" moments. New in 1.7.1: the settings are grouped by category in the Build panel (Activation, Access, Command, Remote, Sound, Visual, Debug), and the access control uses the same Permission Mode + Whitelist + Blacklist scheme as every MPP script. Fully standalone, yet perfectly compatible with all MPP systems. ________________________________________ Key Features • Unified 1–4 command system • Click or collision activation • Send chat messages or Script Events • Built-in cycling system (multi-state logic) • Remote control via Script Events • Visual feedback with tint and emissive • Optional interaction sound • Configurable cooldown (per avatar or global) • Private "please wait" notice during cooldown • Access control by Permission Mode: owner only, owner + whitelist, everyone except a blacklist • Whitelist and blacklist of avatar handles or UUIDs • Private message for denied visitors • Optional: hide the button from denied visitors • Startup state initialization • Material filtering support • Settings grouped by category in the Build panel • Works on any object ________________________________________ Unified Command System Command Count = 1 • Single action button • Always sends the same command • Visual: flash + fade back Command Count = 2–4 • Cycles through commands • Each click advances to next state • Each state has its own tint and emissive ________________________________________ Access Control Decide who can use each button with one number and two lists: • Permission Mode 1 — Owner only • Permission Mode 2 — Owner + the avatars of the Whitelist • Permission Mode 3 (default) — Everyone, except the avatars of the Blacklist (empty list = everyone) The lists accept avatar handles or UUIDs, separated by commas. The scene owner can never be locked out, even by mistake. Denied visitors receive a short private message (customizable, or silent). Optionally, denied visitors do not even see the button as clickable. Tip: turn Debug Logging on and click with an avatar to show its handle and UUID in the script console, ready to paste into a list. ________________________________________ Cooldown & Anti-Spam • Per-avatar or global cooldown • Private notice in Nearby Chat: "Please wait 3 seconds before using this button again." • Fully customizable text with {time} (e.g. "2 minutes 30 seconds") or {seconds} • At most one notice every 3 seconds per avatar: informative, never spammy • Built-in double-click protection, even with the cooldown set to 0 • Lightweight cooldown engine, stable even under heavy clicking ________________________________________ Advanced Visual Feedback Tint • Single command: flash + fade • Multi-command: persistent color per state Emissive • Per-command intensity control • Automatically restores initial value Applies to: • all materials • or a specific material ________________________________________ Remote Control System Control buttons externally via Script Events: • Reset buttons globally or individually • Force specific states (Command 1–4) • Synchronize systems across your scene Event format: <prefix>[_token]_set_X <prefix>[_token]_reset Tip: set your master reset button to Permission Mode 1 (owner only), so visitors cannot reset your scene. ________________________________________ Technical Details • Commands: 1 to 4 • Activation: Click or Collision • Output: Chat or Script Event • Access: Permission Mode 1–3 with Whitelist and Blacklist • Cooldown system (global or per avatar) with private notice • Spatial sound support • Full visual feedback (Tint + Emissive) • Configurable Initial Command • Built-in Remote Control • 36 optimized properties, grouped by category ________________________________________ Example Uses • Light switches • Control panels • Owner-only admin panels and master reset buttons • VIP or staff-only controls • Multi-mode buttons (speed, ambiance, etc.) • Interactive doors • Puzzle systems • Invisible triggers • Script synchronization • Debug tools ________________________________________ Full documentation online: https://mpp-mainstore.com/sansar/ActionButton/ ________________________________________ Updating from 1.7.0 — please read • Take a screenshot of the Build panel of each button whose access you had changed BEFORE updating the script. • All your settings are kept, except the three access settings: Owner Only, Access List and List Is Blacklist are replaced by Permission Mode (1–3), Whitelist and Blacklist, which start at "everyone can use the button". • After the update, set the access again on those buttons: Owner Only On → Permission Mode 1 (or 2 with your list in the Whitelist); Owner Only Off with a blacklist → Permission Mode 3 with your list in the Blacklist. Buttons that let everyone click need nothing. • Commands, Script Events and Remote Control events are unchanged: the scripts that listen to your buttons keep working. Changelog — Version 1.7.1 • Settings grouped by category in the Build panel: Activation, Access, Command, Remote, Sound, Visual, Debug. • Access control by Permission Mode (1 owner only, 2 owner + whitelist, 3 everyone except blacklist), with separate Whitelist and Blacklist, the same scheme as every MPP script. • Labels: "Collision Mode" is now "Use Collision", "Visual" is "Visual Feedback", "Emissive" is "Affect Emissive", "Debug" is "Debug Logging". Same settings, same values. • Module listed as "MPP - Action Button", without a version number in its name. • 36 properties, as in 1.7.0; only the three access settings are new (see "Updating from 1.7.0" above). Changelog — Version 1.7.0 • Added private cooldown notice (customizable text, anti-spam) • Added access control: owner only, whitelist or blacklist of avatar handles or UUIDs • Added customizable message for denied visitors • Added optional hiding of the button for denied visitors (click mode) • The scene owner can never be blocked • New lightweight cooldown engine • Built-in double-click protection • More robust chat, Script Event, sound and material updates under heavy use • Clear warnings in the log for inconsistent settings • Sound Volume 0 now fully mutes the click sound • Debug log now shows the avatar handle and UUID • 29 → 36 properties, all V1.6 property names kept Changelog — Version 1.6 • Introduced unified command system • Removed legacy Single/Sequence modes • Simplified parameters (34 → 29) • Added full Remote Control system • Enabled remote control for single-command buttons • Added per-command emissive control • Improved naming consistency • Increased flexibility and clarity ________________________________________ Enjoy and Keep Good Vibes. Hugs from Morgane. ________________________________________