Bonded Mounts aren't created properly

Description

Steps to reproduce:

  1. Create a paladin

  2. Update paladin to level 5.

  3. Add Divine Bond - Special Mount

  4. Add a special mount - Choose Horse

     

  5. Click Switch to Companion

  6. The Companion Race is shown red (as well as all the other ones, and some completely illogical ones that were not even presented).

     

  7. Switch to Race -> Select Companion (Horse) .. it's red in the right top panel.

You can never add more levels as the companion class doesn’t appear in the class list.

 

Same as this one you closed:
https://pcgenorg.atlassian.net/browse/HELP-160?focusedCommentId=49209

Environment

Windows 10

Activity

Show:
Andrew Maitland
August 30, 2020, 10:09 AM

Hi, the companion races are not selectable because they fall outside the norms for the animals (Often are weaker variants that get promoted when the master hits the level 4 or 7 milestone). This was intentional. The race is already added by the Companion selection tab, which makes that is a non-issue.

Regarding adding levels - You only level up the master and the companion will level up correctly at the appointed levels. This keeps the animal companion / bonded animal rules correct in this regard. If you could add levels manually, you’d miss out on the class granted perks for the correct levels.

The companion group covers all companions - druids, rangers, and paladins plus the multitude of archetypes. The selection box shows what your character was qualified to take.

Mount should have 2 HD +3 Companion levels = 5 HD by a 5th level Paladin (Assuming no archetypes altering anything)

Is there actually an issue with the mount not being rules legal that needs to be addressed?



Cethrie
September 1, 2020, 2:30 PM

Hi,

I’m not sure you’ve answered my question:

Why even following all the things you have said is it marked red when I switched to the companion? Are you suggesting its fine don’t worry about it, that was all intentional?

 

No not that I can see, it’s just a very confusing interface as usually if the interface marks it as red something is wrong. It’s also confusing since there are other companions that are not marked in red.

Andrew Maitland
September 2, 2020, 8:50 AM

Hmm, yeah, it’s intentional. I can make it so the race won’t appear as red once you get it. That would make it less confusing I think. The purpose was to prevent GMs from grabbing less powered races for encounters that are coded specifically to be companions. (Come to think on it, I suppose we could alter the base race to work, but companion progression is an oddball thing).

 

I’ll see if I can standardize the interface to avoid the confusion. But if everything is coming out correctly, that’s the most important thing.

Cethrie
September 11, 2020, 6:52 AM

Thank you for your answer.

I would suggest the following in terms of the interface. Lock pretty much everything the software will take care of and make sure it isn’t red.

This ensures the behavior you want is maintained. Also helps avoid confusion (but again due to the nature of the interface I can see how it might not occur to people why everything is locked from their control).

It might also be good if there was something that linked it back to the existence of the “master”.

Assignee

Andrew Maitland

Reporter

Cethrie

Labels

None

Source Books

PF - Core Rule Book

Epic/Theme

None

Pending User Input

Yes

Components

Affects versions

Priority

Minor
Configure