• 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

Editing and Switching from 2.2 to 3.x

H

Homer S

Well-known member
I have a behavior that I use frequently in 2.2 that I have not found a replacement for in 3.x.

When the leader of a unit is an upgrade to an existing model, the total number of models should remain fixed when the leader option is selected. In 2.2, I would add the attribute "modl:-1" to the option. How can this be replicated in 3.x?

I assume it is a script, but for the things I have tried I get an error about read-only.

Thanks,
Homer

P.S. The answer is here.
 
Last edited:
I'm looking at this again and I *thought* this was the answer:

The "entity.count[model] = entity.count[model] - 1" eval script is the equivalent of "modl:-1" from 2.2.

But is isn't. It reduces the count by one, but it also reduces the squad maximum by one.

Expected:
Current/Min/Max = 3/3/5 should change to 2/2/4 but it behaves like 2/2/3.

Any one know how to replicate this in AB3?

Homer
 
I just tried this, and if I have a unit who has 5-10 models, and I add a sergeant (whose option has the "entity.count[model] = entity.count[model] - 1" script), the unit count drops to 4, and the limits are now 4-9.

Are you sure there isn't something else that's affecting the unit count? Whereabouts in the data files is this problem taking place?
 
I'll take a look again. I wonder if it is related to the child being effective?

UPDATE: That's it! If the child is effective, it acts like it is double dipping. If the child is not effective, then it works right. This will get applied to any number of places in the files where a leader is an upgrade, like say an Eldar Exarch. That way, the squad goes from 5 base models to 4 base + 1 upgrade for the +xx cost.

Thanks!
Homer
 
Last edited:
One more monkey for the wrench. It is behaving now for adding the unit and dialing it up to maximum. If you dial it down to minimum, you can't get it down all the way. So, starting with a unit size of 5. Adding the upgrade sets it to 4+1. You can then dial it up to 9+1. You cannot dial it down to 4+1, just 5+1. You can remove the upgrade unit and re-add it to get to 4+1. Any other suggestions?

Homer
 
Homer S said:
One more monkey for the wrench. It is behaving now for adding the unit and dialing it up to maximum. If you dial it down to minimum, you can't get it down all the way. So, starting with a unit size of 5. Adding the upgrade sets it to 4+1. You can then dial it up to 9+1. You cannot dial it down to 4+1, just 5+1. You can remove the upgrade unit and re-add it to get to 4+1. Any other suggestions?

Homer
Click to expand...

I could let you borrow my Hammer of Coding +11, I used to you the +10 but this is one more then...
 
Homer, does my solution from post #3 work? If not, can you point to where in the data files I can see an example of the problem?
 
Colen said:
Homer, does my solution from post #3 work? If not, can you point to where in the data files I can see an example of the problem?
Click to expand...
I implemented your suggestion and here is the result. It is in the current Eldar files, choose any Aspect Warrior squad.

You can have it one of two ways:

1) Add an Exarch, so 5 become 5+1. You then have to dial it down to 4+1.

2) Upgrade an Exarch, so 5 become 4+1. This is what the codex states.

Case 1 is how it used to work. People complained that the pricing was wrong, since they didn't notice the squad size increased.

Case 2 is how it works now and the only issue is that if you dial it up and back down, you can't bottom it out. The workaround is to remove the Exarch and start again.

Any Thoughts?
Homer
 
Ah, I think this is the same problem that the author of the FB data files reported to us a while back. Unfortunately we didn't have time to implement a fix in AB3.3. :(

If you mark the Fire Dragon Exarch as "effective", the minimum limit will work properly. Unfortunately you'll then have the opposite problem - the maximum limit will be 1 too low with the Exarch added. The FB data files solved this by making the upper limit for the unit 1 too high, then giving a validation error if you took the maximum number of guys.

Unfortunately I can't think of a better way to handle this right now. :( It is on our to-do list, and it's hopefully something we can tackle in a future release of AB.
 
You must log in or register to reply here.
Back
Top