Aizik’s redeem system combines a Discord bot that creates reward codes with a FiveM /redeem command. The original preview credits Aizik#5555, matching the Aizik5/AiziksRedeem repository. Its latest commit is dated 26 December 2020; the old claim of regular updates and compatibility with every framework is unsupported.
What the code actually does
Authorised Discord users can create a code for money or an inventory item and send it to a mentioned user. The FiveM handler looks up the code, credits bank money for type money or adds an inventory item for other types, then deletes the code. There is no separate weapon-reward handler.
The database stores code, type and amount. It does not bind redemption to the Discord recipient or an in-game character, and it contains no expiry field. Sending a code privately does not make it recipient-restricted.
Legacy requirements and setup gaps
The FiveM directory is Aizik_Reedem. Its code uses the legacy esx:getSharedObject event, mysql-async and mythic_notify. The accompanying ReedemBOT is a separate Node.js process using discord.js 12. The bot imports mysql, but mysql is missing from both its package manifest and lockfile. This is not a verified install-and-start package for current ESX or Discord.
codes.sql selects a database named essentialmode. Review the database name and schema before any import, and back up existing data. Keep bot tokens and database credentials private. The archived README is historical setup documentation, not evidence that its old runtime instructions remain suitable today.
Redemption checks required before public use
The Lua handler accesses the first database result without checking whether a code exists. It also lacks a player-object check. Rewarding and deleting the code are separate asynchronous operations, so concurrent requests are not protected by an atomic claim.
The bot builds its INSERT statement by concatenating input and uses Math.random for codes. It also assumes a mentioned user exists and does not fully validate numeric reward amounts. A maintained implementation needs parameterised queries, validated rewards, unpredictable codes and an atomic single-use claim. Recipient binding and expiry must be added if required by your rules.
The original screenshot is retained as a historical preview. Source inspection did not include running the bot, connecting to Discord, importing its SQL or testing rewards in FiveM. Review and repair the implementation before deployment.