#Node.js exiting (exit code 0)
1 messages · Page 1 of 1 (latest)
:rocket: Congratulations @slender crystal, you leveled up to <@&828359841512816671>!
Back at it again
I know you may not like this but I keep getting overlooked and I would like some guidance @crisp prawn
You just violated our rules, consider this a warning.
Please use this 60 seconds to read our #rules, if you violate them again you will be muted.
then show a full screenshot instead of the useless part of the message
Sounds good , I will take a screenshot
!reserror
@slender crystal
The issue you are having is likely caused by some resource.
:point_right: Steps you can take to troubleshoot and pinpoint the cause:
:one: First check your txAdmin > Live Console and look for errors;
:two: On the CFG Editor and try disabling all resources one-by-one (or in groups) until it starts working again;
:three: Try updating your txAdmin/FXServer;
:four: Go to txAdmin > Settings > FXServer and try different OneSync Options.
:five: Go to txAdmin > Settings > FXServer and take note of the two paths, then go to txAdmin > System > Master Actions > Reset FXServer and deploy a new server with the CFX Default recipe. If it works then that will confirm that the issue is related to a resource. Now you can go to the settings and restore the paths to go back to your previous server before the reset.
No errors on the console , and Ive upadated to latest, iIve set up a servber all over again to try to find out whats going on
follow step 5
try removing waveshield
Its my anticheat
i know