Dungeon Master Forum

Well, I'm not sure whether this could be actually seen as a bug, but anyway: In original FTL-DM it was possible to avoid parts of the trap protecting the diamond edge by throwing the edge down to corridor with the shooters. If I do this in RTC they will be activated thrice. I think this was changed long ago along with the bug that allowed to salvage the powergem. Yet, while being able to carry the powergem up to the dungeon's entrance certainly was a bug, I don't think that being able to partially avoid the diamond edge's trap would also be a bug. So, is it possible to change back the triggers in order to make them only activate, if a character carrying the blade is stepping on them, but not, if the the blade is propelled over them?

I don't regard this as a bug, and the current behaviour is the correct one.

If you think about it, I can't see any physical justification for a trigger not being activated when an item is in full view and flying over the trigger but being activated when its hidden away in the party backpack. If anything it should be the other way around!

Well, I don't agree (depends on what physical mechanism the trigger represents), but then, its a very minor unimportant detail, so never mind.

I like GG's logic here. If you just take the sword and simply keep it out ie equip it or throw it around, surely the dungeon mechanics designed to protect it should "see" the sword. But if you hide it away in your pack and walk away casually (we all know what happens when you run) then maybe you could get away with it.

Either way, if you don't like it, change it, that's what the editor is for.

I believe the opbys were improved so that you could have the old DM 'throwing item over is fine, walking over not' or the new RTC 'over or on' However, sicne the throwing of the firestaff was an unforseen bug, you have to assume the diamond edge was too, so RTC doens't allow it and has 'over/on'

Sure I COULD change that in the dungeon.txt. But I wouldn't pay the price to become incompatible to the gHoF for such a minor detail. For a major issue like being able to manually set the difficulty level I would accept that, but not for a single, irrelevant trap.