Log Event Handlers - Fivemora

fivemora-core/logeventhandlers is the main extension point for custom server integrations. You can trigger these events from any server-side script to standardize logs across your ecosystem.

Money

TriggerEvent('Fivemora:MoneyAdded', src, moneyType, amount, reason)
TriggerEvent('Fivemora:MoneyRemoved', src, moneyType, amount, reason)
TriggerEvent('Fivemora:MoneySet', src, moneyType, amount, reason)

Admin and moderation

TriggerEvent('Fivemora:AdminCommandAction', src, command, args, argString)
TriggerEvent('Fivemora:Admin:PlayerKicked', targetSrc, authorName, reason)
TriggerEvent('Fivemora:Admin:PlayerWarned', targetSrc, authorName, reason, actionId)
TriggerEvent('Fivemora:Admin:BanRevoked', data)
TriggerEvent('Fivemora:Admin:WarnRevoked', data)
TriggerEvent('Fivemora:PlayerBanned', data)

Reputation

TriggerEvent('Fivemora:CrimRep:Updated', targetSrc, metadata)
TriggerEvent('Fivemora:CraftingRep:Updated', targetSrc, metadata)

Reports

TriggerEvent('Fivemora:Reports:Created', src, {
    report = 'Player report text'
})

Direct logging alternative

If you want full custom payload control, call export directly:

exports['fivemora-core']:AddWebsiteLog(category, level, message, metadata, source)

Best practices for custom scripts

Always include source when player-related.
Keep metadata stable and structured.
Use clear action values (add, remove, set, kick, warn, etc.).
Avoid triggering server events from clients unless explicitly validated in your own flow.