User Tools

Site Tools


4rpl:commands:getunitcanbuild

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
4rpl:commands:getunitcanbuild [2021/01/08 16:01] – external edit 127.0.0.14rpl:commands:getunitcanbuild [2025/02/14 14:57] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ~~NOTOC~~ ~~NOTOC~~
 <=[[4rpl:start| Index]] <=[[4rpl:start| Index]]
 +
 +<WRAP tabs>
 +  * [[4rpl:commands:GetUnitCanBuild|Get]]
 +  * [[4rpl:commands:SetUnitCanBuild|Set]]
 +</WRAP>
  
 ====== GetUnitCanBuild ====== ====== GetUnitCanBuild ======
Line 6: Line 11:
  
 ===== Description ===== ===== Description =====
-Returns a boolean indicating if the specified unit can be built. This call controls the visibility of the build buttons in the left build pane.+Returns a boolean indicating if the specified unit can be built. This call controls the visibility of the build buttons in the left build pane. Unit type is a subset of  [[Unit Types]]  and must be represented on the build pane. 
 The unitType can be one of:\\ The unitType can be one of:\\
   * riftlab   * riftlab
Line 32: Line 38:
   * beacon   * beacon
  
 +Avoid using this call frequently. It is very CPU intensive and should only be declared at the most minimalistic applications. Never use this more than you need to for as infrequent as possible.
 ===== Examples ===== ===== Examples =====
 <code 4rpl> <code 4rpl>
4rpl/commands/getunitcanbuild.1610121708.txt.gz · Last modified: 2025/02/14 14:56 (external edit)