Changes between Version 10 and Version 11 of Quagents AINodes


Ignore:
Timestamp:
Jun 3, 2011 11:35:40 AM (13 years ago)
Author:
jpawlick
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Quagents AINodes

    v10 v11  
    1313
    1414'''Parameters:'''
    15  * val1: unused
     15 * val1: obstacle flag: 1 if the agent should hop over low obstacles, 0 if it should report blocked when it encounters them.
    1616 * valf1: theta, the heading in which the agent should walk relative to its current facing. 0 is straight ahead, 90 is strafe left, etc.
    17  * valf2: speed, 1.0 = normal maximum bot movement speed, 0 = stopped. 2.25 is as fast a rocket, 5 is as fast as a plasma ball. Increasing movement speed also increases how far the bot looks ahead to see if it should say it is blocked.
     17 * valf2: speed, 1.0 = normal maximum bot movement speed, 0 = stopped. In the current version, sending values greater than 1 will often lead to immediate "blocked" returns, and don't make the bot go faster.
    1818
    1919'''Reports:'''
    … …  
    2929
    3030'''Reports:'''
    31  * ''blocked'' if movement ended (or wouldn't begin) due to cliff/wall/slime/lava/blocking entity.
    32  * ''done'' if jump completes otherwise.
     31 * ''done'' when the quagent lands and is ready to jump again. Even if the quagent encountered an obstacle during flight, this is reported.
    3332
     33== AINode_GPop ==
     34This node immediately removes itself and the next command, if such a command exists. Intuitively, one might expect a pop node to report ''done'' after the popped command reports ''popped'', but this is incompatible with the assertion that commands report in order with respect to the command queue. It is still safe to assume that any order sent over the socket will be manipulating the queue after the popped command is gone - once pop has begun its execution the socket is not read until after it has completed.
    3435
     36'''Parameters:'''
     37 * none used.
     38
     39'''Reports:'''
     40 * ''done'' when the pop begins (removes itself from the stack).
     41 * causes the next command to report ''popped''
     42
     43== AINode_GPause ==
     44This node does nothing forever.
     45
     46'''Parameters:'''
     47 * none used.
     48
     49'''Reports:'''
     50 * never halts, though it may be popped/forgotten.
     51
     52== AINode_GForgetAllTasks ==
     53This node immediately removes itself, reporting 'done', then removes all tasks. Intuitively, 'done' would signal that all other tasks have been removed, but this is not compatible with the assertion that tasks report completion in the same order that they are removed from the queue. It is still safe for a user to do something immediately after a done - see pop.
     54
     55'''Parameters:'''
     56 * none used.
     57
     58'''Reports:'''
     59 * ''done'' immediately.
     60 * causes all other commands to report ''forgotten'', in the order that they would have normally been executed.