You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the bot supports dedicated servers from DatHost.net, would it be possible to use the bot without it? Meaning all functionalities except for the server host integration part?
I am running a local dedicated server, so I am in no need for servers via DatHost.net.
The text was updated successfully, but these errors were encountered:
You can use the bot without DatHost, it should run everything up until it tries to start the server and it'll fail. You might need to put in blank values for the Dathost config fields otherwise the settings might not load. I should probably allow an option to disable actually spawning the server (gracefully).
It would be possible to add a feature to use a local server too, but I'd like to possibly find some sort of way to reduce the amount of work necessary when it comes to configuring & start/stopping a local CS2 server. Back in CSGO it would be fairly trivial to have a server running a plugin like Get5 and then simply drop in a config or use their existing API, but there aren't any solutions yet for CS2 that I am aware of (please feel free to share if something exists). It might be possible to simply do all of the interaction via RCON though.
This is definitely something I wanted to get around to doing, so I'll keep this up for feedback and possible implementations.
Alright, I'll see if I can test the bot without the DatHost functionality and see if it works.
I do not know if it is possible, but I have tried this cs2 plugin which is working great: https://github.com/shobhit-pathak/MatchZy
Right now the bot supports dedicated servers from DatHost.net, would it be possible to use the bot without it? Meaning all functionalities except for the server host integration part?
I am running a local dedicated server, so I am in no need for servers via DatHost.net.
The text was updated successfully, but these errors were encountered: