{"id":9904,"date":"2024-02-05T09:20:01","date_gmt":"2024-02-05T08:20:01","guid":{"rendered":"https:\/\/esx-scripts.com\/?p=9904"},"modified":"2025-08-27T08:44:21","modified_gmt":"2025-08-27T06:44:21","slug":"conserto-do-crewphone","status":"publish","type":"post","link":"https:\/\/fivemx.com\/pt\/crewphone-fix\/","title":{"rendered":"CrewPhone: Solu\u00e7\u00e3o essencial para o problema de hash imposs\u00edvel"},"content":{"rendered":"

How to Fix CrewPhone Hash Problem (###)<\/strong> <\/p>\n

Many players who use the CrewPhone (or gcPhone) addon on their FiveM servers find themselves staring at a seemingly random number like ###-####<\/strong> instead of the expected full phone number. It\u2019s a subtle but disruptive glitch that stops players from being able to place calls, send messages, or use the in\u2011game phone at all. If you\u2019ve hit this snags, you\u2019re not alone, and the solution is quite straightforward. <\/p>\n

—<\/p>\n

CrewPhone Hash Problem: Quick Fix <\/h2>\n

The culprit is usually a missing client\u2011side event that tells the server when a player has fully loaded into the game. Without this tiny notification, the server-side script that generates phone numbers often falls back to a default sequence, producing the placeholder numbers you see. The fix is to fire a server event as soon as the player\u2019s loadout has been restored. <\/p>\n

Here\u2019s the full, ready\u2011to\u2011copy snippet you can drop into your `client.lua` (or an equivalent Es_extended client script): <\/p>\n

“`lua
\n— Trigger a server event as soon as the player has loaded
\nTriggerServerEvent(‘crew:onPlayerLoaded’, GetPlayerServerId(PlayerId()))<\/p>\n

— Example: Attach to the existing loadout restoration hook
\nAddEventHandler(‘esx:restoreLoadout’, function()
\n local playerPed = PlayerPedId()
\n local ammoTypes = {}<\/p>\n

— Remove any pre\u2011existing weapons
\n RemoveAllPedWeapons(playerPed, true)<\/p>\n

— Re\u2011give the player their loadout
\n for _, weapon in ipairs(ESX.PlayerData.loadout) do
\n local weaponName = weapon.name
\n local ammoType = GetPedAmmoTypeFromWeapon(playerPed, weaponName)<\/p>\n

— Add weapon to the ped
\n GiveWeaponToPed(playerPed, weaponName, 0, false, false)
\n SetPedWeaponTintIndex(playerPed, weaponName, weapon.tintIndex)<\/p>\n

— Add any weapon components
\n for _, component in ipairs(weapon.components) do
\n local componentHash = ESX.GetWeaponComponent(weaponName, component).hash
\n GiveWeaponComponentToPed(playerPed, weaponName, componentHash)
\n end<\/p>\n

— Add ammo only once per type
\n if not ammoTypes[ammoType] then
\n AddAmmoToPed(playerPed, weaponName, weapon.ammo)
\n ammoTypes[ammoType] = true
\n end
\n end<\/p>\n

— Tell the server the player has fully loaded
\n TriggerServerEvent(‘crew:onPlayerLoaded’, GetPlayerServerId(PlayerId()))<\/p>\n

isLoadoutLoaded = true
\nend)
\n“`<\/p>\n

All you need to do is paste this block above the rest of your client\u2011side code, ensuring it runs immediately after the player\u2019s data is fully restored. <\/p>\n

—<\/p>\n

Why the Event is Crucial <\/h2>\n

In a typical FiveM server running Es_extended, player data (including the phone number) is stored on the server and fetched each time a player joins. The client script then sends a \u201cplayer loaded\u201d event back to the server so that the server knows all required assets (weapons, clothes, phone data) have been applied. <\/p>\n

If that event is missing, the server can\u2019t correctly link the phone number to the player object\u2014leading it to fall back to either: <\/p>\n

1. A default, unreadable hash<\/strong> (the infamous `###-####`), or
\n2. No number at all,<\/strong> which forces the client to request a new one, causing the same glitch again. <\/p>\n

By firing `crew:onPlayerLoaded` at the right moment, you give the server a chance to bind the freshly loaded player object to its stored phone number. The hash conversion portion of the script then correctly transforms that number into a readable format. <\/p>\n

—<\/p>\n

Step\u2011by\u2011Step Setup Guide <\/h2>\n

1. Locate Your Client Script<\/strong>
\n Find the `client.lua` (or a similarly named file) within your `es_extended` or `CrewPhone` resource folder. <\/p>\n

2. Insert the Trigger<\/strong>
\n At the very top of the file, add:
\n “`lua
\n TriggerServerEvent(‘crew:onPlayerLoaded’, GetPlayerServerId(PlayerId()))
\n “`
\n This ensures the event fires even before any other logic runs. <\/p>\n

3. Update the Loadout Hook<\/strong>
\n Search for the `AddEventHandler(‘esx:restoreLoadout’, function()` line.
\n Replace or augment the handler with the complete example shown above. <\/p>\n

4. Save and Reload<\/strong>
\n Save the file, then run the following in your server console:
\n “`bash
\n apply_pgsql
\n restart CrewPhone
\n restart es_extended
\n “`
\n Alternatively, simply restart the entire server to ensure all changes take effect. <\/p>\n

5. Test<\/strong>
\n Join the server, equip a weapon, and open your in\u2011game phone. The number should now appear correctly, e.g., `012-3456`. <\/p>\n

—<\/p>\n

Troubleshooting Common Issues <\/h2>\n

| Problem | Possible Cause | Fix |
\n|———|—————-|—–|
\n| Phone number still shows as `###-####` | Event not firing (e.g., script order wrong) | Double\u2011check that the `TriggerServerEvent` line appears above any other function definitions. |
\n| Server logs show `ERROR: crew:onPlayerLoaded` | Mis\u2011named event on the server side | Verify that the server script<\/a> listens for `crew:onPlayerLoaded` (usually in `server.lua`). |
\n| Player receives a different<\/strong> number each time | Number regeneration on load | Ensure `crew:onPlayerLoaded` triggers only after the loadout is fully applied; the snippet above handles this. |
\n| Game crashes when loading weapons | Incorrect weapon hash or component value | Confirm the ESX version you\u2019re using matches the snippet\u2019s API (some older versions use `GetWeaponComponent`.) |<\/p>\n

—<\/p>\n

Alternatives if the Script Doesn\u2019t Work <\/h2>\n

Although the above solution works for most setups, you might still face challenges if your server runs custom scripts or a different framework. Here are a couple of alternative approaches: <\/p>\n

1. Directly Call the Phone Registration Function<\/strong>
\n “`lua
\n TriggerServerEvent(‘crew:registerPhone’, GetPlayerServerId(PlayerId()))
\n “`
\n Some CrewPhone variants expose a `registerPhone` event that forces the server to generate a new number regardless of the loadout status. <\/p>\n

2. Patch the Server\u2011Side Number Generator<\/strong>
\n Locate the server script that handles `crew:onPlayerLoaded` and ensure it includes:
\n “`lua
\n if not playerData.phone then
\n playerData.phone = GeneratePhoneNumber()
\n end
\n TriggerClientEvent(‘crew:setPhoneNumber’, src, playerData.phone)
\n “`
\n This forces a proper number to be set even if the client didn\u2019t request one. <\/p>\n

—<\/p>\n

Expanding Beyond the Hash Problem <\/h2>\n

Fixing the hash problem is just one part of having a polished phone system on your server. To get the meeste value out of CrewPhone, consider adding: <\/p>\n

– Custom Call Sounds<\/strong> \u2013 Replace the default ringtone with localized genres.
\n– Messaging Spam Protection<\/strong> \u2013 Implement cooldowns to avoid players flooding the chat.
\n– Contacts Import<\/strong> \u2013 Allow players to import contacts from a shared database for easier management. <\/p>\n

Each of these enhancements can be tackled later, but by starting with the hash fix you\u2019ll eliminate a major friction point for your players. <\/p>\n

—<\/p>\n

Conclusion <\/h2>\n

The CrewPhone hash problem<\/strong> is a minor glitch that can feel like a major roadblock. By ensuring the client fires the `crew:onPlayerLoaded` event right after a player\u2019s loadout is restored, you signal the server to link the correct phone number, eliminating the placeholder `###-####` display. Implement the snippet above, test it, and you\u2019ll have a seamless phone experience for your players. <\/p>\n

Quick recap: <\/p>\n

1. Insert the event trigger<\/strong> at the top of your client file.
\n2. Patch the `esx:restoreLoadout` handler<\/strong> with the detailed code example.
\n3. Restart the server<\/strong> and verify the number shows correctly. <\/p>\n

With these steps, the CrewPhone hash problem will be a memory of the past, allowing your community to enjoy a fully functional in\u2011game telephone system. Happy gaming!<\/p>\n","protected":false},"excerpt":{"rendered":"

Com dificuldades para gerar n\u00fameros no CrewPhone? Um ajuste r\u00e1pido no es_extended client.lua far\u00e1 com que seus n\u00fameros sejam exibidos corretamente em segundos!<\/p>","protected":false},"author":1,"featured_media":1309,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1900],"tags":[],"class_list":["post-9904","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-troubleshooting"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/posts\/9904","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/comments?post=9904"}],"version-history":[{"count":0,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/posts\/9904\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/media\/1309"}],"wp:attachment":[{"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/media?parent=9904"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/categories?post=9904"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fivemx.com\/pt\/wp-json\/wp\/v2\/tags?post=9904"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}