Team Robot Simulator and Gear Comparison Tool - Page 12

Eilanara · 03/10/10, 2:30 AM

Are you working on the other classes...an wil the heal be included?

aceofsween · 03/10/10, 12:00 PM

How does the Simulator treat Nibelung? It looks at the moment that it simply applies a DoT, which isn't altogether a bad way of doing things, but how does it handle multiple Val'kyr procs? Also, does it use the original 1% proc rate or the new 2% proc rate?

The reason I ask is that I never seem to see in the combat log results that it procs more than twice. In most situations though, I'm casting well over 200 spells, closer to 250 really, which would imply an average of 4 or 5 procs.

Yellowsix · 03/10/10, 1:50 PM

I think nibelung is still using the old 1% proc rate... I'll update it to 2%.

I model nibelung as a "rolling" DoT to deal with multiple val'kyr. That's of course not exactly what happens, but the total damage dealt should be correct. It's a minor hack to work around the fact that the simulator doesn't like having 2 DoTs going at the same time with the same name/ID.

We are working to add every class to Team Robot: mages and warlocks are in development and should be available soon.

Eventually we'd like to add support for tanking and healing, but we have no timeline for that. All of the DPS classes will come first.

ithatan · 03/11/10, 11:28 AM

I tried this briefly, it looks pretty cool and I love how easy it is to use. Three suggestions:

1) Save the buff settings. The app seems to be able to save configurations of everything else, it's weird that it doesn't do this. I keep having to select my ArP food and lack of Bleed damage %.

2) A "maximum power" condition. I think it's still the case that you still want to use Ferocious Bite at minimal energy.

3) Add a time remaining to the "has one or more stacks" of a buff condition. I only want to FB if both Rip and SR are >= 9 seconds, for example.

Yellowsix · 03/11/10, 2:21 PM

Saving buff settings is definitely on my to-do list.

You can get a "maximum power" condition with the NOT operator:

NOT (HAVE AT LEAST 40 POWER)

That would be true any time you have less than 40 power.

You can do time remaining on an dot or aura in a similar manner:

NOT (TARGET MISSING [RIP BLEED] OR LESS THAN 9 SEC REMAINS)

This is true whenever the target has the rip bleed and more than 9 seconds remain.

We definitely want to make the rotation editor more intuitive eventually, but with a little cleverness, you can make it do most of the things you need for now.

conghaile · 03/11/10, 5:38 PM

Had a question on possible conditional options.

I wanted to test a case where moonfire would be applied unless moonfire is already up, solar eclipse has more than 7 seconds left, or lunar eclipse has less than 3 seconds left, thus I looked to do a conditional table that looks sort of like this:

Only execute Moonfire if:

NOT Target has Moonfire
AND

Lunar Eclipse aura is on (yourself) and less than 12 seconds have passed.
OR
NOT have >= 1 stacks Lunar Eclipse.
AND
NOT have >= 1 stacks Solar Eclipse.

OR
Solar Eclipse aura is on (yourself) and more than 8 seconds have passed.

It doesn't appear measuring time left on auras you already have is an option, and using the cooldown timing conditional is clunky as balance since one eclipse aura gained can proc both cooldowns if both eclipses are cooled down. Is there any way to implement my case using current conditionals that I missed?

Yellowsix · 03/11/10, 6:07 PM

Note 1: for the "aura" conditions, the text will say "TARGET", even though auras typically refer to buffs on yourself. Don't worry about that, if you do an "aura" condition and choose Solar Eclipse, it will work just fine. Note also that the "aura" conditions work for buffs on yourself OR debuffs on your target. Thus the slight funkiness in wording. (The latest version that I have not posted changes this language to say "PLAYER", which I think will make more sense in most cases.)

If I'm reading your condition correctly, in english, you want:

Cast moonfire if:
- the moonfire DoT is not already up
- solar eclipse isn't up or if it is, it has less than 7 seconds left
- lunar eclipse isn't up or if it is, it has more than 3 seconds left

Your full condition would become:

ONLY EXECUTE MOONFIRE IF:

NOT (TARGET HAS [MOONFIRE DOT])
AND 
PLAYER MISSING [ECLIPSE SOLAR] OR LESS THAN 7 SEC REMAINS)
AND
(
  NOT (PLAYER MISSING [ECLIPSE LUNAR] OR LESS THAN 3 SEC REMAINS)
  OR
  NOT (HAVE >= 1 STACKS OF [ECLIPSE LUNAR])
)

• Hamlet · 03/11/10, 6:09 PM

Originally Posted by conghaile

Had a question on possible conditional options.

I wanted to test a case where moonfire would be applied unless moonfire is already up, solar eclipse has more than 7 seconds left, or lunar eclipse has less than 3 seconds left, thus I looked to do a conditional table that looks sort of like this:

[/indent]
It doesn't appear measuring time left on auras you already have is an option, and using the cooldown timing conditional is clunky as balance since one eclipse aura gained can proc both cooldowns if both eclipses are cooled down. Is there any way to implement my case using current conditionals that I missed?

See what I was doing here:
Team Robot Simulator and Gear Comparison Tool
I was looking at something different, but the same idea should work.

There's a bit of confusion between "player" and "target" in the condition description in the rotation editor, but the "target aura" one works for Eclipse.

Yellowsix · 03/25/10, 6:37 PM

3.3.3 changes have been posted! A full list of changes is at:

WoW Simulator Change Log

There was only one bug fix for moonkin from the 3.3.3 beta to the current live version: glyph of focus was giving the old 20% multiplier to the AoE splash part of starfall instead of the new 10%.

gannonjf · 03/26/10, 7:36 AM

Looks like the Phaly trinkets haven't been updated within the tool to reflect the minor buff Blizzard gave them in 3.3.3. I'm curious to see how that will change the rankings for trinkets, if at all.

Yellowsix · 03/26/10, 3:47 PM

edit:

The tooltip is showing the old tooltip for [Phylactery of the Nameless Lich], but the code is actually using the new spell power values. When the armory is back up, the new tooltip should show up at some point... the old one is still cached on the server, but the cache should expire in a little while.