| 04-21-2009, 04:39 AM | #1 | ||
Quote:
What is the basis for the claim? Real world example seems to prove this wrong. Overly cautious map maker here... |
| 04-21-2009, 05:24 AM | #2 |
So, you responded by telling me I was wrong, then proceeded to start a new thread admitting you know not whereof you speak. Interesting. |
| 04-21-2009, 05:41 AM | #3 | |
Quote:
Incorrect. Where do I admit lack of knowledge? I started this thread out of respect for your reputation. I thought, how could someone so knowledgeable be completely wrong. I'm hoping others will fill in the gap here. |
| 04-21-2009, 06:50 AM | #4 | ||
Quote:
Quote:
|
| 04-21-2009, 10:04 AM | #5 | ||
Quote:
Regardless, your claim about the Widgetizer not working are false. I have plenty of abilities with more than four levels, and none of them fail after widgetization. Quote:
|
| 04-21-2009, 11:08 AM | #6 | |||||||||
The data for the rest of the levels staying in the war3map.w3a. Did some benchmarks for first add times of a 4 and a 16 level bonus life ability with and without widgetizing to show the differences; average of 4 tests. First load times:
In the original context of SetUnitMaxState, this shows four 4 lvl abilities >> one 16 lvl ability once widgetized. |
| 04-21-2009, 02:26 PM | #7 | |
That's a strange result Alexander. Supposedly the .w3* files are converted at load (whence the ridiculous load time of data-heavy maps when not widgetized), but if that's the case it doesn't seem like there should be a discrepancy for hybrid w3*-slk data after load. Quote:
|
| 04-21-2009, 05:08 PM | #8 |
Real world example demonstrated, locking. |
