I am having trouble with the Veterancy type behavior where the max level is not the same as the levels set in the Behavior: Veterancy Levels and the unit with the behavior is skipping levels.
My custom Veterancy behavior has levels 0,1,2,3 with Minimum Experience required as 0,100,100,100 respectively. In game the hero is leveling like this:
The level is skipping from 3 to 5, while the max experience cap is at 600. I tried disabling the Combine Experience and Combine Numeric Modifications flags in the Veterancy Flags field individually and together, but these didn't do anything.
I instead gave my hero Blizzard's default Test Veterancy behavior, which also has levels 0,1,2,3 with Minimum Experience required as 0,100,100,100 respectively. This gave my unit proper leveling while my behavior did not:
So I made a copy of the Test Veterancy behavior to see if it was an issue with my behavior. This new behavior is called Test Veterancy Copy. I applied this to my unit and I had the same error that I had with my original Veterancy Behavior. The level was skipping from 3 -> 5 and the max experience cap was 600. The leveling was the exact same as my original one, even though I made a direct duplicate copy of the properly working Test Veterancy.
The unit that I am testing with does not have any other behaviors, nor was I stacking any of the Veterancy behaviors. On the test map I was using, no other units had any Veterancy behaviors.
Edit (Additional information):
I also set the Gameplay Data "Default SC2 Gameplay Settings" fields related to Veterancy to the following: Stats: Veterancy Search Filters: Excluded: Player, Ally, Neutral, Enemy, Dead, Hidden Stats: Veterancy Search Max Count: 0 Stats: Veterancy Search Radius: 0
These were edited in order to disable XP sharing between units. I don't think these are related to my issue seeing as the Test Veterancy behavior is working fine.
Has anyone had similar issues or know any solutions to this? Any help would be appreciated.
Thanks.
I actually just updated my main post about that when you replied.
The unit that I am testing with does not have any other behaviors, nor was I stacking any of the Veterancy behaviors. On the test map I was using, no other units had any Veterancy behaviors.
Attached a screenshot of the Unit fields.
It currently has the Test Veterancy Copy behavior. This behavior is not giving proper leveling.
Some more background information: all my data is in a mod that my test map is using as a dependency. I have this test map set as the default test map through the Preferences > Test Document option.
So I gave both my hero unit and the Test Hero my Hero Veterancy behavior. Turns out when I run the test through the mod (which goes through the Preferences > Test Document and then runs my test map), I am getting the issues with the level skipping and max experience problems. However, when I run the map directly from the test map file, the leveling is working properly. So I think there may be some issue with the dependency linking between the test map and my mod.
There were some other issues when I ran directly from the test map though, like some ModelAddition actors that should be created on a UnitBirth event not appearing. I haven't tried removing and adding my mod again, but yeah it seems like there are some dependency issues in my test map that I'll need to look at.
Thanks for your suggestion about testing with the Test Hero, since that led to my finding the above issue.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I am having trouble with the Veterancy type behavior where the max level is not the same as the levels set in the Behavior: Veterancy Levels and the unit with the behavior is skipping levels.
My custom Veterancy behavior has levels 0,1,2,3 with Minimum Experience required as 0,100,100,100 respectively. In game the hero is leveling like this:
Level: 0 -> 1 -> 2 -> 3 -> 5 -> 6 -> 7 -> 8
Experience: 0/0 -> 0/100 -> 100/200 -> 200/300 -> 300/400 -> 400/500 -> 500/600 | Experience caps at 600
The level is skipping from 3 to 5, while the max experience cap is at 600. I tried disabling the Combine Experience and Combine Numeric Modifications flags in the Veterancy Flags field individually and together, but these didn't do anything.
I instead gave my hero Blizzard's default Test Veterancy behavior, which also has levels 0,1,2,3 with Minimum Experience required as 0,100,100,100 respectively. This gave my unit proper leveling while my behavior did not:
Level: 0 -> 1 -> 2 -> 3 -> 4
Experience: 0/0 -> 0/100 -> 100/200 -> 200/300 -> 300/400 | Experience caps at 400
So I made a copy of the Test Veterancy behavior to see if it was an issue with my behavior. This new behavior is called Test Veterancy Copy. I applied this to my unit and I had the same error that I had with my original Veterancy Behavior. The level was skipping from 3 -> 5 and the max experience cap was 600. The leveling was the exact same as my original one, even though I made a direct duplicate copy of the properly working Test Veterancy.
Level: 0 -> 1 -> 2 -> 3 -> 5 -> 6 -> 7 -> 8
Experience: 0/0 -> 0/100 -> 100/200 -> 200/300 -> 300/400 -> 400/500 -> 500/600 | Experience caps at 600
The unit that I am testing with does not have any other behaviors, nor was I stacking any of the Veterancy behaviors. On the test map I was using, no other units had any Veterancy behaviors.
Edit (Additional information): I also set the Gameplay Data "Default SC2 Gameplay Settings" fields related to Veterancy to the following:
Stats: Veterancy Search Filters: Excluded: Player, Ally, Neutral, Enemy, Dead, Hidden
Stats: Veterancy Search Max Count: 0
Stats: Veterancy Search Radius: 0
These were edited in order to disable XP sharing between units. I don't think these are related to my issue seeing as the Test Veterancy behavior is working fine.
Has anyone had similar issues or know any solutions to this? Any help would be appreciated.
Thanks.
hmm sry that i have to ask this, but does your hero have other veterancy behaviours? can you show a screenshot of your hero?
@FunkyUserName: Go
I actually just updated my main post about that when you replied.
The unit that I am testing with does not have any other behaviors, nor was I stacking any of the Veterancy behaviors. On the test map I was using, no other units had any Veterancy behaviors.
Attached a screenshot of the Unit fields.
It currently has the Test Veterancy Copy behavior. This behavior is not giving proper leveling.
@Xethyr: Go
what happens if you give the Test Hero your behaviour?
Some more background information: all my data is in a mod that my test map is using as a dependency. I have this test map set as the default test map through the Preferences > Test Document option.
So I gave both my hero unit and the Test Hero my Hero Veterancy behavior. Turns out when I run the test through the mod (which goes through the Preferences > Test Document and then runs my test map), I am getting the issues with the level skipping and max experience problems. However, when I run the map directly from the test map file, the leveling is working properly. So I think there may be some issue with the dependency linking between the test map and my mod.
There were some other issues when I ran directly from the test map though, like some ModelAddition actors that should be created on a UnitBirth event not appearing. I haven't tried removing and adding my mod again, but yeah it seems like there are some dependency issues in my test map that I'll need to look at.
Thanks for your suggestion about testing with the Test Hero, since that led to my finding the above issue.