Skip to content

Commit 6eb7398

Browse files
[wiki] Transfer gems transferrer / transferee object type clarification
1 parent 34cc496 commit 6eb7398

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

wiki/reference/actions/core_action_transferGems.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,10 @@ If the position points to an object that can hold gems (Cores / Units / Gem Pile
1616

1717
Only units are able to drop gems on the floor.
1818

19-
- Units can only transfer gems if their action cooldown is 0, for more see [Cooldowns](documentation/cooldowns).
20-
- Units can only transfer gems one tile up, down, left or right; for more see [Action Position Limits](documentation/action_position_limits). The only exception to this is outlined in the tip box below.
19+
- Objects can only transfer gems if their action cooldown is 0, for more see [Cooldowns](documentation/cooldowns).
20+
- Objects can only transfer gems one tile up, down, left or right; for more see [Action Position Limits](documentation/action_position_limits). The only exception to this is outlined in the tip box below.
21+
22+
The transferring object must be a Core or Unit of your team, and the target object must be a Core or Unit of any team, a Gem Pile, or an empty grid position.
2123

2224
> [!TIP]
2325
> Unlike other action parameters, the server won't stop executing the transfer gems action if the gems amount parameter is set higher than the possible amount. That means you can pass `99999`, even if the source object is only holding `42` gems, to transfer the maximum possible amount of gems anyways.

0 commit comments

Comments
 (0)