🔄 Updating from 1.5.1

This page is for servers still running the public 1.5.1 TGG Casino & Slots package. Newer releases have breaking changes. Do not merge files one-by-one — replace the whole resource folders, then re-apply only editable customizations.

1. Who this is for

• You are on 1.5.1 (or an older public build) and want the current package.
• You customized config.lua and/or server/custom / client/custom bridges and need to re-apply those edits after the replace.

2. Backup first

Before you touch anything:

1. Backup your database (MariaDB / MySQL dump of the schema used by slots).
2. Copy your old resource folders somewhere safe (zip or rename them, e.g. tgg-slots-server-1.5.1-backup).
3. Note your current server.cfg ensure list and any ACE lines you added for admins.

SQL tables still migrate automatically on start, but a DB backup is required if you need to roll back.

3. Replace entire resource folders

1. Stop the server (or stop all TGG slots/casino resources).
2. Delete (or move aside) every old TGG slots/casino resource folder you are updating.
3. Drop in the new package folders as shipped — full directories, not partial overlays.

Replace all resources in your package the same way (tgg-slots-server, game resources, props/interior if included, table games, etc.).

4. Update server.cfg ensure list

Start dependencies and the core server first, then games. Add new resources only if they are in your download / purchase.

lua
Copy
-- Core dependencies
ensure oxmysql
ensure ox_lib
ensure ox_target

-- Framework (your resource name)
ensure es_extended or qb-core or qbx_core

-- Optional interior / props (when included in your package)
ensure tgg-slots-interior
ensure tgg-slots-props

-- Core
ensure tgg-slots-server

-- Table games (when included)
ensure tgg-casino-tables

-- Slot games you own
ensure tgg-slots-fruit-cocktail
ensure tgg-slots-lucky-fruits
ensure tgg-slots-plinko
ensure tgg-slots-orbit

-- Newer games / engines (only if purchased / present in the package)
ensure tgg-slots-sweet-spin
ensure tgg-slots-golden-frog
ensure tgg-slots-custom

Table games must start after tgg-slots-server.

5. Re-apply only editable customizations

Do not restore old copies of config.defaults.lua, config.internal.lua, or escrowed core files.

Re-apply from your backup

Typical config.lua choices to restore

In tgg-slots-server/config/config.lua:

• Config.Framework, Config.Target, Config.Inventory, Config.Phone
• Config.AdminAcePermission / Config.AdminCommandsPermission
• Safezone, death guard, jackpot screen/TV model lists, CCTV model lists (as needed)

In your table-games config/config.lua (folder tgg-casino-tables):

• Config.Framework / Config.Target (often inherit from slots-server)
• Config.Banking, Config.Inventory
• Bet tiers / game-specific options in the per-game config files above

Custom bridges

Re-copy only your real edits under:

• server/custom/frameworks, inventory, phone (slots-server)
• client/custom/frameworks, target, functions (slots-server)
• server/custom/banking, frameworks, inventory and client/custom/** (casino tables)

Prefer re-applying edits into the new bridge files rather than overwriting a whole new file with an ancient 1.5.1 copy.

6. Significant changes since 1.5.1

Concise highlights (not a full changelog):

• Venues / casinos admin — place and manage machines, tables, layouts, and venue enable/disable from the lobby admin UI.
• Table games — roulette, blackjack, and 3-card poker via tgg-casino-tables + admin placement.
• Cashiers & dirty-money exchange — place cashiers, rates/methods, and related analytics in admin.
• Promos — lobby promos (spins, bonus wagering, contests, advertise flows) managed in admin.
• CCTV — place/inspect CCTV; editable camera model list in config.lua.
• Jackpot screens & TVs — machine toppers / world TV boards with admin assignment; model lists in config.lua.
• Custom slots — tgg-slots-custom engine + admin custom-games tooling (when purchased).
• New slot games — e.g. Sweet Spin, Golden Frog (when in your bundle).
• Admin permissions — dashboard/placement gated by ACE (Config.AdminAcePermission, default admin).
• Lobby branding — title, theme, hero banner, and related options via Admin Settings (DB).
• Config split — integrations stay in config.lua; runtime economy/game settings move to Admin / DB.

7. Where to configure now

See Configuration and Admin dashboard for details.

8. Restart and verify

1. Confirm ACE for staff, e.g. in server.cfg:

   Code
   Copy
   add_ace group.admin admin allow
   add_principal identifier.license:YOUR_LICENSE group.admin

   Match Config.AdminAcePermission if you changed it (QBCore often uses qbcore.admin).

2. Start the server once so SQL migrations can run.

3. Check the console for tgg-slots-server / table-games (tgg-casino-tables) errors.

4. Join as an admin → open the GoldLine lobby → confirm Admin tabs load.

5. Spot-check: deposit/withdraw, one slot game, cashier (if used), one table game (if ensured).

6. Confirm venues/machines still look correct; re-place or re-seed layouts only if something is missing after the upgrade.

9. Related docs

• Installation — dependencies and load order
• Configuration — editable Lua configs
• Admin dashboard — Settings, venues, promos, displays
• Phone app — YSeries / LB Phone lobby app (when enabled)