How do you turn off the IP within the Discord Log but so you still have it in the database?
can you make a version for esx not essentialmode server ?
[BanSql] An error happens for query "INSERT INTO banlist help ?
Hello, would it be possible to make a version for qbcore from oxmysql ??
Does this work with es_extended
cuz in console its saying “Couldn’t start resource BanSql.”
any fix for this…
ESX would have nothing to do with whether this resource would start or not. More than likely, you’re not satisfying all of the dependencies listed in the first post of the topic, two of which are abandonware(essentialmode, esplugin_mysql).
can i install essentialmode if i have es_extended? im dumb 
Newer ESX does not use ES. If you install it, you will begin to have issues with the two fighting over your users table, resulting in broken player loadins. The solution to your issue isn’t installing ES, it’s converting this script not to use it. ES hasn’t be updated in years so nobody should be installing it to their servers.
There’s not much this script needs from the ES framework, if you’re at all familiar with lua, the conversion wouldn’t be that hard at all. Another solution would be finding another script that does what you need as this resource is also abandoned and over two years old. Everything, including the FiveM artifacts has changed a lot in those two years. You’re much better off finding something that is designed to work with today’s FiveM out of the box.
yeah the es_extended came with the esx that was in the txadmin install thing
es_extended is not essentialmode. es_extended is ESX.
now i dont understand, im too dumb
maybe this will help GitHub - Yamsoo/BanSql-V2
Update is OUT!!!
1.2.0 - 2026-02-14
Major Change
- No need to use
sqlbanofflineto ban a player who has connected since the last server restart.
Added
- Update checker and improved version messaging.
- Update notification via Discord webhook configuration.
- Framework detection and command registration for multiple frameworks (ESX, QBX).
- Player load handling on resource restart.
- Database initialization with table creation for ban management.
- Token support in database tables and ban logic.
- Migration helper to add token column to existing tables.
Changed
- Configuration structure refactor for clarity.
- Database schema refactor: replace identifier with steamid and fivemid.
- Token column renamed to tokens for consistent handling.
- Command registration refactor and safer initialization order.
- Ban command logic refactor to streamline duration handling and use player data.
- ICheat ban command refactor for readability.
- Unban and search commands now normalize player name lookup (case-insensitive).
- Discord webhook config refactor and update notification wiring.
- Project structure reorganized under server/.
Fixed
- Syntax error in playerLoaded and proper function closure.
- Double ban console error and nil value in sqlbanhistory.
- Console command return info consistency.
- Issues #31 and #37.
- Typo fixes and minor cleanup (removed unused variable).
Removed
- Legacy __resource.lua in favor of fxmanifest.lua.
- database.sql file (handled by runtime initialization/migrations).
Notes
- No manual intervention is required for the database migration.
Version 1.3.0 — 2026-02-22
Added: New web administration interface for ban management with search and pagination.
Added: API endpoint for viewing and managing sanctions (UI-compatible).
Changed: Database migration updated for bansql (optimized bans/appeals schema).
Security: Strict validation of payloads for public endpoints.
Upgrade Notes:
Back up your database before running the migration.
(Optinal) Read the documented DB migration.
Thanks: Thanks to contributors and testers for their feedback and fixes.