Wrong Flameskull Passive Perception

Hi, in the compendium Flameskull has 10 "passive_wisdom" (perception) instead of 12, and 0 "perception_bonus" instead of 2. Maybe an error? I'm checking Monster Manual and the web and it says 12 (10 + 2).

Where are you seeing this? My compendium lookup shows 12. If you have an old or edited copy in your game already, dragging in a fresh one from the compendium won't overwrite it (this protects you from overwriting homebrew). If you click the entry in the Compendium tab or the web page you should see 12. If you want to replace your copy with a correct one, delete (or rename) all instances of it in your game before dragging in the new one.

Monster dragged into game, from Lost Mines of Phandelver, just purchased. Look at the 3rd bar. Thank you.

The issue is with the passive_wisdom attribute, not the text listed in the npc_senses attribute. If you select the flameskull and run @{selected|passive_wisdom}, it returns a 10 as Luke85 mentioned. I tried it with another npc sheet that is trained in Perception (a Behir). The same thing is happening. So, it would appear that npc sheets don't account for proficiency bonus to passive_wisdom. PC sheets seem to update the attribute correctly. Maybe the sheetworkers behave differently for pc/npc sheets? It looks like the {npc_perception} attribute is correct, so I would suggest using [[@{selected|npc_perception}+10]] for your npc macros.   EDIT - we cross-posted. I see that you are using linked bars, so the inline roll I suggested won't work. If you are just using bar 3 for quick reference, I guess you would have to just use npc_perception and add the 10 in your head.

Gotcha. I understand the issue better. I never use that attribute so I didn't even think about the fact that it is elsewhere than on the displayed statblock. Best thing for a small compendium correction is to file a  Help Center Request . Be sure to explain it fully, so the person on the other end doesn't make the same silly assumption I did. Typos and minor compendium errors are logged and ticketed. When a dev can get to them, they will likely do a sweep of any outstanding issues and catch it then. Have you noticed if this is endemic to the compendium, or is the Flameskull an outlier?

Looks like a widespread issue for proficient npcs. I checked a Behir, a Drow, and a Drow Priestess of Lloth in addition to the OP Flameskull. None have proficiency bonus added to passive_wisdom but their npc_perception is correct. Their passive_wisodm only includes wisdom bonus (incorrect), while npc_perception includes wisdom bonus plus proficiency bonus (correct). Checked a PC sheet (proficient in perception). Both passive_wisdom and perception_bonus attributes correctly include wisdom bonus and proficiency bonus. Note that 5e sheet is weird with pc & npc attribute names, which makes this comparison more confusing :/ 

Yes, it seems that this bug affects all creatures. I just tried with a random one, a dire wolf. It must have passive perception +13, but in token it's just +1 (12 WIS + proficency). It's annoying because it's very useful to link scores to token, to see them immediately without opening dozens of notes. Flameskull is from from LMoP but is in Monster Manual too; dire wolf is in player's handbook, it doesn't even appear in LMoP, but it's bugged anyway. So I don't think is a single-compendium problem. I will open a ticket in the help center request. Thank you.

Done. By the way, the same problem was discussed 3 years ago; I now found this:&nbsp; <a href="https://app.roll20.net/forum/post/7073251/how-do-i-put-passive-perception-in-one-of-my-tokens-bar-attribute" rel="nofollow">https://app.roll20.net/forum/post/7073251/how-do-i-put-passive-perception-in-one-of-my-tokens-bar-attribute</a> I see you, keithcurtis, in that topic :-) And I see the dev answer: there is not passive perception score meant to be used from NPC. I find this answer really disappointing. Why expose "passive_wisdom" and not also "passive_percetion", among al those scores? It's very useful so see it with a single glance for a token, instead of open it's note each time... :-(

Ha! I'm lucky if my memory goes back to "earlier this morning", let alone three years ago. Nevertheless, I should have thought of that, since I do now remember that the attributes are different, and I understand why. I've had to deal with it in several threads involving reporting the attribute in chat menus and such. I do agree that it would be a handy attribute to have mechanically available on all NPCs, given how it is used in the game. An API script could transcribe it, but that doesn't help most people.

They answered! They "were able to confirm this bug"... it's a promising beginning :-) Here's the answer:

I also posted as suggestion&nbsp; here , waiting to get 10 votes (it still works like that?).

I threw in a vote, even though I know that it probably doesn't need one, given that it is already on the backlog.