<div class="quoteheader"><div class="topslice_quote"><a href="https://elliquiy.com/forums/index.php?topic=283008.msg14037603#msg14037603">Quote from: Lockepick on 31-03-2018, 05:55:28</a></div></div><blockquote class="bbc_standard_quote">There is nothing written about removing the cap, but there previously <em>was</em> no cap (for Vampire Slaves) -- because a normal Vampire doesn't have control over any Vampires they make (only Spawn). That made me read the new text about how Vampires are enslaved until the Master dies as if it was establishing a new rule, and less about transferring the previous Spawn Cap to full Vampire Slaves. <br/><br/>Honestly, I admit it's fuzzy -- I'd respect either decision; I could see the ruling going either way. With the whole generational vampire control work-around/shenanigans anyway -- removing the cap just sort of keeps things more thematic/interesting.<br/></blockquote><div class="quotefooter"><div class="botslice_quote"></div></div><br/>Normal Vampires do control templated vampires they create<br/><br/>"<em>If the vampire instead drains the victim’s Constitution to 0 or lower, the victim returns as a spawn if it had 4 or less HD and as a vampire if it had 5 or more HD. In either case, the new vampire or spawn is under the command of the vampire that created it and remains enslaved until its master’s destruction</em>"<br/><br/>Aside from pointing that out, I just want to say I think the DM(s) should rule on potential hit dice cap based on what they think is best compared to what the template specifically says. As Lockepick points out there is always the generational trick to bypass limits.  So an argument can be made for either way being better.