Script/area problem.

[TheGreatCthulhu]

Are you sure there isn't a bug in the script itself? The fact that AddPropForce() works only means that OnStart() get's called, it doesn't tell you anything about the other functions. There could be other subtle errors.

For example, here:

PHP Code: (Select All)

AddEntityCollideCallback("Player", "area", "cake", false, 0); 


Are you sure that the first script area is named "area" in the editor?

You can use AddDebugMessage() to check which functions get called when. If a callback should be called but isn't, then it means that it wasn't hooked up correctly. Something along these lines:

PHP Code: (Select All)

// Debugging using AddDebugMessage()

void OnStart()
{
    AddDebugMessage("In OnStart().", false);   // The message will be displayed in the lower left corner
   
    AddPropForce ("rope_beam02_Body_1", 500, 0, 0, "world");  
    PlayMusic("12_amb.ogg", true, 0.8, 1, 1, true);   
    AddEntityCollideCallback("Player", "area", "cake", false, 0);
}

void cake(string &in asParent, string &in asChild, int alState)
{
    AddDebugMessage("In cake().", false);

    SetEntityActive("suitor", true);   
    AddEnemyPatrolNode("suitor", "PathNode1", 0, "");   
    AddEnemyPatrolNode("suitor", "PathNode2", 0, ""); 
    AddEntityCollideCallback("suitor", "ScriptArea_1", "cake1", false, 1);
}

void cake1(string &in asParent, string &in asChild, int alState)
{
    AddDebugMessage("In cake1().", false);
    SetEntityActive("suitor", false);
} 


[The chaser]

Delete map_cache if there is.

[TheGreatCthulhu]

I did not notice a debug message at any rate, when running through the area, so that means that it is being called, yes?

For a function, if the corresponding message was shown (each should be different, so that you can tell which one is it), then yes.

Done that, noticed it after second test but it still doesn't work.

Hm... If all checks out, then I'm not sure what's going on. Gotta go now, but I'm going to try and test the code later on, if the issue isn't resolved. For now, when you say it doesn't work, you mean that everything compiles, no errors are shown, but enemy doesn't patrol the area? What exactly happens, and what did you expect to happen?

Also, do you happen to use CreateEntityAtArea() anywhere in the script file (in parts not shown here, if any)? It says in the wiki:

When creating an enemy [using this function], it cannot chase properly along PathNodes(using for example ShowEnemyPlayerPosition).

[FlawlessHappiness]

Have you been to the properties of the area and unchecked "AutoRemoveAtLookAt" or something like that?

[Adrianis]

Does the enemy appear, and not walk along the path, or does the enemy just not appear at all?

[NaxEla]

Try

PHP Code: (Select All)

AddEntityCollideCallback("Player", "area", "cake", true, 1); 


[FlawlessHappiness]

Try

PHP Code: (Select All)

AddEntityCollideCallback("Player", "area", "cake", true, 1); 


That shouldn't change anything.
What you change there is that the scripts isn't able to call again, and only calls when the player enters the area.
Though it's a little strange to have it set to "...false, 0);"

[TheGreatCthulhu]

Another guess at what could be happening - if you add code to the script file and just hit "Quick Reload", only OnEnter() is called, if it exists, and OnStart() is not. OnStart() is only called when the player enters the map for the first time, or during development, only on full reload.

If the handler assignment code was added to preexisting code after you started the map (which would explain why rope swinging works), but you've only used quick reload, the updated OnStart() function is never called, so the cake() callback is never hooked up.

Edit: Apparently, that's not the case. Both OnStart() and OnEnter() get called on quick reload... God dammit. XD

P.S.

Though it's a little strange to have it set to "...false, 0);"

Nah. It may not be used so often, but it isn't strange if the collision needs to be detected only once.

[FlawlessHappiness]

Though it's a little strange to have it set to "...false, 0);"

Nah. It may not be used so often, but it isn't strange if the collision needs to be detected only once.

But if the detection should be only once then it should be true, and not false.

If it's false the monster will keep being set active, and be assigned patrol nodes everytime the function calls, and that's at least 2 times since the next value is 0

[TheGreatCthulhu]

Oh, sry - you are correct; I completely misread that code snippet. Didn't even notice the value of the last param.