Reply to thread

Message

<blockquote data-quote="Kalendraf" data-source="post: 1601068" data-attributes="member: 3433">A rogue in one of my previous 3e campaigns came up with a suggestion for a custom feat to allow trapsensing.&nbsp; I believe he modeled it from either a prestige class or a similar feat he had seen, but changed it slightly to allow him to get it sooner, but without as good a search capability.&nbsp; I agreed to try it and it didn't seem too unbalancing, however its mechanics left something to be desired.IIRC, that version allowed a free check anytime the rogue came within 5' of a trap, but with a small penalty.&nbsp; Unfortunately, it meant that the DM had to continually roll dice whenever he moved, else it easily gave away the existance of a trap nearby.&nbsp; Of course, I would tend to forget rolls more often than I should have, and the dice rolls probably gave away more traps than they should have.&nbsp; When the character died, the feat died with him.Using a static number instead of a roll would eliminate the need for those rolls.&nbsp; The idea didn't dawn on us at the time, probably because it just seemed like traps needed to be rolled for.&nbsp; But now that I understand that searching for traps can use the take 10 or take 20 rules, assigning a static value for that trapsensing ability seems logical.So the question is, if a rogue is moving half-speed, what number should they get?&nbsp; The equivalent of a take 10?&nbsp; That means they'll spot some obious traps, but miss the hard ones unless they take time to search.&nbsp; However, it seems like 10 is too much, since that would be the result of a 1 minute search which is quite a bit different than a half-speed trek thru some squares.</blockquote>

[QUOTE="Kalendraf, post: 1601068, member: 3433"] A rogue in one of my previous 3e campaigns came up with a suggestion for a custom feat to allow trapsensing. I believe he modeled it from either a prestige class or a similar feat he had seen, but changed it slightly to allow him to get it sooner, but without as good a search capability. I agreed to try it and it didn't seem too unbalancing, however its mechanics left something to be desired. IIRC, that version allowed a free check anytime the rogue came within 5' of a trap, but with a small penalty. Unfortunately, it meant that the DM had to continually roll dice whenever he moved, else it easily gave away the existance of a trap nearby. Of course, I would tend to forget rolls more often than I should have, and the dice rolls probably gave away more traps than they should have. When the character died, the feat died with him. Using a static number instead of a roll would eliminate the need for those rolls. The idea didn't dawn on us at the time, probably because it just seemed like traps needed to be rolled for. But now that I understand that searching for traps can use the take 10 or take 20 rules, assigning a static value for that trapsensing ability seems logical. So the question is, if a rogue is moving half-speed, what number should they get? The equivalent of a take 10? That means they'll spot some obious traps, but miss the hard ones unless they take time to search. However, it seems like 10 is too much, since that would be the result of a 1 minute search which is quite a bit different than a half-speed trek thru some squares. [/QUOTE]

Verification