Reply to thread

Message

<blockquote data-quote="Lanefan" data-source="post: 9524539" data-attributes="member: 29398">Exactly, and I'm just fine with this. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":)" title="Smile&nbsp; &nbsp; :)"&nbsp; data-smilie="1"data-shortname=":)" />It's a choice for them: risk using it now and potentially gain the benefits of doing so, or not use it until after the next downtime if ever.Remove Curse isn't guaranteed to work though...at least not the verion I'm used to.I very rarely if ever do this, if only to keep them from meta-thinking: &quot;Ah, that gives acid resist, we must have an acid trap or a Black Dragon coming up&quot;.But even then, many's the time they had an item carefully stowed away that, if used, could have made a big difference.What's wrong with that?&nbsp; I've always had the combat matrix be fully DM-side info anyway, so they never know what AC they can hit.&nbsp; And so it's &quot;I roll 10 on the die, plus 1 for Strength and 1 for Prayer plus whatever the sword gives me&quot;.&nbsp; Simple as pie.I'm the opposite.&nbsp; In character (!) I once wrote a guide to field-testing magic items which somehow ended up getting fairly wide dissemination in the setting, to the point where &quot;Lanefan's Guide&quot; became the go-to manual for field-testers.An item that identifies itself should be a rare occurrence and can be played for laughs: for example on being wielded (and every time it's wielded henceforth!) a sword might speak in Common: &quot;Hello.&nbsp; I am your plus 2 longsword.&nbsp; Please handle me with care as my blade is very sharp, and do not expose me to extreme heat, cold, or acid as such things may cause loss of enchantment.&nbsp; I prefer to be used against Giants as I am particularly good at slaying such.&nbsp; Enjoy your combat, and have a nice day.&quot;</blockquote>

[QUOTE="Lanefan, post: 9524539, member: 29398"] Exactly, and I'm just fine with this. :) It's a choice for them: risk using it now and potentially gain the benefits of doing so, or not use it until after the next downtime if ever. [I]Remove Curse[/I] isn't guaranteed to work though...at least not the verion I'm used to. I very rarely if ever do this, if only to keep them from meta-thinking: "Ah, that gives acid resist, we must have an acid trap or a Black Dragon coming up". But even then, many's the time they had an item carefully stowed away that, if used, could have made a big difference. What's wrong with that? I've always had the combat matrix be fully DM-side info anyway, so they never know what AC they can hit. And so it's "I roll 10 on the die, plus 1 for Strength and 1 for [I]Prayer [/I]plus whatever the sword gives me". Simple as pie. I'm the opposite. In character (!) I once wrote a guide to field-testing magic items which somehow ended up getting fairly wide dissemination in the setting, to the point where "Lanefan's Guide" became the go-to manual for field-testers. An item that identifies itself should be a rare occurrence and can be played for laughs: for example on being wielded (and [I]every[/I] time it's wielded henceforth!) a sword might speak in Common: "Hello. I am your plus 2 longsword. Please handle me with care as my blade is very sharp, and do not expose me to extreme heat, cold, or acid as such things may cause loss of enchantment. I prefer to be used against Giants as I am particularly good at slaying such. Enjoy your combat, and have a nice day." [/QUOTE]

Verification