Restoring broken item

[Damascus]

In my custom story, I've put it an item that is destroyed when it's thrown hard enough against something (preset under the BreakEntity properties of the entity). However, I want to be able to restore it, unbroken, to its original position when it's destroyed.

So far, setting the entity active/inactive hasn't brought it back. Neither has ResetProp. I don't think I can create a different entity either, because it also needs to respond to the same script that worked on the original. Can anyone help me?

[7heDubz]

dont let it break? or is it imperative to the story that it breaks?

[Daemian]

Hey DAmascus ;p
I think you're gonna have to create the entity again along with its callbacks.
It worked fine for me.

[Damascus]

@WIWWM: Yeah, it is crucial the story that it breaks, but only under certain circumstances.

Hey DAmascus ;p
I think you're gonna have to create the entity again along with its callbacks.
It worked fine for me.

I used CreateEntityAtArea to respawn it, and it worked... twice. After I broke the item for the third time, it stopped coming back. I repeated the experiment several times, but every time, the CreateEntityAtArea only triggered twice. I'll include my code here:

PHP Code: (Select All)

void CheckGold(string &in asTimer)
{
    if (GetPropHealth("potash_1") < 1)
    {
        if (GetLocalVarInt("Pillar") == 1)
        {
            AddTimer("", 1.0f, "BlowPillar");
            SetEntityActive("SignArea_1", false);
        }
        else
        {
            CreateEntityAtArea("potash_1", "crystal_rock_02.ent", "FulmGoldArea", false);
        }
    }
    else
    {
        AddTimer("check", 0.1f, "CheckGold");
    }
} 


Basically, this timer is constantly checking the health of the item. Once it breaks, if it's inside the proper area, a custom script is triggered. If it's not, a new item should respawn at FulmGoldArea.

[Your Computer]

When an entity breaks, it gets replaced with an entity that is supposed to represent its broken state. This "broken" entity no longer represents the original entity, therefore ResetProp, etc, doesn't work.

For your current code, you're probably going to have to increment the prop name. Not sure if inspection mode can help with writing a more suitable kind of code.

[Statyk]

What if you place a second entity of it, set it inactive, and when the first gets broken, activate the second entity?

[Daemian]

OnStart {
SetEntityCallbackFunc( "ent123", "ReplaceMeOnBreak" ); }

void ReplaceMeOnBreak ( string &in e, string &in t )
{ if t == "Break", CreateEntity e at area; SetEntityCallbackFunc( e, "ReplaceMeOnBreak" ); }


Something like that.

[Damascus]

Okay, I was stupid. The part of the script that was creating the new item wasn't resetting the timer. Now that I've fixed that, the item respawns endlessly. BUT, I have a new problem. When I break the first item within BlowPillarArea, the BlowPillar timer activates. However, with the new items that are produced, they do not trigger the timer, even if they are within BlowPillarArea. Instead, they simply respawn again.

This is especially odd because I know the new items all must have the same name, otherwise the script that is respawning them wouldn't work either!

PHP Code: (Select All)

void OnStart()
{
    AddEntityCollideCallback("potash_1", "BlowPillarArea", "PillarVar", false, 0);
}

void PillarVar(string &in asParent, string &in asChild, int alState)
{
    if (alState == 1)
    {
        SetLocalVarInt("Pillar", 1);
    }
    else if (alState == -1)
    {
        SetLocalVarInt("Pillar", 0);
    }
}

void CheckGold(string &in asTimer)
{
    if (GetPropHealth("potash_1") < 1)
    {
        if (GetLocalVarInt("Pillar") == 1)
        {
            AddTimer("", 1.0f, "BlowPillar");
            SetEntityActive("SignArea_1", false);
        }
        else
        {
            CreateEntityAtArea("potash_1", "crystal_rock_02.ent", "FulmGoldArea", false);
            AddTimer("check", 0.1f, "CheckGold");
        }
    }
    else
    {
        AddTimer("check", 0.1f, "CheckGold");
    }
} 


[Adrianis]

Use a debug message to print the names of the new entities being created, to make sure that they do have the same name - the way the issue is manifesting sounds exactly like the names of the new ones are not the same.
You can do that in the collide callback function, print the name of the colliding entity

It's possible that there is some security code in the source to prevent errors by adding numbers to names of objects being created if the name is the same (in the same way that the level ed will add _x to an entity when you duplicate it)

[Damascus]

Unfortunately, I can't use debug mode (link). I will keep working on it today and see if I can find a way around it.