4rpl:commands:setuniternsimulated
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 4rpl:commands:setuniternsimulated [2022/05/17 15:23] – [Description] added link to GitHub isue Karsten75 | 4rpl:commands:setuniternsimulated [2025/02/14 14:57] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| ===== Description ===== | ===== Description ===== | ||
| - | State controls the ERN override. If state is 1, then the unit will act as if it has an ERN. If state is -1, then unit will act as if it does not have an ERN, even it is actually does. If state is 0, then there is no override to either ERN state. Note that the visual state of the unit is not affected by this call, only the effects of an ERN are altered. | + | ? State |
| + | : controls the ERN override. If state is | ||
| + | ? 1, | ||
| + | : then the unit will act as if it has an ERN. | ||
| + | ? -1, | ||
| + | : then unit will act as if it does not have an ERN, even it is actually does. | ||
| + | ? 0, | ||
| + | :: then there is no override to either ERN state. Note that the visual state of the unit is not affected by this call, only the effects of an ERN are altered. | ||
| :NOTE:\\ | :NOTE:\\ | ||
| - | Pylons are an exception to this. This API will not change the connection range of a Pylon although traditional ERNs will. It will be completely unaffected. | + | Pylons are an exception to this. This API will not change the connection range of a Pylon although traditional ERNs will. It will be completely unaffected. |
| ===== Examples ===== | ===== Examples ===== | ||
| <code 4rpl> | <code 4rpl> | ||
4rpl/commands/setuniternsimulated.1652801026.txt.gz · Last modified: 2025/02/14 14:56 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
