Reply to thread

Message

<blockquote data-quote="Flamestrike" data-source="post: 7134179" data-attributes="member: 6788736">1) An invisible Imp still needs to take the hide action in order to be hidden. It doesn't matter if it's invisible or not - the invisibility just allows it to be stealthy. You should be comparing the Familiars stealth check to the Guards passive perception scores.2) The familiar is evil alignment. While the warlock has a great level of control over it, don't forget its alignment. Have it twist its orders, to lead the warlock astray. Don't let the warlock treat his familiar as just a class feature. You should run it as a non-player character run by the DM with its own agenda, albeit one that the warlock has a great level of control over.3) It takes the warlock one hour to recall his familiar. Time limit your quests so that if the familiar dies, the warlock does not have enough time to summon it back.4) If the warlock continually uses his familiar as a suicide or distraction beast and gets it killed all the time, have his patron step in. The familiar is a gift to the warlock from his patron. The patron could very well recall the familiar if the warlock mistreats it.In my games I impose the loss of one level of exhaustion on the master if a Familiar dies. I find this makes warlocks and other spell casters look after their Familiars a little bit better and not use them as suicide beasts.But otherwise remember the familiar is there to be an scouting machine. The character in your campaign is using the familiar appropriately. Don't be too heavy-handed. But on the other hand don't let one class feature totally dominate your game.</blockquote>

[QUOTE="Flamestrike, post: 7134179, member: 6788736"] 1) An invisible Imp still needs to take the hide action in order to be hidden. It doesn't matter if it's invisible or not - the invisibility just allows it to be stealthy. You should be comparing the Familiars stealth check to the Guards passive perception scores. 2) The familiar is [B]evil[/B] alignment. While the warlock has a great level of control over it, don't forget its alignment. Have it twist its orders, to lead the warlock astray. Don't let the warlock treat his familiar as just a class feature. You should run it as a non-player character run by the DM with its own agenda, albeit one that the warlock has a great level of control over. 3) It takes the warlock one hour to recall his familiar. Time limit your quests so that if the familiar dies, the warlock does not have enough time to summon it back. 4) If the warlock continually uses his familiar as a suicide or distraction beast and gets it killed all the time, have his patron step in. The familiar is a gift to the warlock from his patron. The patron could very well recall the familiar if the warlock mistreats it. In my games I impose the [B]loss of one level of exhaustion [/B]on the master if a Familiar dies. I find this makes warlocks and other spell casters look after their Familiars a little bit better and not use them as suicide beasts. But otherwise remember the familiar is there to be an scouting machine. The character in your campaign is using the familiar appropriately. Don't be too heavy-handed. But on the other hand don't let one class feature totally dominate your game. [/QUOTE]

Verification