mirror of
https://github.com/godotengine/godot-docs-l10n.git
synced 2025-12-31 09:49:22 +03:00
237 lines
11 KiB
Plaintext
237 lines
11 KiB
Plaintext
# SOME DESCRIPTIVE TITLE.
|
|
# Copyright (C) 2014-present Juan Linietsky, Ariel Manzur and the Godot community (CC BY 3.0)
|
|
# This file is distributed under the same license as the Godot Engine package.
|
|
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
|
|
#
|
|
#, fuzzy
|
|
msgid ""
|
|
msgstr ""
|
|
"Project-Id-Version: Godot Engine latest\n"
|
|
"Report-Msgid-Bugs-To: \n"
|
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
|
"Language-Team: LANGUAGE <LL@li.org>\n"
|
|
"MIME-Version: 1.0\n"
|
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|
"Content-Transfer-Encoding: 8bit\n"
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:4
|
|
msgid "Designing the mob scene"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:6
|
|
msgid "In this part, you're going to code the monsters, which we'll call mobs. In the next lesson, we'll spawn them randomly around the playable area."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:9
|
|
msgid "Let's design the monsters themselves in a new scene. The node structure is going to be similar to the ``player.tscn`` scene."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:12
|
|
msgid "Create a scene with, once again, a :ref:`CharacterBody3D <class_CharacterBody3D>` node as its root. Name it ``Mob``. Add a child node :ref:`Node3D <class_Node3D>`, name it ``Pivot``. And drag and drop the file ``mob.glb`` from the *FileSystem* dock onto the ``Pivot`` to add the monster's 3D model to the scene."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:19
|
|
msgid "You can rename the newly created ``mob`` node into ``Character``."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:22
|
|
msgid "|image0|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:334
|
|
msgid "image0"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:24
|
|
msgid "We need a collision shape for our body to work. Right-click on the ``Mob`` node, the scene's root, and click *Add Child Node*."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:27
|
|
msgid "|image1|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:335
|
|
msgid "image1"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:29
|
|
msgid "Add a :ref:`CollisionShape3D <class_CollisionShape3D>`."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:31
|
|
msgid "|image2|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:336
|
|
msgid "image2"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:34
|
|
msgid "In the *Inspector*, assign a *BoxShape3D* to the *Shape* property."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:38
|
|
msgid "We should change its size to fit the 3D model better. You can do so interactively by clicking and dragging on the orange dots."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:41
|
|
msgid "The box should touch the floor and be a little thinner than the model. Physics engines work in such a way that if the player's sphere touches even the box's corner, a collision will occur. If the box is a little too big compared to the 3D model, you may die at a distance from the monster, and the game will feel unfair to the players."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:47
|
|
msgid "|image4|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:337
|
|
msgid "image4"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:49
|
|
msgid "Notice that my box is taller than the monster. It is okay in this game because we're looking at the scene from above and using a fixed perspective. Collision shapes don't have to match the model exactly. It's the way the game feels when you test it that should dictate their form and size."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:55
|
|
msgid "Removing monsters off-screen"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:57
|
|
msgid "We're going to spawn monsters at regular time intervals in the game level. If we're not careful, their count could increase to infinity, and we don't want that. Each mob instance has both a memory and a processing cost, and we don't want to pay for it when the mob is outside the screen."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:62
|
|
msgid "Once a monster leaves the screen, we don't need it anymore, so we should delete it. Godot has a node that detects when objects leave the screen, :ref:`VisibleOnScreenNotifier3D <class_VisibleOnScreenNotifier3D>`, and we're going to use it to destroy our mobs."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:68
|
|
msgid "When you keep instancing an object, there's a technique you can use to avoid the cost of creating and destroying instances all the time called pooling. It consists of pre-creating an array of objects and reusing them over and over."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:73
|
|
msgid "When working with GDScript, you don't need to worry about this. The main reason to use pools is to avoid freezes with garbage-collected languages like C# or Lua. GDScript uses a different technique to manage memory, reference counting, which doesn't have that caveat. You can learn more about that here: :ref:`doc_gdscript_basics_memory_management`."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:79
|
|
msgid "Select the ``Mob`` node and add a child node :ref:`VisibleOnScreenNotifier3D <class_VisibleOnScreenNotifier3D>`. Another box, pink this time, appears. When this box completely leaves the screen, the node will emit a signal."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:83
|
|
msgid "|image5|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:338
|
|
msgid "image5"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:85
|
|
msgid "Resize it using the orange dots until it covers the entire 3D model."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:87
|
|
msgid "|image6|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:339
|
|
msgid "image6"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:90
|
|
msgid "Coding the mob's movement"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:92
|
|
msgid "Let's implement the monster's motion. We're going to do this in two steps. First, we'll write a script on the ``Mob`` that defines a function to initialize the monster. We'll then code the randomized spawn mechanism in the ``main.tscn`` scene and call the function from there."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:97
|
|
msgid "Attach a script to the ``Mob``."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:99
|
|
msgid "|image7|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:340
|
|
msgid "image7"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:101
|
|
msgid "Here's the movement code to start with. We define two properties, ``min_speed`` and ``max_speed``, to define a random speed range, which we will later use to define ``CharacterBody3D.velocity``."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:139
|
|
msgid "Similarly to the player, we move the mob every frame by calling the function ``CharacterBody3D.move_and_slide()``. This time, we don't update the ``velocity`` every frame; we want the monster to move at a constant speed and leave the screen, even if it were to hit an obstacle."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:144
|
|
msgid "We need to define another function to calculate the ``CharacterBody3D.velocity``. This function will turn the monster towards the player and randomize both its angle of motion and its velocity."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:148
|
|
msgid "The function will take a ``start_position``,the mob's spawn position, and the ``player_position`` as its arguments."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:151
|
|
msgid "We position the mob at ``start_position`` and turn it towards the player using the ``look_at_from_position()`` method, and randomize the angle by rotating a random amount around the Y axis. Below, ``randf_range()`` outputs a random value between ``-PI / 4`` radians and ``PI / 4`` radians."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:181
|
|
msgid "We got a random position, now we need a ``random_speed``. ``randi_range()`` will be useful as it gives random int values, and we will use ``min_speed`` and ``max_speed``. ``random_speed`` is just an integer, and we just use it to multiply our ``CharacterBody3D.velocity``. After ``random_speed`` is applied, we rotate ``CharacterBody3D.velocity`` Vector3 towards the player."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:214
|
|
msgid "Leaving the screen"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:216
|
|
msgid "We still have to destroy the mobs when they leave the screen. To do so, we'll connect our :ref:`VisibleOnScreenNotifier3D <class_VisibleOnScreenNotifier3D>` node's ``screen_exited`` signal to the ``Mob``."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:219
|
|
msgid "Head back to the 3D viewport by clicking on the *3D* label at the top of the editor. You can also press :kbd:`Ctrl + F2` (:kbd:`Opt + 2` on macOS)."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:222
|
|
msgid "|image8|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:341
|
|
msgid "image8"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:224
|
|
msgid "Select the :ref:`VisibleOnScreenNotifier3D <class_VisibleOnScreenNotifier3D>` node and on the right side of the interface, navigate to the *Node* dock. Double-click the ``screen_exited()`` signal."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:227
|
|
msgid "|image9|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:342
|
|
msgid "image9"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:229
|
|
msgid "Connect the signal to the ``Mob``"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:231
|
|
msgid "|image10|"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:343
|
|
msgid "image10"
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:233
|
|
msgid "This will add a new function for you in your mob script, ``_on_visible_on_screen_notifier_3d_screen_exited()``. From it, call the ``queue_free()`` method. This function destroys the instance it's called on."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:252
|
|
msgid "Our monster is ready to enter the game! In the next part, you will spawn monsters in the game level."
|
|
msgstr ""
|
|
|
|
#: ../../docs/getting_started/first_3d_game/04.mob_scene.rst:255
|
|
msgid "Here is the complete ``mob.gd`` script for reference."
|
|
msgstr ""
|