• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

AUTHORING - Changing a parent unit's min/max sizes via options

H

Homer S

Well-known member
I found how to change a child unit's sizes when added as a link via an option (sizescript). My question is can you point me to some sample code of how to set a parent unit's sizes via an option? Note that the unit will have to exist in the same list default and changed, so overrides and global tags are out (unless someone knows how).

Thanks!
Homer
 
I don't think there's a way to change a parent unit's size, just that of a child unit. What exactly are you trying to accomplish? It's possible we can figure out some way of doing what you need. :)
 
Colen said:
I don't think there's a way to change a parent unit's size, just that of a child unit. What exactly are you trying to accomplish? It's possible we can figure out some way of doing what you need. :)
Click to expand...

I believe the goal was to try an simulate something from the new Tyranid list. A certain model can actually spawn other entirely dissimilar models in the game. Homer was trying to figure out a way that these spawn models, which are of course one of the possible units you can normally take for your list, could be added into the roster as a reference. So that the basic stats could be displayed as a unit, but the unit would need a model size of zero as it is only for information - it should not add models to the list nor should it be considered for composition and the like.

Or in perhaps clearer language he wanted to have a unit add another unit into the roster but with a size of 0 which could not be modified or count for composition although the unit could nominally be taken outside of this one unit.
 
Can you have an assortment of child units with model counts of zero beneath the spawning model? Then you could add a global tag for each of the units when it is *not* a child unit. The option that attaches the child unit would disable itself if the global tag is present. The net result is that all the potentially spawned units would be listed beneath the spawner, except if that unit already existed in the roster as a top-level unit.

Just thinking out load here. I'm not sure if this would fly, but it could be a viable solution.
 
D'oh! You took my line!

I did the line addition, that is changing a child's size. I suspect I just reinvented the Necron's wheel on that one...

Unfortunately, I forgot the original situation I was asking about. It might have had something to do with an Apoc formation. I'll have to think about it again.

Homer
 
You must log in or register to reply here.
Back
Top