View source for DDNet Mobile Tutorial/zh

<languages/>
这是DDNet的'''手机版'''教程。请注意由于当前版本客户端非常老旧，存在许多漏洞和问题，新版本正在开发中。 

在阅读此教程前，玩家需要先了解基础的按键绑定知识，并弄清楚自己需要的功能。要寻求手机版的帮助，请在wiki、b站、Discord等地方咨询ForgottenCat。因为大部分人对手机版了解不深，请勿过多叨扰。

教程中的设置仅供参考，请根据您的个人习惯适当修改。

<span id="Download"></span>
== 如何下载 ==

最新的手机版为9.3.1，仅支持安卓设备。点击[https://ddnet.org/downloads/DDNet-9.3.1.apk 此处]下载。
有些设备无法正常安装，例如安卓版本不匹配。也许您可以尝试使用Android Debug Bridge来安装。

<span id="Getting_to_Start"></span>
== 入门指南 ==

初次启动游戏，您会看到“按下左摇杆跳跃（Tap left joystick to jump）”。此时重启游戏，将会出现一行字“更改设备配置（CHANGE DEVICE CONFIGURATION）”。请点击它来进入设置界面。

[[File:MBmainpagenew.jpeg|thumb|upright=|主界面]]

此界面的所有更改会'''自动保存'''。

<span id="Buttons_and_Remap"></span>
== 按钮和重映射 ==

手机版带有重映射这一特殊的选项。因为电脑版通常使用键盘操作，按键本身已经命名，例如ctrl、alt等，可以直接绑定不同名字按键的功能。而手机版与之不同，在绑定按键的功能之前，必须先对按钮进行命名。

以下三个选项与重映射有关：“屏幕键盘（On-screen keyboard）”、“物理按键重映射（Remap physical keys）”、“屏幕双指操作（Two-finger screen gestures）”。

<span id="On-screen_keyboard"></span>
=== 屏幕键盘 On-screen keyboard ===

::该选项用于更改屏幕上的按键设置。

[[File:MBonscreen.jpeg|upright=|thumb|right|屏幕按键设置界面]]

:; 屏幕按键主题 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（Joystick1）”，否则移动和跳跃会相互冲突。禁用方式请点进选项并参考图片。

[[File:MBexample1.jpeg|upright=|thumb|right|禁用 ''Joystick1''的勾选情况]]

::{{key press|Joystick 2}}是'''唯一可以'''出钩的按钮，请勿禁用。轻触''ok''来保存设置并进入重映射界面，如图所示。

[[File:MBexample2.jpeg|upright=|thumb|right|重映射界面]]

::被映射的按钮在'''表现上'''与键盘按键一致。例如：如果你将{{key press|button 1}}映射为{{key press|A}}，那么按下{{key press|button 1}}将与连接键盘并按下{{key press|A}}的功能完全相同。

::顶部会显示当前被映射的按钮名。按钮名字。按钮通常有默认的映射。推荐将按钮映射到{{key press|A}}、{{key press|D}}、{{key press|space}}、{{key press|X}}、{{key press|pagedown}}/{{key press|PgDn}}，因为这些按键已经默认绑定了和电脑端一致的功能，而无须重新绑定。

<div lang="en" dir="ltr" class="mw-content-ltr">
::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".
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
::Default: ''A''=Move left, ''D''=Move right, ''Space''=Jump, ''X''=Switch dummy, ''Pagedown''=Nextweapon, ''Mouse1''=Fire. Mouse1 is mouse left button.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
::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.
</div>

<span id="Remap_physical_keys"></span>
=== 物理按键重映射 Remap physical keys ===

<div lang="en" dir="ltr" class="mw-content-ltr">
::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>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
::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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
::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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
::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.
</div>

<span id="Remap_Two-finger_screen_gestures"></span>
=== 屏幕双指操作重映射 Remap Two-finger screen gestures ===

<div lang="en" dir="ltr" class="mw-content-ltr">
::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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
::Normally we choose the ''Medium'' sensitivity. You can try yourself to see which option suits you best.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
::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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
::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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
::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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== 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
</div>
[[File:MBlayout.jpeg|thumb|upright=|<span lang="en" dir="ltr" class="mw-content-ltr">the layout</span>]]
<div lang="en" dir="ltr" class="mw-content-ltr">
, 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">
=== Remap Example ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
::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 "...".
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Settings and Binding In-Game ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Basic Settings ===
</div>

[[File:MBlobby.jpeg|upright=|thumb|right|<span lang="en" dir="ltr" class="mw-content-ltr">Homepage</span>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
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">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Remember, all changes made after entering ddnet could only be saved by exiting using the ''' '''''X''''' ''' at the top right corner.'''
</div>

[[File:MBbindinterface.jpeg|upright=|thumb|right|<span lang="en" dir="ltr" class="mw-content-ltr">Controls, you can bind there</span>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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">
Now, get into a random DDNet server, and start binding.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Basic Bindings ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Press the button that is mapped to ''F1'', then you can use the ''Text input button'' to input commands.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Mode Switch Key ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
*bind a "zoom+"
*bind d "zoom-"
*bind rctrl "exec off.cfg"
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Then, create another config file called "off.cfg". The following commands are what's inside.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
*bind a "+left"
*bind d "+right"
*bind rctrl "exec on.cfg"
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Then, go into game, tap f1, input "exec off.cfg", the key is now usable. Let's see what the key can do.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Two mode switch key is enough for now, just two volume keys. Too many mode switch keys will make you confused.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Bugs and Solutions ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
;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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Textures ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''/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">
== Example ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is the current setting of ForgottenCat, hope this will help you!
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Remap Part ===
</div>

[[File:MBbuttonlayout.jpeg|upright=|thumb|right|<span lang="en" dir="ltr" class="mw-content-ltr">The on-screen button layout</span>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
*Volume+:RCTRL
*Volume-:LALT
*Back:RETURN
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
*Button 1:A
*Button 2:SPACE
*Button 3:D
*Button 4:X
*Button 5:PAGEDOWN
*Button 6:WORLD_55
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
*Zoom in:WORLD_5
*Zoom out:ESCAPE
*Rotate left:K
*Rotate right:F1
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Binding Part ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''ctrlon.cfg'''
<syntaxhighlight lang="text" line>
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"
</syntaxhighlight>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''ctrloff.cfg'''
<syntaxhighlight lang="text" line>
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"
</syntaxhighlight>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''deepfly.cfg'''
<syntaxhighlight lang="text" line>
bind world_55 "+fire;+toggle cl_dummy_hammer 1 0"
bind x "exec deepflyoff.cfg"
emote 1
</syntaxhighlight>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''deepflyoff.cfg'''
<syntaxhighlight lang="text" line>
*bind world_55 "+fire"
*bind x "exec deepfly.cfg"
*emote 12
</syntaxhighlight>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''alton.cfg'''
<syntaxhighlight lang="text" line>
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"
</syntaxhighlight>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''fastron.cfg'''
<syntaxhighlight lang="text" line>
exec ctrloff.cfg
emote 5
bind return "say /r"
</syntaxhighlight>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Ending ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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!
</div>