645 replies to this topic

[Mitchfork]

Setting the type to (None) in the enemy editor just prevents it from appearing, and trying ghost->Type = NPCT_NONE doesn't work either; zscript.txt says this is syntactically correct but won't actually do anything.

[Mero]

Setting the type to (None) in the enemy editor just prevents it from appearing, and trying ghost->Type = NPCT_NONE doesn't work either; zscript.txt says this is syntactically correct but won't actually do anything.

Try setting the "is boss death counter" attributeto to yes.

[Mitchfork]

Thanks, that worked.

[Saffith]

Just how are eweapons normally removed anyways. It's not delete is it. Cause then it's impossible to check.

Yes, they're just deleted.

This is a bit of a methods question: how would I go about having an enemy that respects combo solidity and relevant No Enemies flags while clipping through Link without dealing or taking damage and knockback? I can take care of taking damage with Ghost_SetAllDefenses(ghost, NPCDT_IGNORE), but I can't figure out a good way for the enemy not to cause knockback on Link. Setting ghost->CollDetection to false results in clipping through combos and flags, and I've also tried reducing the hitbox size. Any advice?

CollDetection is the right way to do it. It shouldn't affect walkability checking at all; if it does, something's not working right.

[Mitchfork]

CollDetection is the right way to do it. It shouldn't affect walkability checking at all; if it does, something's not working right.

Hmmm. I was using this script and it seemed like setting the CollDetection to 0 makes the enemy go anywhere on screen. I didn't try it in the script that I was writing though, so I'll investigate more once I get back to my laptop. Might have to do with the specific movement functions that were being used in that script, but I'm not sure.

EDIT: Well, ghost->CollDetection seems to work fine in my script. I don't know what it was about that particular instance that caused it to fail.

[Mitchfork]

Okay, another question (I know, I know)- how do I suppress the shadow from appearing on a specific enemy? I need them to have a Z value so that they're drawn over Link, but I don't want the shadow. The only settings I could find in ghost.txt were for shadow animation or eweapon shadows.

[Saffith]

If you're using real Z values, ZC draws the shadow itself, so you'd have to do something to stop it. I think setting npc->Tile to 0 might do it. You might have to do something tricky, though. You could modify its DrawXOffset in the global script; if you set it to 0 before DrawGhostFFCs() and set it to a very high number afterward, that ought to work.
I'll see if I can't add a "no shadow" flag for the next version.

[Mero]

Actually Saffith there's a much easier way to do it. Setting npc->Extend to EXT_NOSHADOW from std.zh will work.
Come to think of it. You might want to add GHF_NO_SHADOW which does just that.

[Saffith]

D'oh, completely forgot about that. Thanks.

[Moosh]

So ghost.zh has gotten pretty big. I mean you know it's pretty dang big when its own creator is forgetting about stuff. You think maybe it's time to stop expanding? I feel like the focus of ghost.zh has shifted from "Hey, let's make a useful base for custom enemies and bosses" to "Hey, let's make a second enemy editor out of scripts". The more stuff gets added to it the more I worry about whether my scripted stuff outside of ghost will break my ghosted enemies. Do you think you could either make an alternate version of ghost with only the basic features, say somewhere in the readme what not to mess with when using ghost, or include downloads for older versions in the OP? Any one of these would to some extent alleviate my concerns for any future projects I might want to use ghost.zh for.

[Saffith]

To be fair, that's an obscure ZC feature I forgot about, not a ghost.zh feature.
I've been pretty careful to minimize potential interference from other scripts, but, yeah, I should probably detail it in the documentation. Basically, if you avoid using npc->Misc[__GHI_GHZH_DATA] or eweapon->Misc[__EWI_anything] where eweapon->[__EWI_FLAGS]!=0, you shouldn't do any harm.


Incidentally, I just updated to fix a couple of bugs.

[Mero]

To be fair, that's an obscure ZC feature I forgot about, not a ghost.zh feature.
I've been pretty careful to minimize potential interference from other scripts, but, yeah, I should probably detail it in the documentation. Basically, if you avoid using npc->Misc[__GHI_GHZH_DATA] or eweapon->Misc[__EWI_anything] where eweapon->[__EWI_FLAGS]!=0, you shouldn't do any harm.
Incidentally, I just updated to fix a couple of bugs.

You added a few functions "Ghost_FloaterWalk" but it's not listed in the documentation yet.

[Saffith]

Ah, sorry. I didn't mean to add that yet; that's for the next minor version. I'm still reworking it a bit.

[Mitchfork]

Actually Saffith there's a much easier way to do it. Setting npc->Extend to EXT_NOSHADOW from std.zh will work.
Come to think of it. You might want to add GHF_NO_SHADOW which does just that.

Thanks, this worked for me.

[Demonlink]

Good night fellow members. I am having a little problem combining Active scripts, so I though I would post this here...

So, I want combine 2 global scripts so far, Saffith's ghost.zh and Lord Volcanon's Ice Combos

This is the result of my latest try using ghost version 2.6.1:

Spoiler

CODE

// ghost.zh
// Version 2.6.1

//Constants used by Ice Combos
const int CT_ICECOMBO = 142; //The combo type "Script1 by default"
const int ICE_ACCELERATION = 1;
const int ICE_DECELERATION = 1;
const int ICE_MAXSTEP      = 150;

