ORDNANCE CONTROL / PROFILE MANAGEMENT
Weapon profiles
Access the armory.
Enter your administrator token to manage profiles, publish tuning changes, and enroll devices.
The server creates this indata/admin-token. Your token stays in this tab’s memory.Start with a platform
Create a profile from a rifle, emplacement, tank, drone, or jet preset.
Issued keys
| Object | Owner | Revision | Last check-in | Update delivery |
|---|
No devices yet. Create a key and add the receiver to an object.
Recent activity
From profile to in-world object
- Create and publish a profile. Choose your platform, adjust the stats, and select Publish. Draft changes do not affect live objects.
- Create an enrollment key. Enter the avatar UUID of the owner. Copy the description or use a notecard named
Arsenal Config. - Set the server address. In
receiver.lsl, setSERVERto your public HTTPS address. Localhost is only for this preview; Second Life needs a reachable server. - Add the modules. Put the receiver and runtime in the same root prim. Add effects.lsl for sounds, animations.lsl for optional avatar states, and controls.lsl for owner-only /7 draw, /7 sling and /7 reload commands. Projectile mode also needs a projectile object containing
projectile.lsl. - Attach and grant controls. The sample runtime fires with the left mouse button in mouselook. It reloads automatically. For vehicles, connect your controls using the documented linked-message interface.
- Publish changes. Online objects receive a refresh notification. A periodic check recovers missed messages. Access expires after ten minutes without a successful check.
Group access
Set the object’s group to the required group UUID and have the owner activate that group. This is an active-group check, not a membership lookup.
Trust and permissions
Description and notecard keys are enrollment credentials, not tamper-proof identity. Distribute scripts no-modify and use a trusted combat meter to validate damage. The sample raycast reports hits; an adapter must connect them to your chosen combat system.
Small by design
Runtime stats stay in linkset storage between restarts. Firing never makes an HTTP request. Animation and effects are optional modules.