possible rounding error in STR END calculations

[msteele]

I am not sure if this is an error or just a quirk of the rounding rules. Try the following: Buy a 15 STR in the Characteristics tab. END is calculated as 1. Then, buy 25 STR as a Power, END is calculated as 2. The total STR value shows as 40, but END cost shows as 3. Should the END cost on the total actually be 4? Or is this just how combining Characteristics is supposed to work?

[Killer Shrike]

Rounding occurs at each point.

So your base STR rounds to 1 END cost and the Power rounds to 2 END Cost which are then added for 3 END Cost.

[msteele]

Yeah, I get that about the rounding. I guess my question was whether that was the expected way for it to work, particularly since the added STR doesn't have any limitations or conditions attached. It's not a big deal, of course. Just a curiosity.

[Killer Shrike]

Originally posted by msteele
Yeah, I get that about the rounding. I guess my question was whether that was the expected way for it to work, particularly since the added STR doesn't have any limitations or conditions attached. It's not a big deal, of course. Just a curiosity.

Well, if its not modified, then there is no reason to buy it as a Power other than to "beat the system", getting around NCM.

AFAIK the rounding operates that way by design.

[msteele]

Generally, there isn't a reason to do it that way. In the case where I encountered, I was experimenting with a package deal and it was more a matter of illustration than anything else. Beating the system doesn't particularly interest me.

[Killer Shrike]

Originally posted by msteele
Generally, there isn't a reason to do it that way. In the case where I encountered, I was experimenting with a package deal and it was more a matter of illustration than anything else. Beating the system doesn't particularly interest me.

Didnt mean to suggest it did; I was just pointing out that there is no real legitimate reason to do it that way in the first place.

As far as Package Deals are concerned, for "career" or "profession" type packages consider using the Save As Template/Create New Character From Template behaviour.

Do you pkg deal as a character straight up, then save it as a Template. When you create a character from that template, voila, they have everthing the package offers.

[Simon]

Every purchase is rounded separately, in accordance with the rules of the system.

As KS said, there's better, more elegant ways to handle a package deal than to purchase characteristics as Powers. A Characteristic Power is different from a Characteristic (different rules, different purchase mechanism, etc)

[msteele]

Thanks to both of you for your responses, I'll give the template business a go.