v1.0.4 parche
Tables load exactly where you placed them, bot naming and a new update checker
Parche IncompatibleCrítica prioridad
9 nov 2026Script Billiards
Qué cambió
5cambios
Tables load exactly where you placed them, bot naming and a new update checker
5cambios
[02] Versión
Pool tables now load exactly where they were placed, and Config.BotAI is renamed to Config.BotSkill to follow the Cfx and Tebex rules. The server console gets a new update checker.
config/config.lua, rename Config.BotAI to Config.BotSkill. Keep your values; only the name changes. The old name is no longer read.qs_pool_tables table changes. On the first start after updating, the resource copies each table's position into a new coords column and drops the old cx, cy, cz and heading columns. Nothing to run by hand. Back up the table first if you may want to go back to the previous version. If the table does not exist, the resource now creates it on start.play_bot_desc changed in every language ("against the bot" instead of "against the AI"). If you edited it, re-apply your text.Replace every file in the resource, except what you edited yourself:
client/bot.lua.config/config.lua — Config.BotAI renamed to Config.BotSkill.server/ — main.lua, version.lua.shared/utils.lua.database/sql.sql — only used on new installs.locales/ — every language (play_bot_desc).fxmanifest.lua — version only.Renamed to follow the Cfx and Tebex rules. It holds the same per-difficulty values and the bot plays exactly as before. Rename it in your `config/config.lua` when you update.
The menu now reads "Create a match against the bot", to follow the Cfx and Tebex rules.
Replaces the old version check. When the resource starts, the console shows your version, the latest version and whether you are up to date. When an update is available, it lists what changed and links to the full changelog.
Table positions were saved as one number per axis. A whole-number value, such as a heading of 90, could load back as 0 or as an invalid number, so a table could spawn facing the wrong way, in the wrong place or not at all. Decimals also lost precision. Positions now save in a single `coords` field and always load as exact decimals. Existing tables are converted automatically on the first start.