Originally Posted by
Langy
Lappee thoughts on Boomy thus far? Is it looking better than mop and does it look like it can compete for top rankings? Ive always played warlock but ive been watching hotted stream wod boomy quite a bit and it is looking a lot nicer to play for sure.
PvE wise, I still hate the new eclipse mechanic. Just doesnt quite feel like Im in control of it. Leveling and PvP wise the changes so far are awesome.
Originally Posted by
Cyous
@lappee
For the pure timer, we could manually import the formulas for SWE:
MAX(-100,MIN(100,105*SIN(T*PI()/20)))
MAX(-100,MIN(100,-105*SIN(T*PI()/20)))
But I don't know a "good solution" to the issues caused be AC, aside from tacking on 0.3sec worth of time every 0.10sec channeling AC.
Pure timers are just pain in the ass to make. Need to check different things all the time like CA, CA glyph, AC, Eclipse point when combat starts (if it isnt @ 0) etc, I'd much rather prefer if the game told us the sine value instead of eclipse energy :/.
Originally Posted by
CollisionTD
action.starsurge.recharge_time<3
I can add in starsurge charges to the sample table, I'll just hack in a buff that returns the current amount of charges available. Eclipse Energy will be a little more difficult, but I think I can do it by disabling mana from showing up there and telling it that eclipse is the primary resource. I'll try and add it in sometime today.
That would be really helpful, cheers!
Originally Posted by
Cyous
I'm trying to add "Time to next Eclipse" using Lua and it's more-so the text editor, in-game, not liking my code. So I'll try to add it later. But for now, most of my time today was spent learning WA's structure. And now that's pretty much gtg.
Here's what I have so far.
http://imgur.com/OYIuIvV
@Collision
Thank you for the source code link
I have something similar made into the addon (Time till eclipse changes, aka goes past 0 marker, which is what i personally care about and needed for the addon).
Code:
if GetEclipseDirection() == 'moon' then
moon = true
else
moon = false
end
currentPowerTime = math.asin(UnitPower('player', SPELL_POWER_ECLIPSE)/105)/math.pi*20
if moon then
eclipseAfterCast = math.sin((currentPowerTime-castingTimeLeft)*math.pi/20)*105
else
eclipseAfterCast = math.sin((currentPowerTime+castingTimeLeft)*math.pi/20)*105
end
if moon and eclipseAfterCast > 0 then
eclipseChangeTime = abs(currentPowerTime)
elseif moon and eclipseAfterCast < 0 then
eclipseChangeTime = 20 - abs(currentPowerTime)
elseif not moon and eclipseAfterCast < 0 then
eclipseChangeTime = abs(currentPowerTime)
else
eclipseChangeTime = 20 - abs(currentPowerTime)
end
Now obviously you dont need castingTimeLeft and eclipseAfterCast there so you can remove them and replace (if needed) with current eclipse (incase of eclipseAfterCast) and you'll should have it, more or less (still gets fucked up @ 100 energy, stopping at 8.02 something seconds and continuing from there after ~4seconds). Hopefully it helps abit