okay so i still don't know if that's the good channel for part help, but I put it here
I have no idea what am i supposed to do for the second switch here on "SpeedRun", solo 4*
It's pretty painful since it feels like i can't be faster even tho i'm supposed to be faster.
a serious question, if solved many dummy players' lives will be easier: normally when u have a command like +fire, it should have a corresponding command -fire, but in ddnet console that doesn't exist (at least in the user interface). This causes a problem: when you switch between modes that has +fire and without +fire, if you happen to be holding mouse1 at the same time, the -fire will not register as "+fire" has been removed from the bind itself, this nullifies the first +fire command after the switch, and causes tremendous problems for dummy players like me. My questions are as follows: is there a way to manually call "-fire"? If not, is there any workaround that solves this problem?(edited)
1
05:32
also what is +fire anyways, why isn't there a -fire
05:37
it's basically resetonswitch except the main's hammer gets stuck instead of the dummy
a serious question, if solved many dummy players' lives will be easier: normally when u have a command like +fire, it should have a corresponding command -fire, but in ddnet console that doesn't exist (at least in the user interface). This causes a problem: when you switch between modes that has +fire and without +fire, if you happen to be holding mouse1 at the same time, the -fire will not register as "+fire" has been removed from the bind itself, this nullifies the first +fire command after the switch, and causes tremendous problems for dummy players like me. My questions are as follows: is there a way to manually call "-fire"? If not, is there any workaround that solves this problem? (edited)
So, firstly, is there even a "-fire" command in the game's cmd? if then, use your dummy switch bind to do that aswell as changing dummy i guess
08:48
But most dummy player just try their best switching when we don't hold anything.
There's one command which is "cl_dummy_reset" i think, what it does is literally your dummy is reset, but it stops hooking aswell so it's kind of bothering more than helping on harder maps(edited)
08:51
if you somehow like the "cl_dummy_reset", you can use "cl_dummy_resetonswitch 1" which does it everytimes you switch
some guys join servers(when i play) with ping ~200
16:42
and serv starts having lagspikes
16:42
how to ban them?
16:42
i cant votekick cuz there are not 5 players on nserv
𓆏 Kynilix 𓆏
But most dummy player just try their best switching when we don't hold anything.
There's one command which is "cl_dummy_reset" i think, what it does is literally your dummy is reset, but it stops hooking aswell so it's kind of bothering more than helping on harder maps (edited)
maybe I haven't made myself clear, but this problem occurs not when I switch to my dummy, but rather switching between different modes (like half-deepfly to normal mode). As many other dummy players I try to avoid switching when holding anything, but in some insane maps where intensive switching is required this problem occurs more than usual.
17:27
a very simple example: when I switch from deepfly to dummycopyfly (plant used this to get 0:57 on just fly 1), and then to deepfly again, because the timing is so precise sometimes I hold my m1 down during the first transition, and on the 2nd transition I need to click twice for my +fire to work normally
17:28
u know how bad clicking twice to actually hammer is: basically if you hammerhit tees in freeze you miss the first hit, and you wouldn't even realize that your first hit wouldn't come out
this is posted in #developer but i'll post it again hoping someone will answer it:(edited)
17:39
I previously mentioned a problem which can be replicated like this:
Define 2 modes:
1. Half deepfly - "bind a bind mouse1 '+toggle cl_dummy_hammer 1 0'"
2. Deepfly - "bind b bind mouse1 '+fire; +toggle cl_dummy_hammer 1 0'"
if you connect your dummy, and press the keys in the following order:
b m1down a m1up m1down m1up b m1down (<- supposed to be +fire and +toggle cl_dummy_hammer 1 0, but try it, your main wouldn't actually +fire)
The problem is when you switch to Half deepfly mode, the "+fire" has been removed from mouse1, so I assume the second stroke wouldn't be registered, so your main is stuck in the +fire status
so during the last transition (...b m1down) you need to click twice (m1down m1up m1down) for your main to actually hammer once
is there any way to solve this problem?(edited)
1
1
2
1
