Not that one, no. That's probably an old log. The latest one is what i need.
I know exactly what's happening. This is actually a logic error of the Monk's combat routine.
In the MonkCombat.cs, first it will check whether it's a WoL build. If yes, it goes to GetWolPower() to cast WoL. Here is the trick: the author forgets that there WoL monks using THE LEGACY OF LIGHTMARE set who have no need to have SW stacks. And the file's WoL condition is having at least one stack of SW. So many LEGACY OF LIGHTMARE WoL monks end up casting nothing.
Besides this ,it also has another bug: The GetWolPower() method does not check whether it needs to cast blinding flash; it will therefore ignore the blinding flash, which can recover 165 energy and is very common in LEGACY WoL build.
[HIDE]I have another suggestion. In the casting WoL statement, the author uses GetBestClusterPoint(), which will lead to some issues: it will often make the player go to somewhere close to the mobs, which not only increase the chance being attacked by the mobs, but also cannot make the best use of the Zei Gem. I personally change it to CurrentTarget.Position, so that it casts WoL on the far away immediate target, which is not only safer but has higher damage because of Zei. However I think the best position to cast WoL is to offset the CurrentTarget.Position a bit because there are minor chances that if you cast WoL on the exact position of the mob, it cannot hit the mob if the mob size is very very small. But since I don know what data type the "Position" is ,I cannot implement this.[/HIDE]
Attached is my fixed Monk combat routine. It needs Trinity .39 and ONLY works well with LEGACY OF THE NIGHTMARE WoL monk because:
1, I deleted the SW stacks check
2, it can cast blinding flash off CD (if you check non-stop blinding flash)
View attachment MonkCombat.cs
Edit:
After more observing , i found the default target selection i.e. the GetBestClusterPoint() works very well, so I retrieve my suggestion.