For information and discussion about Oolite.
https://bb.oolite.space/
YIKES! thanks for catching this!Eric Walch wrote:Not true as this tests if a "pirate" role is among the possible roles for that ship, that may be added as a trader at the moment. You probably need: (entity.primaryRole == "pirate")Dr.Tripsa wrote:it is only activated by the presence of a pirate (entity.hasRole("pirate")) within 1/5 Km.
25Km radius, in 1:1 mode.Dr.Tripsa wrote:(by contrast the scanner display is what .. 10Km radius? )
I suspected as much.. I was really just making a joke..Dr.Tripsa wrote:The reason for the test release is so people can give feedback on pricing/availability after playing with it a bit
Is this still true? This "method" is mentioned on 4 relevant wiki pages which seem to say nothing apart from this one: https://wiki.alioth.net/index.php/Oolit ... essMessageEric Walch wrote: ↑Mon Jan 21, 2013 8:19 pmThis UPDATE needs a pause to become:Without pause, it is broadcasted 4 times every second. That is a bit overuse of cpu time. Specially because identical messages are suppressed and not visible at all.Code: Select all
UPDATE = (broadcastDistressMessage, "pauseAI: 8");
One problem will be that the beacon needs a primary aggressor that is already targeting the beacon in attack mode. If not present, broadcastDistressMessage will do nothing.
EDIT: This behaviour is different that written in the wiki were it is suggested that you can set a primary target that will become the "aggressor". I looked it up, and the wiki was correct up to Oolite 1.74. In 1.76 there already needed to be an explicit primary aggressor. Probably to prevent buggy behaviour where a viper went after an unwanted primary target. (Going to edit the wiki now....)