//Declare Global variables used by "IceCombos.Z"
bool isScrolling;
bool onice;
float Ice_X;
float Ice_Y;
int Ice_XStep;
int Ice_YStep;
//End declaration


global script Slot2
{
    void run()
    {
        InitializeGhostZHData();

        //Setup variables for ice combos.
        Setup_IceCombos();

        //Variable that stores Game->GetCurScreen() the previous frame.
        int oldscreen = Game->GetCurScreen();

        //Main Loop

        while(true)
        {
            UpdateGhostZHData();
            UpdateEWeapons();
            CleanUpGhostFFCs(); // Only needed if __GH_USE_DRAWCOMBO is 0

            Waitdraw();
            
            AutoGhost();
            DrawGhostFFCs();

            Update_IceCombos(oldscreen);
            oldscreen = Game->GetCurScreen();

            Waitframe();
        }
    }
}

//Initializes global variables used for ice combos.
void Setup_IceCombos()
{
    isScrolling = false;
    onice = false;
    Ice_X = 0;
    Ice_Y = 0;
    Ice_XStep = 0;
    Ice_YStep = 0;
}

//Adds Ice Combo functionally to CT_ICECOMBO;
void Update_IceCombos(int oldscreen)
{
    //Update Variables
    if(Link->Action != LA_SCROLLING)
    {
        if(isScrolling || oldscreen != Game->GetCurScreen() || (!onice && OnIce()))
        {
            Ice_X = Link->X;
            Ice_Y = Link->Y;
            if(isScrolling)
                isScrolling = false;
            else
            {
                Ice_XStep = 0;
                Ice_YStep = 0;
            }
        }
        onice = OnIce();
    }
    else
    {
        isScrolling = true;
        return;
    }

    //Ice Physics
    if(onice)
    {
        //Y Adjustment
        if(Link_Walking() && (Link->InputUp || Link->InputDown))
        {
            if(Link->InputUp && !Link->InputDown)
                Ice_YStep -= ICE_ACCELERATION;
            else if(!Link->InputUp && Link->InputDown)
                Ice_YStep += ICE_ACCELERATION;
        }
        else if(Ice_YStep != 0)
            Ice_YStep = Cond(Abs(Ice_YStep) - ICE_DECELERATION > 0, Ice_YStep - Sign(Ice_YStep)*ICE_DECELERATION, 0);
        Ice_YStep = Clamp(Ice_YStep, -ICE_MAXSTEP, ICE_MAXSTEP);

        //X Adjustment
        if(Link_Walking() && (Link->InputLeft || Link->InputRight))
        {
            if(Link->InputLeft && !Link->InputRight)
                Ice_XStep -= ICE_ACCELERATION;
            else if(!Link->InputLeft && Link->InputRight)
                Ice_XStep += ICE_ACCELERATION;
        }
        else if(Ice_XStep != 0)
            Ice_XStep = Cond(Abs(Ice_XStep) - ICE_DECELERATION > 0, Ice_XStep -Sign(Ice_XStep)*ICE_DECELERATION, 0);
        Ice_XStep = Clamp(Ice_XStep, -ICE_MAXSTEP, ICE_MAXSTEP);

        //Reset the Ice Position to Link's Actual Position if he's hurt or hopping out of water.
        if(Link->Action == LA_GOTHURTLAND || Link->Action == LA_HOPPING)
        {
            Ice_X = Link->X;
            Ice_Y = Link->Y;
        }

        //Null appropiate step variable if Link would slide into a solid object.
        if(!CanWalk(Ice_X, Ice_Y, RadianAngleDir4(ArcTan(Ice_XStep, 0)), Abs(Ice_XStep/100), false)) Ice_XStep = 0;
        if(!CanWalk(Ice_X, Ice_Y, RadianAngleDir4(ArcTan(0, Ice_YStep)), Abs(Ice_YStep/100), false)) Ice_YStep = 0;
        
        //Return if not sliding.
        if(Ice_XStep == 0 && Ice_YStep == 0)
            return;
        Ice_X += Ice_XStep/100;
        Ice_Y += Ice_YStep/100;
        Link->X = Ice_X;
        Link->Y = Ice_Y;
    }
}

//Function used to check if Link is over a ice combo.
bool OnIce()
{
    int comboLoc = ComboAt(Link->X + 8, Link->Y + 12);
    return (Link->Z == 0 && Screen->ComboT[comboLoc] == CT_ICECOMBO);
}

//Returns true, if keyboard input is moving Link.
bool Link_Walking()
{
    if(UsingItem(I_HAMMER)) return false;
    else return (Link->Action == LA_WALKING || Link->Action == LA_CHARGING || Link->Action == LA_SPINNING);
}


item script GhostZHClockScript
{
    void run(int duration)
    {
        if(duration<=0)
            __ghzhData[__GH_CLOCK_TIMER]=-1;
        else
            __ghzhData[__GH_CLOCK_TIMER]=duration;
    }
}

The ice combos work fine, "But", when I setup Saffith's Armos Knights using this same script, well, they don't move, they just make the rumble sound then freeze. If I take out the ice combo scripts parts, the Armos work fine.

A little help please?