Limiting of 1 Single Upgrade Structure

[Somatic]

I have a Building which is upgraded from another Structure. But I want to make it such that When this Building is Build, the Base Structure this Building is Upgraded from is not avabilar to be Constructed again.

Ill Briefly Explain this, My Base Structures Upgrades to the Super Weapon Base. Which can be Upgraded to 3 different Structures. And, My aim is to Make the Super weapon Base Impossible to be upgraded from the Base Structure, after you own either of the Super Weapon.

Any idea?

 

[Ghan]

Something like this might work:

Not Available
    Events
        Unit - A unit Finishes an upgrade
    Conditions
        (Unit-type of (Triggering unit)) Equal to <Some Unit-Type>
    Actions
        Player - Make <Some Unit-Type> Unavailable for training/construction by (Owner of (Triggering unit))

 

[elmstfreddie]

Naw that only works for building the unit. Not upgrading to.

Maybe if he already has one you could set the upgrade progress to 0%?

 

[Ghan]

> Naw that only works for building the unit. Not upgrading to.

Tested and verified. Fires for upgrades.

 

[elmstfreddie]

> Naw that only works for building the unit. Not upgrading to.

Tested and verified. Fires for upgrades.

>_>
Oh. You learn something everyday... Even things I should've known a long time ago >_>

 

[AceHart]

And, if your only structure is destroyed?


Player - Limit training / construction of <unit type> to 1 for Player 1
Repeat for all players, in some trigger with the event "map init".

And, to get this requirement to the new structure, add your new structure(s) to the base structure's "techtree - dependency equivalents".

That should do it. Without triggers.

 

[Ghan]

> Player - Limit training / construction of <unit type> to 1 for Player 1

I'm not sure where you're going here. I though about that, but then when the building is upgraded, there won't be one of that unit-type, allowing you to build another base unit. How does using the Dependency Equivalent get around that?

 

[AceHart]

> How does using the Dependency Equivalent get around that?

...

By telling the game that the base structure should still have some importance when changed to one of those...
Or the other way around, by telling the game that the new upgraded structure actually is equivalent to the previous base structure.

 

[Ghan]

Oh, got it. The game thinks those structures are the same. At least, as far as the requirements go.

 

[Somatic]

Thanks For All Your Help. +rep =)