unbindall
is also always written before all other binds to the config file and this was probably always the purpose of the command. But I don't know why this was necessary. When executing the config file you would not have any binds anyway since the client is just starting and it also appears like the config is first use...6e32967
Mention that email templates are automatically reloaded too - Jupeyy194 files changed, 186 insertions(+), 12287 deletions(-)
github:ddnet:core
as owner on crates.io to grant everyone who has push access to https://github.com/ddnet/ddnet to the cratesma
and autocomplete anywaygit init
$ git init
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: git branch -m <name>
development
to annoy everyoneNS_ERROR_FAILURE
is that a name resolve failure?FlagPos -= vec2((ScaleX - TileSize) / 2.f, ((ScaleY - TileSize) / 2.f) + (ScaleY / 2) * 0.75f);
(edited)FlagPos -= vec2((ScaleX - TileSize) / 2.f, ((ScaleY - TileSize) / 2.f) + (ScaleY / 2) * 0.75f);
(edited)foo
of size 3 but array expression has 5 elements sv_rescue_delay
works? Tooltip says "Number of seconds between two rescues".
But it only works with respect to spawn time, so e.g. value of 5 blocks me from using /r for the first 5 seconds of the run, but after that i notice no effect. Am i missing something? (edited)m_LastRescue
is never set ;Dm_LastRescue
is never set ;D m_LastRescue
is never set ;D sv_rescue_delay
doesnt seem to have the intended effect. The description states that it should set the "Number of seconds between two rescues". However, it only restricts rescue x seconds after spawning.
This seems to be the case because #2242 removed the line for updating m_LastRescue
, which i believe was not intended.
This PR reintroduces this line. I tested the change ingame. Now the server option does what you'd expect: Restricting rescue usage for x seconds after each...