DDNet 手機版教程
這是DDNet的手機版教程。請注意由於當前版本客戶端非常老舊，存在許多漏洞和問題，新版本正在開發中。
在閱讀此教程前，玩家需要先了解基礎的按鍵綁定知識，並弄清楚自己需要的功能。要尋求手機版的幫助，請在wiki、b站、Discord等地方諮詢ForgottenCat。因為大部分人對手機版了解不深，請勿過多叨擾。
教程中的設置僅供參考，請根據您的個人習慣適當修改。
如何下載
最新的手機版為9.3.1，僅支持安卓設備。點擊此處下載。 有些設備無法正常安裝，例如安卓版本不匹配。也許您可以嘗試使用Android Debug Bridge來安裝。
入門指南
初次啟動遊戲，您會看到「按下左搖杆跳躍（Tap left joystick to jump）」。此時重啟遊戲，將會出現一行字「更改設備配置（CHANGE DEVICE CONFIGURATION）」。請點擊它來進入設置界面。
此界面的所有更改會自動保存。
按鈕和重映射
手機版帶有重映射這一特殊的選項。因為電腦版通常使用鍵盤操作，按鍵本身已經命名，例如ctrl、alt等，可以直接綁定不同名字按鍵的功能。而手機版與之不同，在綁定按鍵的功能之前，必須先對按鈕進行命名。
以下三個選項與重映射有關：「屏幕鍵盤（On-screen keyboard）」、「物理按鍵重映射（Remap physical keys）」、「屏幕雙指操作（Two-finger screen gestures）」。
屏幕鍵盤 On-screen keyboard
- 該選項用於更改屏幕上的按鍵設置。
- 屏幕按鍵主題 On-screen keyboard theme
- 用於更改按鈕材質。默認設置為「Sun」，這是唯一一個會顯示搖杆觸碰位置的材質。
- 屏幕鍵盤尺寸 On-screen keyboard size
- 用於更改按鈕的可觸碰範圍。不推薦在此處更改。
- 按鈕圖案大小 Size of button images
- 用於更改按鈕的圖案大小，但是不會影響可觸碰範圍。
- 屏幕鍵盤透明度 On-screen keyboard transparency
- 用於更改按鈕的透明度。調整範圍在「透明（Invisible）」和「不透明（Non-transparent）」之間。
- 定製屏幕鍵盤樣式 Customize on-screen keyboard layout
- 用於更改屏幕按鍵布局。非常推薦在此處編輯按鈕圖層，您可以直接拖動按鈕擺放的位置，按下即可選中對應按鈕，之後在空白處滑動調整其形狀。同時會有文字顯示按鈕信息。
- 如果您的材質不是「Sun」，則會顯示為「Simple Theme」。
- 屏幕控制重映射 Remap on-screen controls
- 總共有7個按鈕和2個搖杆，其中「文本輸入按鈕（Text input button）」和搖杆不能進行重映射。建議禁用「搖杆1（Joystick 1）」，否則移動和跳躍會相互衝突。禁用方式請點進選項並參考圖片。
- Joystick 2是唯一可以出鉤的按鈕，請勿禁用。輕觸ok來保存設置並進入重映射界面，如圖所示。
- 被映射的按鈕在表現上與鍵盤按鍵一致。例如：如果你將button 1映射為A，那麼按下button 1將與連接鍵盤並按下A的功能完全相同。
- 頂部會顯示當前被映射的按鈕名。按鈕名字。按鈕通常有默認的映射。推薦將按鈕映射到A、D、space、X、pagedown/PgDn，因為這些按鍵已經默認綁定了和電腦端一致的功能，而無須重新綁定。
- 注意：您必須替換並重新綁定開火鍵。因為開火默認操作是滑鼠左鍵Mouse1，但是觸屏手機系統的點擊是手指觸碰界面空白處，這會導致在按住按鈕的時候無法開火。您可以嘗試作如下替換：將button 6重映射為world_55，然後將world_55綁定為「+fire」，或者根據您的喜好作其他重映射。
- 上面提及的默認綁定功能有：A=左移動；D=右移動；Space=跳躍；X=切換分身；PgDn=切換到下一武器；Mouse1=開火。
- 您在任何時候退出重映射界面，已有的設置都會被保存，未改變的內容則保持不變。在重映射設置好後，調整按鈕布局即可完成屏幕按鈕的設置工作。
物理按鍵重映射 Remap physical keys
- 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.
- Then press Show all keycodes. Other options don't work at all. Then map your physical keys freely. You can only map one key at the same time.
- 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.
屏幕雙指操作重映射 Remap Two-finger screen gestures
- 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.
- Normally we choose the Medium sensitivity. You can try yourself to see which option suits you best.
- 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. Similar situations seldom happen, you can try yourself.
Remap Note
- 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.
Remap Example
- Button 1: A
- Button 2: SPACE
- Button 3: D
- Button 4: X
- Button 5: PAGEDOWN
- Button 6: WORLD_55
- Volume+: RCTRL
- Volume-: LALT
- Back: RETURN
- Zoom in: WORLD_5
- Zoom out: ESCAPE
- Rotate left: K
- 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 "...".
Settings and Binding In-Game
Basic Settings
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.
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.
Remember, all changes made after entering ddnet could only be saved by exiting using the X at the top right corner.
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.
Now, get into a random DDNet server, and start binding.
Basic Bindings
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.
Mode Switch Key
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, create a config file called "on.cfg". The following commands are what's inside.
- bind a "zoom+"
- bind d "zoom-"
- bind rctrl "exec off.cfg"
Then, create another config file called "off.cfg". The following commands are what's inside.
- bind a "+left"
- bind d "+right"
- bind rctrl "exec on.cfg"
Then, go into game, tap f1, input "exec off.cfg", the key is now usable. Let's see what the key can do.
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.
Two mode switch key is enough for now, just two volume keys. Too many mode switch keys will make you confused.
Bugs and Solutions
- On-Screen buttons released itself or cant be released.
- 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.
- White hell
- 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.
- /load 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.
- Full-width breakdown
- 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.
Textures
/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.
Example
This is the current setting of ForgottenCat, hope this will help you!
Remap Part
- Volume+:RCTRL
- Volume-:LALT
- Back:RETURN
- Button 1:A
- Button 2:SPACE
- Button 3:D
- Button 4:X
- Button 5:PAGEDOWN
- Button 6:WORLD_55
- Zoom in:WORLD_5
- Zoom out:ESCAPE
- Rotate left:K
- Rotate right:F1
Binding Part
ctrlon.cfg
emote 12
bind a "zoom+"
bind d "zoom-"
bind space "say /team 1;toggle cl_dummy 0 1;say /team 1"
bind pagedown "toggle cl_dummy_copy_moves 0 1"
bind x "exec deepfly.cfg"
bind rctrl "exec ctrloff.cfg"
bind world_5 "toggle cl_mouse_max_distance 400 2;toggle inp_mousesens 200 1"
bind return "say /spec"
ctrloff.cfg
emote 2
bind a "+left"
bind d "+right"
bind x "toggle cl_dummy 0 1"
bind pagedown "+nextweapon"
bind space "+jump"
bind rctrl "exec ctrlon.cfg"
bind lalt "exec alton.cfg"
bind return "toggle cl_overlay_entities 100 0"
deepfly.cfg
bind world_55 "+fire;+toggle cl_dummy_hammer 1 0"
bind x "exec deepflyoff.cfg"
emote 1
deepflyoff.cfg
*bind world_55 "+fire"
*bind x "exec deepfly.cfg"
*emote 12
alton.cfg
emote 12
bind d "player_name DDNET;dummy_name DDRACE"
bind x "toggle cl_dummy_resetonswitch 0 1"
bind space "say /dnd;toggle cl_dummy 0 1;say /dnd"
bind lalt "exec ctrloff.cfg"
bind rctrl "+showhookcoll"
bind return "Help yourself this is empty"
bind a "exec fastron.cfg"
bind pagedown "Help yourself this is empty"
fastron.cfg
exec ctrloff.cfg
emote 5
bind return "say /r"
Ending
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, we 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!