Node Connections

[Tiger]

Hey guys,

I have one final question. I set the node connection commands in the AI script file, but for some reason they do not seem to be working. One of the files I am having trouble with is attached with the corresponding map. Any takes on why it isn't working?

[Tiger]

Here is the second file. Thanks in advance.

[TomTom]

Since I don't do RTCW I only looked at the aiscript.
Verify that all the action tests are for those types that support the aiscript (like dynamite etc, Not camp, roam etc.)
Your aiscript looks like there are dynamite actions acting on the same ent_num. If that is the case they should be linked, and then only one of the associated action tests for the group is needed.
Verify that the actions in the nav have the correct ent_nums (if they are wrong but don't crash your machine, they definitely won't trigger their action test).

And JIC, a warning. I noted nodes 83 and 261 are totally dis-connected in the aiscript. You should only totally dis-connect a node if (a) there is no way a bot can find itself next to that node say after fighting and (b) the node is not a closenode for an action. If (a) is not the case you can leave just a single connection leaving the node so the bot won't be trapped,

[the bindlestiff]

Hey Tige,

The node_connect statements for actions 25/26/27 work perfectly.

The node_disconnect statements for actions 4/5/6/7 work perfectly. Since the connections from node 83 to the other nodes are ONE-WAY, you shouldn't use "true" as the connection modifier (which signifies a two-way connection). Use "false" instead to indicate a one-way connection. This error didn't cause a problem because you were disconnecting nodes, but to be correct, use "false" for one-way connections.

The node_connect statements for actions 4/5/6/7 that attempt to connect node 261 to nodes 126/192/63 FAIL because there are already four connections from those nodes to other nodes (limit is four). If you check the console after you blow the dynamite at the crypt, you'll see several error messages in RED that tell you "this node has the max number of links already." This is the clue that you have too many node connections for that node and that your node_connect went over the limit and therefore didn't happen. To make this work, you'll have to delete an existing connection from the problem nodes or make the new links from node 261 one-way only (as they were for node 83)

Since dynamite actions 25/26 are linked together and actions 4/5/6/7 are linked together, you don't need to repeat the node statements for each one. You only need to list the connect statements ONCE for each linked group.

You have repeated action tests 4/5/6/7, separating the connect and disconnect statements. This is not necessary and may lead to problems.

You can check the status of a node's connections by typing /g_node_info <node _num>. The console will show you which nodes are connected to your inquiry node. Do this before and after the dynamite blows and you'll be able to tell if the connections were made. This is often easier than following bots around!

Here's how your aiscript should look:

MAPTYPE 0

action 27
{
node_connect 121 18 true
node_connect 121 66 true
}

action 25
{
node_connect 120 154 true
}

action 4
{
node_disconnect 83 126 false
node_disconnect 83 192 false
node_disconnect 83 63 false
node_disconnect 83 75 false

node_connect 261 126 true // this won't work because there are too many connections from node 126 already.
node_connect 261 192 true // same for 192
node_connect 261 63 true // same for 63
node_connect 261 75 true
}

#EOF

[Tiger]

Lol, that sure does seem easier. Thanks for the help. I'll test it out some time later on today or in the weekend coming up.