Runes of Magic US / AU

DIYCE was created for that purpose.

Quoted from "kkulesza"

DIYCE was created for that purpose.

And what about the people who might want a simple macro but don't want automation? I know all the arguments for and against, so don't get started.

You can configure DIYCE to work as simple macro.
Of course if for some reason you don't want diyce, then you can write a complicated macro.
But doing it with diyce is IMO simply faster.

DYICE was created for people who had disabilities and for people with bad internet hook ups, that is why it was created and allowed. But now apparently every ROGUE in the game is disabled, loll. Just remove DYICE and see how easy it is to kill a rogue loll.



No disrespect to people with disabilities in any shape or form.

off the top of my head...
/run for i=1,40 do if UnitDebuff("target", i) == "Shadow Prison" then SP = true break end end if (not SP) then CastSpellByName("Shadow Prison") end


check target debuffs 1 at a time (max of 40). If a debuff at index i is shadow prison (change "Shadow Prison" to w/e the ACTUAL debuff name comes up as when used on a target) then set SP true and stop checking, otherwise check the next buff. If no shadow prison was found, cast shadow prison.

this should work everytime... (checks for 50 debuffs just because you cant have more than 40 so it wont miss the debuff for sure)

assuming you want to check for the debuff...

/run for i=1,50 do if (UnitDebuff("target", i)=="Shadow Prison") then break elseif (i==50) then CastSpellByName("Shadow Prison") end end

--------------------------------

assuming im wrong and its actually a buff...

/run for i=1,50 do if (UnitBuff("target", i)=="Shadow Prison") then break elseif (i==50) then CastSpellByName("Shadow Prison") end end

Quoted from "Amberwave"

The problem with it being in DIYCE is that it will either cast it or it will not, every time. DIYCE will look to see if Shadow Prison is on the target, and if it does not it will cast. There are many mobs I do not want or need to Shadow Prison.

It's not a problem with diyce. Macro works the same way.
I think you misunderstand how diyce works and what it actually does.

Quoted from "zidlef"

DYICE was created for people who had disabilities and for people with bad internet hook ups, that is why it was created and allowed. But now apparently every ROGUE in the game is disabled, loll. Just remove DYICE and see how easy it is to kill a rogue loll.

If that is Your way to justify the fact that You're not able to program Your diyce, then it's fine by me

Quoted from "BlankMinded"

/run for i=1,40 do if UnitDebuff("target", i) == "Shadow Prison" then SP = true break end end if (not SP) then CastSpellByName("Shadow Prison") end

Quoted from "Amberwave"

It will only work one time. Period. If I relog, it will work again, once. Hmmm.

It works only once after logging in, because variable SP is set to true at first time and it stays that way until you logout.
Setting it to false at the begining of the macro should make it work every time:

/run SP = false; for i=1,40 do if UnitDebuff("target", i) == "Shadow Prison" then SP = true break end end if (not SP) then CastSpellByName("Shadow Prison") end

Quoted from "zidlef"

DYICE was created for people who had disabilities and for people with bad internet hook ups, that is why it was created and allowed. But now apparently every ROGUE in the game is disabled, loll. Just remove DYICE and see how easy it is to kill a rogue loll.



No disrespect to people with disabilities in any shape or form.

+1 to this. Button mashers for the win. *brofist*

What's even better is my Knight taking out Rogue's while button mashing against DIYCE. Good fun that.

Wrote the original macro while haalf asleep. Just replace "local SP = true" where you see "sp" before. As it was before, sp ws globaal variable existing outside the macro and therefore not reset when the macro is used. derp

Quoted from "zidlef"

DYICE was created for people who had disabilities and for people with bad internet hook ups, that is why it was created and allowed. But now apparently every ROGUE in the game is disabled, loll. Just remove DYICE and see how easy it is to kill a rogue loll.

This would be ...




DIYCE was never meant for people with disability only, and from beginning was project to build perfect way to use and best utilize all skills available for your class.

Quote from sixpak (coder of original DIYCE) best describes DIYCE

Quoted

Note that this does not automate your combat (sorry bot lovers), it just picks the best attack to execute every time you hit the macro.

