Witch Familiar missing familiar alertness active option


A wizard familiar gives the choice for applying the alertness feat to the wizard, which adds to perception skill. The Witch Familiar should apply the same rule.

Issue will only be present if another class does not use the standard Familiar Grantor ability, and instead has it's own Familiar Granted List.




Andrew Maitland
September 15, 2016, 2:46 AM

I just want to let you know, using open-ended statements make your reports "moving targets". While it may be true, any other class granting a familiar may have the same issue, leaving it open-ended means the volunteer cannot close this issue until they have investigated each instance of a familiar. I'm pretty sure you don't intend to have a volunteer look through the entire database looking for an issue that may or may not exist.

Please keep your reports factual, and on a single issue. It really makes it easier for the volunteers when they have a clear target to fix.

Andrew Maitland
September 15, 2016, 2:50 AM

Witch's Familiar now includes the TYPE:Familiar that triggers the Within Arms Reach/Not Within Arms Reach – Alertness grantor pool..

September 15, 2016, 11:00 PM

No problem, I will always assume the assignee will consider if the issue is part of a more general problem and fix accordingly. The more open-ended statement was to alert the assignee to this and if necessary change the description once it was investigated.

Andrew Maitland
September 16, 2016, 3:09 AM

The problem lies in the assumption said assignee wants to take on that
responsibility. Open-ended tasks are daunting to new volunteers. I don't
know if you've taken a look at the sheer amount of files in the data
folder, but unless you've been around the project a long time, just
finding a single problem can be a daunting task. If the report is a
multiple problem, then you're telling the volunteer that this issue
requires a senior developer to handle. When the number of volunteers
that fit that description is maybe five, and most of them are not very
active, you're shooting yourself in the foot. You're at the mercy of one
volunteer deciding to spend time "investigating" an issue. Which is why
this single experienced senior developer is telling you not to shoot
yourself in the foot. Keep the report factual and specific. Let the
assignee investigate or not if they choose to do so. I'd rather see
three factual reports - "Familiar Alertness not working for Class x";
etc. then one "Familiars alertness isn't being granted to class 1, and
maybe everything else" report. Bitesize reports get fixed much faster.
Report what you want fixed is what it boils down to.

And even as a senior developer, the "you'll have to investigate" reports
are ones I leave til last because they can take 5 minutes, or several
hours, and I don't normally have several hours to give in a single sitting.



Andrew Maitland





Source Books

PF - Advanced Class Guide



Pending User Input



Fix versions

Affects versions