Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Rebel Engine API MIT 95% 454 30,464 216,474 101 120 0 0
Glossary Rebel Toolbox MIT 0 0 0 0 0 0 0

Overview

Project website rebeltoolbox.com
Project maintainers User avatar Rebel
Translation license MIT Rebel Engine API Rebel Toolbox
12 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 11,267 236,508 1,605,062
Translated 95% 10,813 87% 206,044 86% 1,388,588
Needs editing 3% 353 10% 24,453 10% 173,468
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 120 3% 8,033 3% 60,718
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 101 2% 6,011 2% 43,006
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 11,274 changes 0 changes 28 changes 0 changes 0 changes 0 changes 3 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

236 k
Hosted words
11,267
Hosted strings
95%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+95%
+100%
Contributors
—
User avatar None

Resource updated

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
The “translations/zh_CN.po” file was changed. 12 hours ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
The maximum distance a simplified contour's border edges should deviate from the original raw contour.
简化轮廓的边界边缘应偏离原始原始轮廓的最大距离。
12 hours ago
User avatar None

Resource updated

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
The “translations/zh_CN.po” file was changed. 3 weeks ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
[VideoStream] resource handling the [url=https://www.theora.org/]Ogg Theora[/url] video format with [code].ogv[/code] extension.
[b]Note:[/b] While Ogg Theora videos can also have an [code].ogg[/code] extension, you will have to rename the extension to [code].ogv[/code] to use those videos within Rebel Engine.
[VideoStream]资源处理[url=https://www.theora.org/]Ogg Theora[/url]视频格式，扩展名为[code].ogv[/code]。Theora编解码器比[VideoStreamWebm]的VP8和VP9效率低，但它以较少的CPU资源来解码。Theora编解码器是在CPU上解码。
[b]注意：[/b] 虽然Ogg Theora视频也可以有[code].ogg[/code]扩展名，但必须将扩展名改为[code].ogv[/code]，以便在Godot内使用。
3 weeks ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
Control node for playing video streams using [VideoStream] resources.
Supported video formats are [url=https://www.theora.org/]Ogg Theora[/url] ([code].ogv[/code], [VideoStreamTheora]), and any format exposed via a GDNative plugin using [VideoStreamGDNative].
[b]Note:[/b] Due to a bug, VideoPlayer does not support localization remapping yet.
[b]Warning:[/b] On HTML5, video playback [i]will[/i] perform poorly due to missing architecture-specific assembly optimizations, especially for VP8/VP9.
用于播放使用[VideoStream]资源视频流的控件节点。
支持的视频格式有 [url=https://www.webmproject.org/]WebM[/url] ([code].webm[/code], [VideoStreamWebm]), [url=https://www.theora.org/]Ogg Theora[/url] ([code].ogv[/code], [VideoStreamTheora] ) 以及任何通过GDNative插件使用[VideoStreamGDNative]公开的格式。
[b]注意：[/b] 由于一个错误，VideoPlayer还不支持本地化重映射。
[b]警告：[/b] 在HTML5上，视频播放[i]将[/i]表现不佳，因为缺少特定架构的汇编优化，特别是对于VP8/VP9。
3 weeks ago
User avatar None

Resource updated

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
The “translations/zh_CN.po” file was changed. 3 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
WebXR is an open standard that allows creating VR and AR applications that run in the web browser.
As such, this interface is only available when running in an HTML5 export.
WebXR supports a wide range of devices, from the very capable (like Valve Index, HTC Vive, Oculus Rift and Quest) down to the much less capable (like Google Cardboard, Oculus Go, GearVR, or plain smartphones).
Since WebXR is based on Javascript, it makes extensive use of callbacks, which means that [WebXRInterface] is forced to use signals, where other AR/VR interfaces would instead use functions that return a result immediately. This makes [WebXRInterface] quite a bit more complicated to initialize than other AR/VR interfaces.
Here's the minimum code required to start an immersive VR session:
[codeblock]
extends Spatial

var webxr_interface
var vr_supported = false

func _ready():
# We assume this node has a button as a child.
# This button is for the user to consent to entering immersive VR mode.
$Button.connect("pressed", self, "_on_Button_pressed")

webxr_interface = ARVRServer.find_interface("WebXR")
if webxr_interface:
# WebXR uses a lot of asynchronous callbacks, so we connect to various
# signals in order to receive them.
webxr_interface.connect("session_supported", self, "_webxr_session_supported")
webxr_interface.connect("session_started", self, "_webxr_session_started")
webxr_interface.connect("session_ended", self, "_webxr_session_ended")
webxr_interface.connect("session_failed", self, "_webxr_session_failed")

# This returns immediately - our _webxr_session_supported() method
# (which we connected to the "session_supported" signal above) will
# be called sometime later to let us know if it's supported or not.
webxr_interface.is_session_supported("immersive-vr")

func _webxr_session_supported(session_mode, supported):
if session_mode == 'immersive-vr':
vr_supported = supported

func _on_Button_pressed():
if not vr_supported:
OS.alert("Your browser doesn't support VR")
return

# We want an immersive VR session, as opposed to AR ('immersive-ar') or a
# simple 3DoF viewer ('viewer').
webxr_interface.session_mode = 'immersive-vr'
# 'bounded-floor' is room scale, 'local-floor' is a standing or sitting
# experience (it puts you 1.6m above the ground if you have 3DoF headset),
# whereas as 'local' puts you down at the ARVROrigin.
# This list means it'll first try to request 'bounded-floor', then
# fallback on 'local-floor' and ultimately 'local', if nothing else is
# supported.
webxr_interface.requested_reference_space_types = 'bounded-floor, local-floor, local'
# In order to use 'local-floor' or 'bounded-floor' we must also
# mark the features as required or optional.
webxr_interface.required_features = 'local-floor'
webxr_interface.optional_features = 'bounded-floor'

# This will return false if we're unable to even request the session,
# however, it can still fail asynchronously later in the process, so we
# only know if it's really succeeded or failed when our
# _webxr_session_started() or _webxr_session_failed() methods are called.
if not webxr_interface.initialize():
OS.alert("Failed to initialize")
return

func _webxr_session_started():
$Button.visible = false
# This tells Rebel Engine to start rendering to the headset.
get_viewport().arvr = true
# This will be the reference space type you ultimately got, out of the
# types that you requested above. This is useful if you want the game to
# work a little differently in 'bounded-floor' versus 'local-floor'.
print ("Reference space type: " + webxr_interface.reference_space_type)

func _webxr_session_ended():
$Button.visible = true
# If the user exits immersive mode, then we tell Rebel Engine to render to the web
# page again.
get_viewport().arvr = false

func _webxr_session_failed(message):
OS.alert("Failed to initialize: " + message)
[/codeblock]
There are several ways to handle "controller" input:
- Using [ARVRController] nodes and their [signal ARVRController.button_pressed] and [signal ARVRController.button_release] signals. This is how controllers are typically handled in AR/VR apps in Rebel Engine, however, this will only work with advanced VR controllers like the Oculus Touch or Index controllers, for example. The buttons codes are defined by [url=https://immersive-web.github.io/webxr-gamepads-module/#xr-standard-gamepad-mapping]Section 3.3 of the WebXR Gamepads Module[/url].
- Using [method Node._unhandled_input] and [InputEventJoypadButton] or [InputEventJoypadMotion]. This works the same as normal joypads, except the [member InputEvent.device] starts at 100, so the left controller is 100 and the right controller is 101, and the button codes are also defined by [url=https://immersive-web.github.io/webxr-gamepads-module/#xr-standard-gamepad-mapping]Section 3.3 of the WebXR Gamepads Module[/url].
- Using the [signal select], [signal squeeze] and related signals. This method will work for both advanced VR controllers, and non-traditional "controllers" like a tap on the screen, a spoken voice command or a button press on the device itself. The [code]controller_id[/code] passed to these signals is the same id as used in [member ARVRController.controller_id].
You can use one or all of these methods to allow your game or app to support a wider or narrower set of devices and input methods, or to allow more advanced interactions with more advanced devices.
WebXR是一个开放标准，允许创建在网络浏览器中运行的VR和AR应用程序。
因此，这个界面只有在HTML5导出中运行时才能使用。
WebXR支持广泛的设备，从能力很强的设备（如Valve Index、HTC Vive、Oculus Rift和Quest）到能力较弱的设备（如Google Cardboard、Oculus Go、GearVR或普通智能手机）。
由于WebXR是基于Javascript的，它大量使用回调，这意味着[WebXRInterface]被迫使用信号，而其他AR/VR界面会使用立即返回结果的函数。这使得[WebXRInterface]的初始化比其他AR/VR接口要复杂很多。
下面是启动一个沉浸式VR会话所需的最小代码。
[codeblock]
extends Spatial

var webxr_interface
var vr_supported = false

func _ready():
# 我们假设这个节点有一个按钮作为子节点。
# 这个按钮是让用户同意进入沉浸式VR模式。
$Button.connect("pressed", self, "_on_Button_pressed")

webxr_interface = ARVRServer.find_interface("WebXR")
if webxr_interface:
# WebXR使用了大量的异步回调，
# 所以我们要连接各种信号来接收它们。
webxr_interface.connect("session_supported", self, "_webxr_session_supported")
webxr_interface.connect("session_started", self, "_webxr_session_started")
webxr_interface.connect("session_ended", self, "_webxr_session_ended")
webxr_interface.connect("session_failed", self, "_webxr_session_failed")

# 这将立即返回——自身的_webxr_session_supported()方法
# (我们在上面连接了'session_supported' 信号)将在稍后被调用
# 让我们知道它是否被支持。
webxr_interface.is_session_supported("immersive-vr")

func _webxr_session_supported(session_mode, supported):
if session_mode == 'immersive-vr':
vr_supported = supported

func _on_Button_pressed():
if not vr_supported:
OS.alert("Your browser doesn't support VR")
return

# 获得沉浸式的VR体验，而不是AR（'immersive-ar'）
# 或一个简单的3DoF查看器（'viewer'）。
webxr_interface.session_mode = 'immersive-vr'
# 'bounded-floor'是房间大小，'local-floor'是站着或坐着的
# 体验（如果你有3DoF耳机，它会让你离地面1.6米）。
# 而'local'则是让你在ARVROrigin处。
# 这个列表意味着它将首先尝试请求 "bounded-floor"，
# 如果没有其他支持的话，就退而求其次，选择 "local-floor"，
# 如果没有别的就选 "local" 支持。
webxr_interface.requested_reference_space_types = 'bounded-floor, local-floor, local'
# 为了使用'local-floor'或'bounded-floor'，
# 我们须标记这些特征。
webxr_interface.required_features = 'local-floor'
webxr_interface.optional_features = 'bounded-floor'

# 如果无法请求会话，这将返回false。
# 然而，在这个过程中，它仍然可能异步失败
# 只有在
# _webxr_session_started()或_webxr_session_failed()方法被调用时，才知道它是否真的成功或失败。
if not webxr_interface.initialize():
OS.alert("Failed to initialize")
return

func _webxr_session_started():
$Button.visible = false
# 这告诉Godot开始进行渲染。
get_viewport().arvr = true
# 这将是您从上面请求的类型中最终得到的引用空间类型。
# 如果你想让游戏在'bounded-floor'和 'local-floor' 中有一点不同，
# 这是很有用的。
print ("Reference space type: " + webxr_interface.reference_space_type)

func _webxr_session_ended():
$Button.visible = true
# 如果用户退出沉浸模式，
# 我们就会告诉Godot重新渲染到网页上。
get_viewport().arvr = false

func _webxr_session_failed(message):
OS.alert("Failed to initialize: " + message)
[/codeblock]
有几种方法来处理 "controller" 控制器的输入。
- 使用[ARVRController]节点和它们的[signal ARVRController.button_pressed]和[signal ARVRController.button_release]信号。这是Godot的AR/VR应用中通常处理控制器的方式，然而，这只适用于高级VR控制器，例如Oculus Touch或Index控制器。按钮代码由[url=https://immersive-web.github.io/webxr-gamepads-module/#xr-standard-gamepad-mapping]WebXR Gamepads模块[/url]的3.3节定义。
- 使用[method Node._unhandled_input]和[InputEventJoypadButton]或[InputEventJoypadMotion]。这和普通的游戏手柄工作原理一样，只是[member InputEvent.device]从100开始，所以左边的控制器是100，右边的控制器是101，按钮代码由[url=https://immersive-web.github.io/webxr-gamepads-module/#xr-standard-gamepad-mapping]WebXR Gamepads模块[/url]的3.3节定义。
- 使用[signal select]、[signal squeeze]和相关信号。这种方法既适用于高级的VR控制器，也适用于非传统的 "controller" 控制器，如在屏幕上的点击、口语化的语音命令或设备本身的按键。传递给这些信号的[code]controller_id[/code]是与[member ARVRController.controller_id]中使用的id相同。
你可以使用这些方法中的一个或全部，让你的游戏或应用程序支持更广泛或更窄的设备和输入方法，或者允许与更高级的设备进行更高级的交互。
3 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
Returns the angle between the line connecting the two points and the X axis, in radians.
[img caption="Illustration of the returned angle"]/img/vector2_angle_to_point.png[/img]
返回连接两点的直线与X轴的夹角，单位为弧度。
[url=https://raw.githubusercontent.com/godotengine/godot-docs/master/img/vector2_angle_to_point.png]返回角度的图示。[/url]
3 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
Returns this vector's angle with respect to the positive X axis, or [code](1, 0)[/code] vector, in radians.
For example, [code]Vector2.RIGHT.angle()[/code] will return zero, [code]Vector2.DOWN.angle()[/code] will return [code]PI / 2[/code] (a quarter turn, or 90 degrees), and [code]Vector2(1, -1).angle()[/code] will return [code]-PI / 4[/code] (a negative eighth turn, or -45 degrees).
[img caption="Illustration of the returned angle"]/img/vector2_angle.png[/img]
Equivalent to the result of [method @GDScript.atan2] when called with the vector's [member y] and [member x] as parameters: [code]atan2(y, x)[/code].
返回这个向量相对于正X轴的角度，或[code](1, 0)[/code]向量，单位为弧度。
例如，[code]Vector2.RIGHT.angle()[/code]将返回0，[code]Vector2.DOWN.angle()[/code]将返回[code]PI / 2[/code]（四分之一转，或90度），[code]Vector2(1, -1).angle()[/code]将返回[code]-PI / 4[/code] （负八分之一转，或-45度）。
[url=https://raw.githubusercontent.com/godotengine/godot-docs/master/img/vector2_angle.png]返回角度的说明。[/url]
相当于以向量的[member y] 和 [member x]为参数调用[method @GDScript.atan2]时的结果。[code]atan2(y, x)[/code]。
3 months ago
User avatar None

String added in the repository

  1. Rebel Toolbox
  2. Rebel Engine API
  3. Chinese (Simplified)
Tweens are useful for animations requiring a numerical property to be interpolated over a range of values. The name [i]tween[/i] comes from [i]in-betweening[/i], an animation technique where you specify [i]keyframes[/i] and the computer interpolates the frames that appear between them.
[Tween] is more suited than [AnimationPlayer] for animations where you don't know the final values in advance. For example, interpolating a dynamically-chosen camera zoom value is best done with a [Tween] node; it would be difficult to do the same thing with an [AnimationPlayer] node.
Here is a brief usage example that makes a 2D node move smoothly between two positions:
[codeblock]
var tween = get_node("Tween")
tween.interpolate_property($Node2D, "position",
Vector2(0, 0), Vector2(100, 100), 1,
Tween.TRANS_LINEAR, Tween.EASE_IN_OUT)
tween.start()
[/codeblock]
Many methods require a property name, such as [code]"position"[/code] above. You can find the correct property name by hovering over the property in the Inspector. You can also provide the components of a property directly by using [code]"property:component"[/code] (e.g. [code]position:x[/code]), where it would only apply to that particular component.
Many of the methods accept [code]trans_type[/code] and [code]ease_type[/code]. The first accepts an [enum TransitionType] constant, and refers to the way the timing of the animation is handled (see [url=https://easings.net/]easings.net[/url] for some examples). The second accepts an [enum EaseType] constant, and controls where the [code]trans_type[/code] is applied to the interpolation (in the beginning, the end, or both). If you don't know which transition and easing to pick, you can try different [enum TransitionType] constants with [constant EASE_IN_OUT], and use the one that looks best.
[img caption="Tween easing and transition types cheatsheet"]/img/tween_cheatsheet.png[/img]
[b]Note:[/b] Tween methods will return [code]false[/code] if the requested operation cannot be completed.
需要让数值属性在一定范围内做插值的动画可以使用 Tween。[i]Tween[/i] 这个名字来自动画技术 [i]in-betweening[/i]（补间动画）：你指定[i]关键帧[/i]，而计算机则在关键帧之间插补出其他帧。
[Tween] 比 [AnimationPlayer] 更适合于事先不知道最终数值的动画。例如，插值动态选择的相机变焦值最好用 [Tween] 节点完成；用 [AnimationPlayer] 节点做同样的事情会很困难。
下面是一个简短的使用例子，让一个 2D 节点在两个位置之间平滑移动：
[codeblock]
var tween = get_node("Tween")
tween.interpolate_property($Node2D, "position",
Vector2(0, 0), Vector2(100, 100), 1,
Tween.TRANS_LINEAR, Tween.EASE_IN_OUT)
tween.start()
[/codeblock]
许多方法都需要提供属性名称，比如上面的 [code]"position"[/code]。你可以通过在检查器中将鼠标悬停在该属性上找到正确的属性名称。你也可以通过使用 [code]"property:component"[/code] 直接提供一个属性的分量（例如 [code]position:x[/code]），动画就只会对这个分量起效。
许多方法接受过渡类型 [code]trans_type[/code] 和缓动类型 [code]easy_type[/code]。前者接受 [enum TransitionType] 常量，指的是处理动画时间的方式（请参阅 [url=https://easings.net/]easings.net[/url] 的一些例子）。后者接受 [enum EaseType] 常量，控制 [code]trans_type[/code] 应用于插值的位置（开头、结尾、或两处都是）。如果你不知道该选哪个过渡和缓动，你可以用 [constant EASE_IN_OUT] 尝试不同的 [enum TransitionType] 常数，然后使用看起来最好的那个。
[url=https://raw.githubusercontent.com/godotengine/godot-docs/master/img/tween_cheatsheet.png]Tween 缓动与过渡类型速查表[/url]
3 months ago
Browse all changes for this language