Reason that some people get upset as their class does not require more then 2-3 buttons (in case of P/S it was one button, wasn't it ZId?) while some other class combos had to worry about bleeds, position to target, proximity... etc. and many different skills with CD on most of them, while worrying about energy or focus... (task for robot if you ask me) is beyond my understanding.

Also, as DIYCE is basically Do it yourself, you can make it as dumb as you want. For one class I have DIYCE just do 1 single hit. Reason I like to use DIYCE and not just skill button - my dice will check all my buffs, refresh one that are timing out, once mob is dead, it will select next target and if my HP goes down, i twill heal my toon... Sounds simple, but not so simple to write and make everything work if you don't know what you are doing.

Sure, I could do all that manually, but that takes lots of fun from the game. I rather focus more on next mob and or chat then make sure all my buffs are on all the time...

And yes, recomended way to to above is to create DIYCE script that will cast your skill of no SP has been spotted on target. It will be one button hitting - cast SP if no SP, or nothing happens if there is SP.

Quoted from "RoMage"

Quoted from "zidlef"

DYICE was created for people who had disabilities and for people with bad internet hook ups, that is why it was created and allowed. But now apparently every ROGUE in the game is disabled, loll. Just remove DYICE and see how easy it is to kill a rogue loll.

This would be ...




DIYCE was never meant for people with disability only, and from beginning was project to build perfect way to use and best utilize all skills available for your class.

Quote from sixpak (coder of original DIYCE) best describes DIYCE

Quoted

Note that this does not automate your combat (sorry bot lovers), it just picks the best attack to execute every time you hit the macro.

Sure, I could do all that manually, but that takes lots of fun from the game. I rather focus more on next mob and or chat then make sure all my buffs are on all the time...

Your statement there is what boggles my mind. How does pressing one button and having a script do everything for you constitute any kind of fun? The fun is trying to get in a routine to make sure you don't need a secondary program to do it for you. Using scripts like diyce imo is tantamount to botting, and thats how I view it. You don't agree that's fine, but don't get offended when I label you a botter.

Quoted from "Ziav"

Your statement there is what boggles my mind. How does pressing one button and having a script do everything for you constitute any kind of fun?

fun is relative...get over it...and, as ghostwolf has explained in a multitude of threads, DIYCE =/= botting...

This isn't my job, but this thread isn't about DIYCE. So stop beating a dead horse.

/run SP = false; for i=1,40 do if UnitDebuff("target", i) == "Shadow Prison" then SP = true break end end if (not SP) then CastSpellByName("Shadow Prison") end

that worked amazingly for me. Tyvm.


going to add to www.tinyurl.com/bbsaddons

Can that be modified for any skill? Example:

/run SP = false; for i=1,40 do if UnitDebuff("target", i) == "Silence" then SP = true break end end if (not SP) then CastSpellByName("Silence") end

?

Quoted from "bleedingblak"

Can that be modified for any skill? Example:

/run SP = false; for i=1,40 do if UnitDebuff("target", i) == "Silence" then SP = true break end end if (not SP) then CastSpellByName("Silence") end

?

Yes, but be aware that skill name and debuff name are not always the same. So check it twice.

Also there are very many debufs that stun, root, fear or silence a target. Listing them all in single macro might be impossible. That's where diyce comes in handy.

Quoted from "kkulesza"

Quoted from "bleedingblak"

Can that be modified for any skill? Example:

/run SP = false; for i=1,40 do if UnitDebuff("target", i) == "Silence" then SP = true break end end if (not SP) then CastSpellByName("Silence") end

?

Yes, but be aware that skill name and debuff name are not always the same. So check it twice.

Also there are very many debufs that stun, root, fear or silence a target. Listing them all in single macro might be impossible. That's where diyce comes in handy.

So the modified version would have to be the name of the DEBUFF and NOT the SKILL? I understand that. Which makes me wonder if there is a way to do this by the ID of a debuff instead.... no point though, I presume.

Good point with the different forms of silences... the macro would only introduce /if this very specific silence is on the boss, do not use this specific silence [even tho there may be a different version (ID) on the boss already] else silence.\

There might be a way to use the whitelist/blacklists in smarthbuff bars addon to check for this (use one list to put all silence buffs in then check: if debuff at index i is in SmartBBwhitelist then make sp true (i.e do nothing). else make sp is still false and shadow prison (or w/e else) will be casted.

Would have to find some way to reference the appropriate white/blacklist (which should be accessible from a macro if memory servers me correct)

SIDENOTE: you can use something like for "i=1,40 do if Unit(De)Buff(unitname, i) then" to do check for debuffs or buffs on your target, your self, your warden pet, your target's target , w/e you can use as the unitname that the game recognizes, then perform actions (like cancel buffs, cast skills, say soemthing in chat, use an actionbar slot for immune food, etc)