[INFO] Starting RAGE Multiplayer server...
[============================================================]
||
|| MaxPlayers 100
|| Sync rate 40ms
|| Name RAGE:MP Unofficial server
|| Gamemode freeroam
|| Streaming distance 500
|| Announcement disabled
|| Voice chat disabled
|| Address 127.0.0.1:22005
|| Connection limits disabled
|| Encryption enabled
|| NodeJS enabled
|| C# enabled
||
[============================================================]
:3: SyntaxError: Invalid or unexpected token
šrÀö
[INFO] Loading NodeJS packages...
[INFO] Starting packages...
(node:7956) UnhandledPromiseRejectionWarning: ReferenceError: mp is not defined
at file:///C:/Users/Administrator/Desktop/redage_v3/bin/loader.mjs:4:127
(Use
(node:7956) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
(node:7956) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[============================================================]
||
|| MaxPlayers 100
|| Sync rate 40ms
|| Name RAGE:MP Unofficial server
|| Gamemode freeroam
|| Streaming distance 500
|| Announcement disabled
|| Voice chat disabled
|| Address 127.0.0.1:22005
|| Connection limits disabled
|| Encryption enabled
|| NodeJS enabled
|| C# enabled
||
[============================================================]
:3: SyntaxError: Invalid or unexpected token
šrÀö
[INFO] Loading NodeJS packages...
[INFO] Starting packages...
(node:7956) UnhandledPromiseRejectionWarning: ReferenceError: mp is not defined
at file:///C:/Users/Administrator/Desktop/redage_v3/bin/loader.mjs:4:127
(Use
ragemp-server --trace-warnings ...
to show where the warning was created)(node:7956) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)(node:7956) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.