Forum Discussion
XHelperZ
3 years agoHero+
I've noticed this too.
S16 brought the 2.0 revision, which brings new launch parameters.
Refer to the config file in the LiveAPI folder, it contains the new parameters.
I've copied it over for ease:
// Sample config.json // Refer to the readme.txt for more info on these options { // Live API general settings "settings": { // Enable Live API 2.0, which includes websockets and protobuf support "cl_liveapi_use_v2": true, // Use WebSockets client and connect to a server "cl_liveapi_use_websocket": true, // Allow the API to process requests from a WebSocket connection "cl_liveapi_allow_requests": true, // WebSockets client networking options "cl_liveapi_ws_retry_count": 5, "cl_liveapi_ws_retry_time": 5, "cl_liveapi_ws_timeout": 300, "cl_liveapi_ws_keepalive": 10, // Use protobuf as the serialization format. Otherwise, use JSON. "cl_liveapi_use_protobuf": false, // When using JSON, whether to use human readable formatting "cl_liveapi_pretty_print_log": false }, // List of websocket servers Apex should connect to "servers": [ "ws://127.0.0.1:7777", ] }// Sample config.json // Refer to the readme.txt for more info on these options { // Live API general settings "settings": { // Enable Live API 2.0, which includes websockets and protobuf support "cl_liveapi_use_v2": true, // Use WebSockets client and connect to a server "cl_liveapi_use_websocket": true, // Allow the API to process requests from a WebSocket connection "cl_liveapi_allow_requests": true, // WebSockets client networking options "cl_liveapi_ws_retry_count": 5, "cl_liveapi_ws_retry_time": 5, "cl_liveapi_ws_timeout": 300, "cl_liveapi_ws_keepalive": 10, // Use protobuf as the serialization format. Otherwise, use JSON. "cl_liveapi_use_protobuf": false, // When using JSON, whether to use human readable formatting "cl_liveapi_pretty_print_log": false }, // List of websocket servers Apex should connect to "servers": [ "ws://127.0.0.1:7777", ] }
3 years ago
I've already used the config files, let me send a copy for you
- XHelperZ3 years agoHero+
Seems like I got confused, the parameter seems to be indeed broken.
Thought I had resolved it but seems like I was mistaken.
Well, guess we'll just have to wait for a fix.
About Apex Legends Technical Issues
Having issues with Apex Legends? Join here to find help with connectivity, performance issues, crashes and more.37,914 PostsLatest Activity: 2 hours ago
Community Highlights
- EA_Blueberry7 years ago
Community Manager
Recent Discussions
- 10 hours ago
- 11 hours ago