Some basic rules questions (for my android app)

By vykos2, in Anima: Beyond Fantasy RPG

Hello!

A while ago, I decided to make an Android app for rolling dice and table checkup in Anima. I just threw something together over a night basically, and this is the result: https://market.android.com/details?id=vykos.animaroller

It has a few flaws, but works well enough for us to use it in our games.

My goal, however is to make a more complete version, that takes modifications and such into considerations and I therefore am making a new version from scratch (slowly, time is something I am in short supply of at the moment).

I ran into the folllowing issue though (made a search on the forums, found nothing about it):

Modifers for your fumble level isn't explained in enough detail to make me understand exactly how it should work.

Normal circumstances has it looking like this:

Dice roll | mod

1 | +15

2 | 0

3 | -15

If you obtain mastery, it instead looks like

Dice roll | mod

1 | 0

2 | -15

The problems arise when you throw the advantage "Good luck" or disadvantage "Bad luck" into the mix. The rules say nothing about affecting the mod, so I guess for Good luck without mastery it would look like this:

Dice roll | mod

1 | +15

2 | 0

And with mastery:

Dice roll | mod

1 | 0

or is it the opposite?

Dice roll | mod

1 | 0

2 | -15

and

Dice roll | mod

1 | -15

But what happens with Bad luck?

Dice roll | mod

1 | +15

2 | 0

3 | -15

4 | ?

5 | ?

or

Dice roll | mod

1 | ?

2 | ?

3 | +15

4 | 0

5 | -15

Also, do I assume correct if I assume that mastery (ability > 200) is calculated from the characters unmodified ability score, or is it affected by circumstances? If I have a 201 attack ability and get flanked (ending up with a score of 191), do I still only fumble at 1 and 2 (not 3)?

Thanks for any reply.

Fumbles always start at -15, no matter how wide the range.

Mastery is >= 200. At 200, not 201

Mastery is considered attained when the final value on your sheet is 200, so circumstancial modifiers dont apply.

Also, there is already an anima calculator app for androids

In the books it says "over 200", should I assume that's a translation typo?

And I am aware of the already existing app, but I made a new one since my group wasn't happy with it. And it's not like my app hasn't been there since September, I'm just going to rewrite it ;)

"Fumbles always start at -15, no matter how wide the range."

Except for mastery, which is explicitly changing it to 0.

But the question is what happens after 3? 4 and 5? Do they both give +15 on the roll?


"Mastery is considered attained when the final value on your sheet is 200, so circumstancial modifiers dont apply. "

So, as expected then, thanks.

There are plenty of precise rules that got blurred in the double-translation, we figure them out as we get evidence of them (like mastery at 200). Absolutely not surprising, best to just roll with them as you discover them. Translators aren't necessarily good logicians or mathematicians (no offense intended) and so accuracy is lost if it isn't double-checked by someone who recognizes the differences... as a fellow programmer you are no doubt familiar with situations like to this.

Good luck with your app!

Thanks :)

I am indeed aware of the problem. However my Spanish is crap and I was hoping that by posting, I'd discover that there are people out there that has already looked into these things ;)

Personally, I dig your app. I find it easier to use than the other one out there (though that one is nice too).

Out of curiosity, are you planning on adding any more functionality to it when you redesign it? Specifically, i was wondering if it could record characters and their attack/def so you could just select a vs b after inputting their stats once. I don't know anything about apps or programming them, so maybe that would be really hard. But if not, it would be awesome if you could do something like that.

Either way, I look forward to what's coming next.

Thanks for the kind words.

As for the question:

The whole point with rewriting it from scratch is for making it "right" from the beginning, in order to make it easy to extend with new functionality.

The problem right now is that I'm writing my Master Thesis, while having two jobs, so my time for coding on my app is limited and the progress is slow, but in time it will appear.