I do not understand why this configuration is not natively enabled in config.txt
It is unknown by most users (I created just now active in your wiki) and is the most efficient method among the three created (the homunculus to teleport near the master, the master teleport or the master back to fetch the homunculus).
homunculus_StandByAuto enabled natively?
Moderator: Moderators
Re: homunculus_StandByAuto enabled natively?
I totally agree, good notice!
Re: homunculus_StandByAuto enabled natively?
Leveraging the topic...
Anyone have any suggestions for a new name for the configuration, homunculus_StandByAuto? This current name is not descriptive and does not respect the conventions of development.
Anyone have any suggestions for a new name for the configuration, homunculus_StandByAuto? This current name is not descriptive and does not respect the conventions of development.
Re: homunculus_StandByAuto enabled natively?
I actually thought about these two: homunculus_returnAuto and homunculus_teleportIfLost
Re: homunculus_StandByAuto enabled natively?
@KeplerBR
problem of losing the homun control after a teleport type homunculus change unknown
problem of losing the homun control after a teleport type homunculus change unknown
-
- Developers
- Posts: 1798
- Joined: 05 Dec 2008, 05:42
- Noob?: Yes
Re: homunculus_StandByAuto enabled natively?
Maybe something like existing teleportAuto_lostHomunculus? homunculus_standByAuto_lost?
About implementation:
And all other code in this file uses $config{$slave->{configPrefix}.'option'}.
All other such calls set $slave->{standby_time}, why this is different?
About implementation:
Code: Select all
$config{homunculus_StandByAuto}
Code: Select all
$slave->sendStandBy;