You cant string rolls together.
Do you always incur cost when using leg sweep? We could modify the the marvel roll or create a marvelc roll which includes the cost calculation.
Printable View
If I'm being honest, I think by the time you've gone to that trouble you already know what the target number for the attack would be. So, while I think the automation would work, because there's another manual step in the process it would actually prolong the resolution of the attack. I really appreciate the idea, but it seems like it wouldn't be worth your while to do that work.
To answer your final question, Karma isn't a must have in the CT (although it's kind of nice to see it at a glance to know which players/characters have that in their pocket for certain things).
Your example will never work because we are referencing [d] and you have put this in [d] but other than that sometimes you have to fully qualify the references like this instead:
[Martial Arts|c]*[Martial Arts|d]+[Ego|a]
Note that this is in the CALC field for [a] and not in [c] or [d]
And this calculation also works
([Martial Arts|c]*[Martial Arts|d]+[Ego|a])/2
I have added a small change to the damage roll in XCore itself - eg not in the Marvel extension.
If you hold SHIFT when rolling it will apply Double damage.
If you hold ALT when rolling it will apply Half damage.
If this is desirable I will roll it out to the other damage rolls.
For the XCore Marvel extension I have added a new roll cmarvel [a]c#
This will deduct # from your n1 field which is useful if you are using n1 as Focus.
Do not use a formula for # just apply the number.
This works. However, there's a small thing where the "big" damage number in the chatbox doesn't reflect that modifier. It does apply the correct amount of damage (double or half) to the target though. Just thought I'd give the feedback, but am THANKFUL for the new implementation.
See attached for an example. Damage dealt was 12 (correct). Note in damage roll indicates the double damage (12), but the larger number (to the right) was erroneously displayed as 6.