What problem does it solve?
This Skill removes the guesswork from building and maintaining Pawn database code for the BlueG a_mysql plugin, especially where older tutorials, mixed plugin conventions, and unsafe query patterns cause bugs.
Core Features & Use Cases
- Connection setup and packaging: Configure mysql_connect, mysql_connect_file, options, and sampctl dependency pins correctly.
- Threaded query workflows: Use mysql_tquery, mysql_pquery, callbacks, and OnQueryError for reliable server-side database operations.
- Cache and ORM handling: Read result sets by reference, manage saved caches, and build ORM-based login, registration, and persistence flows.
- Version and plugin disambiguation: Distinguish a_mysql from mysql_samp and migrate legacy code with the right calling conventions.
- Use case: A developer can use this Skill to refactor a broken login system into a safe, production-ready Pawn database layer with correct escaping, callback wiring, and cache cleanup.
Quick Start
Ask this Skill to review your Pawn MySQL code for BlueG a_mysql compatibility and generate a safe, tagged, callback-driven database pattern for your login or persistence flow.