Start with the tablet-specific installation guide
The LB Tablet installation guide specifies MariaDB 10.11 or newer, oxmysql and current server artifacts. Its database checker can create or repair tables when the relevant settings are enabled; the supplied tablet.sql is the documented fallback. Start the tablet after the framework and essential resources. Configure the optional tablet item for your actual inventory.
Media uploads require the chosen upload method and matching server-side API keys. Keep those values separate from the client configuration and out of public screenshots. OneSync requirements should be checked against the features enabled in the installed release.
Record your artifact, tablet release, framework, inventory and integrations before a staging installation. Take a restorable backup before any database change. This page reviews publisher documentation; Magnate has not installed the paid resource, modified a database or measured its performance.
For the separate smartphone resource, use our LB Phone setup guide. Similar branding does not make the two resources’ configuration files or app interfaces interchangeable.
Use MDT identifiers consistently
The LB Tablet MDT reference places definitions in lb-tablet/config/mdts.json. Each top-level key is a case-sensitive MDT identifier used by exports, dispatches and shared reports. Restart the resource after changing that file. The documented default definitions include Police, Ambulance, Fire and Mechanic.
The same reference supports copying an MDT with overrides. Its disabledTabs workflow requires an explicit empty tabs array, and matching type and id values identify an overridden copied tab. Keep a small change log so an inherited setting is distinguishable from one you deliberately replaced.
Write down the MDT identifier, framework job and expected capabilities as separate fields before editing. A name shown to players can look correct while another integration points at a different identifier. Use the exact key from the configuration when investigating routing rather than relying on the visible department label.
Test access with roles that should succeed and fail
The following is an original proposed acceptance matrix. Define the expected outcome from your community’s intended permissions before testing. It is not a claim that these particular roles or restrictions are configured by default.
Use a normal member, a supervisor and an unrelated job. Check whether each can view, create, edit and delete a test report. Then repeat the relevant checks after a role change and reconnect. App visibility, action availability and the saved result are separate observations.
For a copied department, compare its intended access with the source department instead of assuming inheritance matches your policy. Record the exact account role and report identifier. Do not use real player records for a demonstration when synthetic test records will answer the same question.
| Test account | Question to decide first | Evidence to retain |
|---|---|---|
| Ordinary department member | Which report actions should this grade have? | Expected versus observed result for each action |
| Supervisor | Which extra actions are intended? | Saved record before and after the action |
| Unrelated job | Should this MDT or shared report be accessible? | Access attempt and resulting state |
| Changed role after reconnect | Does access now match the new role? | Role, session and repeated result |
Read custom-app registration results
The LB Tablet client-export reference documents AddCustomApp returning a success boolean and an APP_ALREADY_EXISTS reason. RemoveCustomApp can return INVALID_APP or WRONG_RESOURCE; SendCustomAppMessage can return INVALID_APP. Capture the result of the actual call rather than treating a missing icon as the complete error report.
Treat the app identifier, owning resource and UI path as different values in your integration notes. A collision, ownership mismatch and missing recipient imply different next checks. Start with one minimal app so a routing mistake can be isolated before adding additional features.
On staging, register the app once, open and close it, then stop its resource and repeat the supported startup sequence. Record return values, console messages and whether stale entries remain. This is a suggested lifecycle test, not a universal restart fix.
Separate the embedded page from its tablet bridge
The LB Tablet custom-app guide describes data and functions imported into globalThis when the app loads. These include resourceName, appName, settings, onNuiEvent, onSettingsChange and fetchNui. Use the tablet’s own reference and template when building the embedded interface.
An HTML page loading successfully is one boundary. Receiving a message, fetching the expected data and responding to settings changes are additional boundaries. Test them independently, especially if a developer copied a phone-specific example into a tablet resource.
If a form appears but input stops responding, preserve the console trace and active resource state before changing code. Record what worked immediately before the failure and which boundary failed next. Reproduce with a minimal app before attributing the problem to the entire tablet.
Reconcile a complete workflow before rollout
Choose one representative workflow: create a synthetic report, attach an original test image, find it again, reconnect and confirm the intended account can still access it. Record expected ownership and access separately from whether the record exists.
If you integrate dispatch or jail, test the handoff through your chosen resources too. A tablet notification proves a narrower result than the correct downstream state. Keep a list of integrations not exercised and make the deployment decision using those limits.
Keep configuration changes and test evidence together so the next update has a repeatable baseline. The guide provides a review and test plan, not a compatibility guarantee, resource download or verified gameplay benchmark.
Questions, answered.
Is LB Tablet the same thing as LB Phone?
No. They have separate documentation and resource APIs. Check the tablet-specific installation and custom-app references even if both products are used on the same server.
Why does AddCustomApp report APP_ALREADY_EXISTS?
The documented export uses that reason for an existing app. Inspect the identifier and registration path for your installed release, and retain the actual return values before changing the integration.
Has Magnate tested an LB Tablet installation?
No. This page reviews the publisher documentation and proposes staging checks. It does not claim a purchase, installed resource, database migration or successful in-game workflow.
Sources & editorial notes
Source review: November 15, 2026. Platform announcements can change. This guide separates published facts from Magnate’s original analysis and preparation advice.
- LB Scripts — LB Tablet installation guide Reviewed November 15, 2026. Publisher documentation; no runtime test.
- LB Scripts — LB Tablet MDT reference Reviewed November 15, 2026. Publisher documentation; no runtime test.
- LB Scripts — LB Tablet client-export reference Reviewed November 15, 2026. Publisher documentation; no runtime test.
- LB Scripts — LB Tablet custom-app guide Reviewed November 15, 2026. Publisher documentation; no runtime test.
Published by an independent editorial brand. Read our editorial standards.