¶ Before collecting logs
Before you collect your logs ensure you have re-created the action which lead to the errors. I.E. if you're having an issue that only happens after you do something in game, make sure the logs include that action.
For Example, if you cannot uncuff someone after cuffing them in the LEO script, ensure that in the timeframe of the log you have gone in game, cuffed someone, then attempted to uncuff them. If you are utilizing the in game method of log collection for the client DO NOT CLOSE OUT OF THE GAME. As soon as you close out of the game the client logs will be lost and you will need to access them via the file system.
Please,
DO NOTsubmit screenshots of your logs to the support team and pleaseDO NOTcopy and paste the log into the textbox in the ticket. We can't read that. UploadTHE WHOLE LOG.
¶ Collecting Server Logs
¶ txAdmin
The txAdmin team made server log collection very easy, simply log into your txAdmin panel:
Click on Live Console
Then, in the bottom right of the console window click Download or in older versions of txAdmin there is a blue button that says Download Logs
Submit the file to your BigDaddyScripts ticket, and wait for the support team to respond based on the logs provided.
txAdmin logs should show for the entire day and reset at midnight server time.
¶ File System
File System guide will only cover
Windowsbased machines. If you are usingLinuxsome of this may still be relevant but specific termonalogy may not apply
If you need to access logs further back than the current day, or you don't use txAdmin, you can find the logs in your server files. Simply open File Explorer on your Windows Machine.
Locate your logs folder, if txAdmin is installed it will be in txData/[name of the server]/logs
Scroll down until you see fxserver.log
From here you can select the current fxserver.log or any previous logs. Submit the file to your BigDaddyScripts ticket, and wait for the support team to respond based on the logs provided.
¶ Collecting Client Logs
¶ In Game
After performing the actions that lead to the issue, press F8 to open your Client Console, then click the blue Open Log button in the bottom right of the console.
After Clicking Open Log your editor of choice will open up (this will likely be vsCode or NotePad), click File>Save As
Save the file somewhere accessable then submit it to your BigDaddyScripts ticket, and wait for the support team to respond based on the logs provided.
¶ File System
File System guide will only cover
Windowsbased machines. If you are usingLinuxsome of this may still be relevant but specific termonalogy may not apply
If you need to access logs further back than the current session, you can find the logs in your server files. Simply open the Local App Data folder on your Windows Machine. You can do this quickly by using the shortcut key Win+R and typing %localappdata% and hit ENTER.
Locate your FiveM folder then your FiveM Application Data
Next, open the Logs folder and select the log you want to share.
Submit the file to your BigDaddyScripts ticket, and wait for the support team to respond based on the logs provided.