just wanted to say thanks uure for posting those. i didn't use them as they are, but i pulled from them to make some custom target/attack macros...
lol, really? No way there was anything new to you here.

But it's always nice if sometimes simple repeating things we "know" triggers this "Oh, wait, could I actually...".
hello how do rogue/mage combo attack macro ?
Do you mean "
combo throw" macro or a way to activate the correct combination/sequence of skills (
combo of skills)?
========
For Combo Throw: you could simply use the skill.

But "Throw" does not trigger global cooldown (GCD), so it's always worth it to do a Throw before anything else. So you would like to make a macro that does Throw + Combo Throw
|
Source code
|
1
2
3
|
/cast Throw
/wait .1
/cast Combo Throw
|
BUT activating two skills with a slow delay quite often does not work correctly. I'm not sure what the reason is but a common workaround is to activate a skill multiple times. So, drawing on the bleedingblak's post (see the link above), your macro would be
|
Source code
|
1
2
3
4
5
6
7
8
9
|
/cast Throw
/wait .1
/cast Throw
/wait .1
/cast Throw
/wait .1
/cast Combo Throw
/wait .1
/cast Combo Throw
|
(again: the idea is just to do Throw + Combo Throw; things are repeated just to make sure that both Throw and CT will be triggered). Note: the bleedingblak's macro in the link does more because it's for R/S: he plays with an xbow&arrows equipped: his macro switches to projectiles, does the T+CT and equips the xbow&arrows back - it's not relevant for R/M).
========
For combo of skills: as a R/M you do the standard R/ rotation: Shadowstab to trigger bleeding, Low Blow to trigger serious wounds and then repeat Wound Attack until you run out of energy. So any DIYCE for R/ will do (although you could also do this by hand, frankly). I believe,
the standard DIYCE2 has R/S part: you can edit it to use for a R/M instead.
I'd do the following:
* get DIYCE (e.g.
from curse)
* take a R/S toon (or create a new one) and test that you can activate the DIYCE and it basically works (you won't have the elites etc. but it's not a problem for testing if it works at all);
You basically make a macro
/run KillSequence()
target a mob and run the macro. You could also do:
/run KillSequence("debugskills")
instead => you should see debug in the chat window. If you are using a not-English client, start it this one time in English (just to test that DIYCE works)
Important: if you can't make it work you'd need to figure out what the problem is => no point starting to edit things if the basic setup does not work.
* get notepad++ (do NOT edit lua with the notepad from windows! esp. if you need some special characters for your language (ń,ę etc.) )
* start editing; always keep a backup; not only the old version, but also every intermediate working version.
I'd assume that the above worked and you were able to activate DIYCE for R/S.
To make a DIYCE for R/M you can do the following:
You will be editing CustomFunctions.lua file. You are interested Rogue/Scout section, i.e. lines from:
--Class: Rogue/Scout
up to
--Class: Rogue/Priest
First, change:
elseif mainClass == "THIEF" and subClass == "RANGER" then
to
elseif mainClass == "THIEF" and subClass == "MAGE" then
=> now this section will be activated for a R/M instead of R/S.
Basically you will only be removing whole lines (so it's easy) or changing skill names to your language.
Remove everything from "--Ammo Check and Equip" to "--Combat" (you might later restore the Potions and Buffs section, but for now let's remove it). Then in the next lines after "Skill2 = " you just:
* remove every skill that you don't have on R/M
* translate the skills you have to your language (carefully, with correct capital letters etc. => the names have to
exactly match the skills)
So, for example, you should remove the line with "Throat Attack"; but keep the line with "Wound Attack", just with the skill in your language.
You need to restart RoM to see the effects.
That's it. If standard DIYCE worked for you for R/S, the edited one should work for R/M.
========
If you meant something different by your question, I'd again suggest that you show us what you have so far.