From f8ee310b698e319d3f3103a372c657878016516e Mon Sep 17 00:00:00 2001
From: Randall Fulton <randall.ml.fulton@gmail.com>
Date: Mon, 24 Jun 2019 16:33:21 -0500
Subject: [PATCH] Call out scaling in Spatial.translate docstring

This fixes issue #26938.

(cherry picked from commit bdf51e8e49c102d17d311ad765449e5171d178da)
---
 doc/classes/Spatial.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/doc/classes/Spatial.xml b/doc/classes/Spatial.xml
index b03bc4aea4f..89a715ffb06 100644
--- a/doc/classes/Spatial.xml
+++ b/doc/classes/Spatial.xml
@@ -274,6 +274,7 @@
 			</argument>
 			<description>
 				Changes the node's position by given offset [Vector3].
+				Note that the translation [code]offset[/code] is affected by the node's scale, so if scaled by e.g. [code](10, 1, 1)[/code], a translation by an offset of [code](2, 0, 0)[/code] would actually add 20 ([code]2 * 10[/code]) to the X coordinate.
 			</description>
 		</method>
 		<method name="translate_object_local">