Real Numbers: When they're wrong

So, there's a lot of cases where Real Numbers are some combination of "totally useless" or "wrong" or whatever. e.g., the accuracy listed for Rain of Fire in Fire Blast is 2.00, but in fact, the pseudo-pet does not have an accuracy of 2.00, it has a normal accuracy of 1.00. Team Teleport says it's an effect with some radius, and a range of 25 feet, but in fact, the range is closer to 200 feet.

Questions:

1. Are these "bugs"? As in, is it conceivable that people at ncsoft/Paragon would consider a report of such a thing to be a bug report, and possibly fix it?
2. Is there a single canonical list of all the cases where the real numbers are Just Plain Wrong?

i think the 25 feet are for the radius in which all things are teleported to the spot you want to

i'm not sure about the first one involving RoF...but pretty sure the "25' range of team teleport" is stating that teammates must be within 25 feet of the caster for them to be teleported.

Quote:

Originally Posted by Smiling_Joe ::looks at RaikenX's signature:: Something funny.

The accuracy of the fire rain is 2.0 for placing the area of the AoE, but the chance to hit each target is based on a different accuracy. This should be true for most placeable powers.

The range on the teleport is the point blank range of allies who are affected, not the distance you all travel.

If they consider it a bug at all, it is a display bug. But really it's just an artifact caused by having two relevant values that need to be displayed for the same display value.

Hmmm, curious about that...

I'm wondering what powers I have slotted wrong because I see certain powers (Rain of Fire, Ice Storm, etc...) that say acc. of 2.0X and so I'm like, "sweet, no acc. needed!" Hmmm...

That and someone told me about a week ago that the poison trap from the Traps powerset needs Acc in it because the chance for hold has a tohit check against it....I just had it slotted for 3 hold and 3 rchg...

They're not bugs, they're correct info. They just point to a different stat than the one you expect.

Summoning a Rain of Fire upon your enemies has a 2.0x acc modifier, but the rain itself has a base 1.0x acc modifier like most attacks. I believe other people have the Team Teleport example covered.

When you see something that calls a pet, and that accuracy is listed at 2.0, means it is autohit. Not that the pet cannot miss, but that you have 100% chance of placing the pet where you want it to be placed.

The pet has whatever inherent accuracy the pet has. If the power allows accuracy enhancers I try to put in at least 50% points more.

The numbers are right as listed, theyre just confusing to someone who doesnt understand the system.

As others have mentioned, these are valid but fairly meaningless information, come about because of how the powers are implemented. Every power has an accuracy whether it needs to hit something or not, and that's what gets displayed by the system for things like summoned pets. "Patch" powers like rains happen to be, as implementation details, summoned entities just like an Animated Stone or Fire Imp, so we reasonably think of them as attacks and not pets, so displaying the accuracy of the summons is especially confusing.

These are "bugs" in the sense that they're not working as seems sensible to the end users, but not in the sense that they're working as designed. Modifying the Real Numbers info to show us the accuracy of the pet and not the power would require some fairly significant special exception handling for those cases where the power summons something. So that particular example could certainly be improved, but doing so would be an enhancement of the system, rather than a bug fix.

That would be an improvement for most of the patch/rain powers, certainly. I don't know why the summons needs a 2.0 in a stat it doesn't even use in the usual sense.

I think, more broadly for powers where we summon things we properly consider pets, making it 1.0 might just obscure the reality even more. If nothing else, the 2.0 stands out as different and weird, and might get people to question whether it's right. For pets, their accuracy really varies by the powers they activate, so putting a 1.0, which looks like a pretty reasonable accuracy value, might lull people into thinking that reasonable looking value must apply to everything the pets do.

It's a pretty crappy justification of having a weird accuracy number in place, but it's something that came to mind when making my earlier post, and why I didn't make the suggestion you have.

While not a case of the numbers being wrong, Tough and the Defender APP version of Temp Invul claim that both powers give damage resistance against all types. (Which would be cool for Tough, but even I'd admit that 30% out-of-the-box resist to all damage types for one toggle would be a bit hax, even though defenders could need it.)

Quote:

Originally Posted by Samuel_Tow City of Heroes is a game about freedom of expression and variety of experiences far more so than it is about representing any one theme, topic or genre.

I think that's for PvP, it's just not particularly clear in the power description/info.

Many pseudopets are listed as having 2x accuracy, I assume, to make them easier to pinpoint in a spreadsheet. It's not a "bug" per se, it's merely returning an accuracy value which has no bearing on the power and is not of any use to the player. It's technically returning the correct accuracy value, it's just not the one you want.

Quote:

Originally Posted by Luminara The purpose of Real Numbers is to inform players exactly what their powers do. Whether the information is correct for the specific pointer it's referencing is irrelevant, it's a bug because it's not performing the intended function of giving players accurate information on those powers.

I'm not sure I accept that definition of "bug." Technically the system does exactly what it is told to do, accurately. It's not a bug, because it works. It does strictly what it was told to do. It's just that it wasn't told to do the right thing. Maybe it doesn't do what it should do in theory, but it does what it should do insofar as what it was programmed to do.

If I make a program to tell me what color apples are: red or green, and it tells me they're red, it's right. Some apples are green of course, but I only gave it the ability to return one answer. It can't do something I didn't tell it to do.

Quote:

Originally Posted by PRAF68_EU Dispari has more than enough credability, and certainly doesn't need to borrow any from you.

If the program was told to do the wrong thing, that is also a bug.