Write the resource once.
Run it on VORP or RSG.
Wild Country Libs sits between your RedM resources and whichever core framework the server runs. One set of functions for player data, money, notifications, prompts, and Discord logging — the lib figures out the rest.
-- same call, every server
wc:AddMoney(source, 50)
wc:Notify(source, { title = "+$50" })-- VORP: currency index 0 = cash
character.addCurrency(0, 50)
Core.NotifyAvanced(source, "+$50", 'itemtype_textures', 'itemtype_cash', 'COLOR_WHITE', 4000)-- RSG: named money type
Player.Functions.AddMoney('cash', 50)
lib.notify({ title = "+$50", type = 'success' })Why Wild Country Libs exists
Most RedM resources are written hard against one framework's exports. Switch cores — or just write a second resource for a server that runs the other one — and every character.addCurrency or Player.Functions.AddMoney call has to be found and rewritten by hand. Wild Country Libs removes that step: your resource calls wc, and wc_libs calls whichever core is actually running.
→ One API surface
GetMoney, GetPlayer, GetJob, Notify, Revive — call the same function regardless of which core is installed.
→ Auto-detected, overridable
Wild Country Libs checks which core resource is running on start. Force it with one config flag if you ever need to.
→ Nothing hidden
Need something the bridge doesn't cover? WCLib.Raw.VORP() and WCLib.Raw.RSG() hand you the native core object directly.
→ Built from real resources
Every helper — prompts, blips, ped spawning, Discord embeds — was extracted from working Wild County RP code, not written speculatively.
Browse the API
Grouped the way you'll actually reach for it — server-side player/money/data on one side, client-side world/UI helpers on the other.