but thos files get created after launching bam5 client once
13:41
before that they are not in there
13:42
(relaunching bam5 client does not change the error)
13:43
i do can use my VisualStudio 2017 project generated by CMake but its full of potential errors ( because every single code base is splitted in different projects ....)
What do you guys think about not counting a wrong rcon password twice?
Imagine some has a rcon_auth bind and unluckily presses it multiple times he gets a ban. But if we ignore duplicated wrong passwords that could be saver
I experience getting banned regularly when restarting the client for a setting to take effect. Would it be possible to make this condition more gentle?
imo the server can stay as trigger happy but the vanilla client should simply sanitize user input and even if the user spamms enter/esc or what ever limiting the connection attempts
Added deployment to appveyor, circleci and travicci to enable automatic trunk builds.
os:
win64
win32
unix
osx (mac)
It adds 4 releases (for each os), which are automatically updated and overwrit...