magnomagus said:

---

@dredknight: you think it is too powerful?

---

dredknight said:

---

magnomagus said:

---

@dredknight: you think it is too powerful?

---

First it does not matter if it is too powerful or not.
It just does not scale through the levels, it is always 103 + 3*Sp.
This is not good because Might heroes can equip destruction books.
Then their units can easily just one hit any opponent monster that has been cast Deep freeze.

Actually the whole mastery scaling spell efficiency is important for all spells because of those books.

Actually I can try it out and share the results.

---

Quote:

---

What I mean is that with 0 spellpower a might hero gets 103% physical damage increase, which is huge.

---

magnomagus said:

---

Do you recommend using it with exe files based on 3.1 or QAI31j?

Are there any known bugs for these exe files?

---

magnomagus said:

---

Quote:

---

What I mean is that with 0 spellpower a might hero gets 103% physical damage increase, which is huge.

---

Wait, what?, I thought 103% means = damage x1.03 , at least that is how the fan manual explains it. This requires verification.

---

thGryphn said:

---

Alright, so, here's the status of the skillwheel (SW):

1) Aside from a few cosmetic things (like highlighting special case prerequisites) it's done.

2) However, it takes a 3-8 seconds to load depending on the system. My Haswell+SSD system takes 5 secs tops.

3) Now, it wouldn't be a problem if this load time was one-time. The problem is, whenever you access a screen where the SW can open from, it loads again, costing these secs, which builds up to be annoying.

For example, to be able to open the SW from the hero screen page (where skills, abilities, etc tabs are), I have to make it so that the SW is included among the files loaded with the hero screen. This means, whenever you double-click your hero, that's 3-8 secs. Even there, whenever you click on the side arrows to move from one hero to the other, that's another 3-8 secs each time. Whenever two of your heroes meet, that's also 3-8 secs. I, as the maker, find it annoying, nobody will like it to say the least...

I tried making it uglier (worse textures) but it didn't speed up, nothing observable at least. It takes these 3-8 secs to load only because there are many (24 to be exact) wheels loaded, each including about 120 icons and descriptions, fetched from different folders. Mind you, I optimized it to my best ability (using common skill locations on wheel whenever possible) but still the amount of icons and descriptions that needs to be fetched cannot be reduced.

So, here's the solution I came up with, with a little compromise and great benefits: Instead of opening the SW from the hero screen, you open it from the adventure screen, using its button placed on the resource bar (right end of it).

Compromise: You won't be able to open the SW immediately after looking at your hero's skills/abilities at the hero screen; you will have to exit the hero screen and then click the SW button (at the resource bar). After many trials, I do not find this to be any issue. I mean, you could never see both (your hero skills and the SW) at the same time anyway...

Benefit: You can open the SW anytime right from the adventure screen

Huge Benefit 1: The SW is loaded only ONCE PER GAME SESSION, costing you 3-8 secs only once, and being lightning fast during gameplay. This also means the hero screen is as fast as ever.

Huge Benefit 2: The SW remembers where you left off, down to the last perk description you opened!


Along all this, the Level-Up screen is also supported, and although I have to load a few extra things there, it's very fast to load with no observable overhead. The only thing I couldn't solve is that when you open the SW at the Level-Up screen, it does not remember the last state and it opens a fresh one at each level-up.




To summarize: Get ready to open the SW from the adventure screen, instead of the hero screen. May sound like a compromise but the benefits are huge I'm working on the last bits like special prereq highlighting and I'll post a finalized version when that's done.

---