:: It's highly recommended to edit button layout there. You can drag buttons directly, or tap to choose one button, then slide in an empty place to change it's shape. There will be words above to inform you what this button is.
:: There are 7 buttons and 2 joysticks in total. You can't remap ''Text input button'' and joysticks. It's highly recommended to turn off the ''Joystick1'', or you can't jump while running, or start to run without jumping. To turn off it, tap into the option and follow the picture.
::Mapping a button to a key actually makes it '''behaves''' just like the key. For example, if you map ''button 1'' to ''A'', then ''button 1'' will be completed the same as the ''A'' on the keyboard.
::The name of the button being mapped is on the top. You don't need to care about its usage according to its name. Also, the button usually have a default mapping. We recommend to map buttons to ''A'', ''D'', ''SPACE'', ''X'', ''PAGEDOWN''. That's because A,D,Space have already been bound by default, meaning you don't have to bind them again if you map the button to keys that have been bound already.
::Also, you have to '''replace''' the button to '''fire'''. It is ''mouse1'' by default. To trigger ''mouse1'', you have to tap empty place on the screen. However, you can't trigger ''mouse1'' while holding on-screen buttons. If you don't change, it will be hard to play. We recommend to remap a on-screen button to fire, for example, map the ''button 6'' to ''WORLD_55'', then bind world_55 "+fire".
::If you quit remapping before all buttons are remapped, the settings that have been made will be saved, and the settings for the remaining buttons won't change. After remapping, go change the button layout, and the work for on-screen buttons is done.
::Usually, our device has volume keys and a back button. These buttons might be hard to reach while playing, so don't make them needed to be used very usually. Firstly, press one of the physical keys in the interface shown in the picture.
</div>
[[File:MBexample3.jpeg|upright=|thumb|right|<span lang="en" dir="ltr" class="mw-content-ltr">Tap a physical key there</span>]]
::You can map physical keys to mouse1, but that doesn't make any sense. If you want to do that, choose ''Mouse emulation'', then ''Left mouse click'', then ''Physical key'', then just tap one of the physical keys. You still need to touch the screen to move the cursor though.
::Another unique advantage is that they can be bound easily. You can bind physical keys and mouse1 in a DDNet interface called ''Controls''(PC ddnet has this as well). In that interface, all on-screen buttons will disappear, you can only activate physical keys and mouse1, meaning you can only bind them freely there.
::4 gestures in total, they are ''Zoom in'', ''Zoom out'', ''Rotate left'' and ''Rotate right''. Similar to physical keys, they can't be triggered easily like the on-screen buttons. So give them a less used function.
::All two-finger gestures are bound to ''UNKNOWN'' by default. This is a invalid key, you can't bind them in ddnet. You have to map them to a valid key first.
::To do these gestures, you need to put only two fingers on the empty locations on the screen. For ''Zoom in/out'', move two fingers away '''from/close''' to the center.(Imagine you are zooming a picture). For ''Rotate left/right'', you can let one finger stay still, then move another finger around the silent one.
::Another problem is, when triggering ''Rotate right'', usually ''Zoom out'' will be triggered at the same time. I seldom trigger other buttons by mistake, that is the only problem, you can try yourself.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Remap_Note"></span>
=== Remap Note ===
=== 映射注意事项 ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
#请记下每个按键对应的映射，之后绑定会省去不必要的麻烦。
#Please write down or memorize every button what it's mapped to. Or you will suffer while binding later.
#To make sure the key you map to has no bindings that you don't know by chance, you can map buttons to keys like "World_X". They are not bound by default.
#映射结束后，你可以重新进入映射界面以查看映射是否存在问题。上一次映射保存的按键会显示在最上方。
#After remapping, you can renter the mapping interface to check if the buttons are mapped correctly, the mapping will be shown at the top normally.
#如果你要像图片那样放置按钮
#If you are going to place buttons like the layout shown in the picture
, you'd better place the space button a little higher. Or bugs will cause while you are trying to kick a tee.(Tap the button ''A'' or ''D'' then ''Joystick 2'' then ''Space'', with a fast speed, the buttons may suddenly be useless unless you release all fingers on screen. The solution is to place space button a little higher, or you just move the finger higher while tapping space button).
#In the ''Mouse emulation'', you can set the ''Calibrate touchscreen''. Touch 4 edge of the screen, then exit.
#All mappings will be activated after you leave this interface and enter ddnet. Meaning all gestures and mappings for physical keys are inactive.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Remap_Example"></span>
=== Remap Example ===
=== 映射举例 ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
::Button 1: A
::Button 1: A
::Button 2: SPACE
::Button 2: SPACE
Line 152:
Line 111:
::Button 5: PAGEDOWN
::Button 5: PAGEDOWN
::Button 6: WORLD_55
::Button 6: WORLD_55
::Volume+: RCTRL
::音量+: RCTRL
::Volume-: LALT
::音量-: LALT
::Back: RETURN
::返回键: RETURN
::Zoom in: WORLD_5
::Zoom in: WORLD_5
::Zoom out: ESCAPE
::Zoom out: ESCAPE
::Rotate left: K
::Rotate left: K
::Rotate right: F1
::Rotate right: F1
::Explanation: You '''must include''' ''RETURN'', this can't be changed. This is the setting of ForgottenCat.
::The key CTRL and ALT don't exist, instead, we have ''LCTRL'' and ''RCTRL'', ''LALT'' and ''RALT''. When binding, we can't bind ctrl as well. We need to bind rctrl "...".
You can set your own name upon first entering. Then you will see this page. Clear the search box upon the ''Host Address'', you can see servers. The ''DDNet'' and ''LAN'' option has no server in. If you want to join a ''LAN'' server, just change the ''Host Address''.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
如果你刷新太快，搜索引擎会停止工作，手机版ddnet刷新比较慢。如果你看到右下角显示''x of 1000+ servers''，说明刷新很成功，之后慢慢等待即可。
If you refresh too fast, it may stop working, the refresh is slow on mobile ddnet. For the perfect refresh you can see ''x of 1000+ servers'', then just wait.
Tap the gear at the top right corner to enter the setting interface. In the option ''Controls'' you can bind your ''mouse1'' or physical buttons conveniently.
There is a '''special''' option in ''HUD'': ''Show Chat''. If you turn it off, the ''text input button'' will act weirdly. Normally when using the button, you will open chat automatically, then you can input messages. But turning ''Show chat'' off will prevent the chat from entering. For example, you input "/lock", you will ''kill'', because the last word of /lock is K, and k is bound to ''kill''. So if you input "yyyyyyk", you will also kill.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
现在，随便进入一个DDNet服务器，然后开始绑定。
Now, get into a random DDNet server, and start binding.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Basic_Bindings"></span>
=== Basic Bindings ===
=== 基础绑定 ===
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
按下被映射为''F1''的按钮，之后你可以用文本输入按钮来输入指令。
Press the button that is mapped to ''F1'', then you can use the ''Text input button'' to input commands.
If you decided to use an on-screen button to fire, it's recommended to bind mouse1 to spectate. Because while spectating, you have to hold the screen to choose which who you want to spec. If you bind another button to spectate, you need to hold that button and the screen at the same time.
After all these settings, your mobile ddnet is now playable! You can now beat most easy maps, but if you are going to higher difficulties, you will find serious problems. You can choose whether to skip mode switch key, but I recommend you not to read them if you are not very familiar with DDNet, or you aren't planning to be a pro in mobile ddnet.
There are too many bindings, but we don't have that many buttons to use. Also, commands like "bind ctrl+a" is not usable in mobile ddnet. So mode switch key is the best solution.
Firstly, you need to know Config Files, and you need to know basic commands. You must place your config files in /storage/emulated/0/Android/data/tw.ddnet/files/data/. Take care that there is a folder named "data", and it has the same content as the current folder. Placing files in there will do nothing.
The ''Mode switch key'' is used for bind lots of buttons to another usage. For example, I create a config file called "on.cfg". The following commands are what's inside.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
*bind a "zoom+"
*bind a "zoom+"
*bind d "zoom-"
*bind d "zoom-"
*bind rctrl "exec off.cfg"
*bind rctrl "exec off.cfg"
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
然后，创建另一个名为"off.cfg"的配置文件，以下为其中包含的指令。
Then, create another config file called "off.cfg". The following commands are what's inside.
Firstly, you use the key, the key ''a'' and ''d'' can now zoom, and the mode switch key can now execute the "off.cfg". When you finish zooming, use the rctrl again, the key ''a'' and ''d'' can now make you move, and the key ''rctrl'' can now execute ''on.cfg''. As you see, ''rctrl'' is considered as a mode switch key there, it can temporarily change the binding of other buttons and have the ability to reset them after using. This is similar to "bind rctrl+a", but mobile ddnet does not support this, so we have to make a small change.
Sounds easy right? But there are more you need to care about while creating your own mode switch key. Firstly, the key that will be changed shouldn't be changed by mode switch key. For example, deep fly will change the binding of fire button. After changing, you need to use the mode switch key to reset bindings. But if it will reset the binding of fire button, the deep fly bind just disappear.
Another issue is, you can't let the key can be triggered by accident. Triggering mode switch key by accident is usually fatal, it may deprive you of your ability to move, if your mode switch key has something to do with move buttons. Take physical keys such as volume keys as mode switch keys is a good option, they can't be triggered easily.
To know which mode you are currently at, using emote is a good choice. Upon entering setting mode, show an afk emote, and upon resetting, show a happy emote. This can prevent you from misunderstanding.
You shouldn't to relate screen gestures to mode change keys. They can't be triggered if you can't release hook for a period of time, and they are easily triggered by accident.
:Your hook usually breaks itself, especially in hf parts, endless, and dummy drags. Avoid situations that you must hold hook for a long time or you will die. If it's not avoidable, release all your buttons before starting to hook, then touch hook joystick only. After this you can start moving, and try not to release your finger which is on the moving buttons. This is a useful way to prevent this bug from occuring.
:In some hookthrough part or rehook part, you will find your hook won't release even though you release your finger. The only way to deal with this problem is to tap your joystick for another time. Of course this is not useful most of the time. A map named ''Polarity'' is a good example, this map is way harder for mobile players because of this bug.
:A more common issue is you can't release on-screen buttons, it usually occurs when you are holding your hook joystick, you just can't release your move buttons. The solution is to touch move buttons before jumping. Jump, then move while holding hook at a fast speed will 100% cause this bug.
:Of course, sometimes your move button will release itself. Probably because you are releasing hook joystick. Lots of hook part requires you to drag dummy, go back, then go forward and get a faster speed to pass through some freeze zone, which means you probably need to release hook. The solution is, when you release your hook, just quickly tap the hook joystick again, then your move button will recover.
:If you placing ddnet client in the background, or something like this, when you come back, your entity will be completely white or something you can't understand most of the time. And if you repeat the action, everything will just collapse. Just reopen the game can fix this problem.
:Sometimes after using /load, the collision between two tees will act very weird, seems very laggy. The solution is, just don't enter solo mode before /load. If you can't, use /timeout or entering a solo tile after /load.
:The text input button can't input full-width characters such as Chinese characters. If you do that, the game will crash normally. But maybe, this bug only occurs on certain devices. However, if you open the input interface without using text input button, the game won't crash if you input full-width characters. For example, change your name in the setting input box. And, for some reason, if you get into a server, don't connect your dummy, and write some Chinese characters in the input box without using that button, then you may temporarily get the ability to send full-width characters without crashing the game.
:Normally, the solution is to create some config files. Placing commands like '''player_name''' or '''say'''. Then while playing you can f1 and execute those files to help you swaping, changing name, or sending messages.
'''/storage/emulated/0/Android/data/tw.ddnet/files/data/''', there you can find every texture. Just replace the original texture without changing the file name. The entity texture is in the ''editor'' folder, its name is '''entities_clear.png'''. If you want to add skins, put files in the ''skins'' folder. ''x_ninja.png'' is the default skin when tee is in freeze. Replace it without changing the file name can change the in-freeze skin.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Example"></span>
== Example ==
== 设置样例 ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
这是ForgottenCat目前的全局设置，希望对你有所帮助。
This is the current setting of ForgottenCat, hope this will help you!
That's all, thx for reading! Playing ddnet on phones and pads is very convenient for us, and can provide us a new experience. However, I don't want you to play this just because you want to show yourself. Of course, the mobile version is hard to play, hard to set well, but this is not the excuse to ask others to help you more than normal. We mobile players are not the disabled, with enough practice even the insane maps are not our limitation. Good luck and have fun!
