Year of the Dragon: Through May 28th, claim free Expansion Pack (excluding Vecna Unleashed) or a Greater Elixir of Discovery! Speak to Xatheral in the Hall of Heroes.edit
Game mechanics • Newbie guide • In development • DDO Store • Social Media
Challenges • Classes • Collectables • Crafting • Enhancements • Epic Destinies • Favor • Feats
Glossary • Items • Maps • Monsters • Places • Quests • Races • Reincarnation • Skills • Spells
Please create an account or log in to build a reputation and unlock more editing privileges, and then visit DDO wiki's IRC Chat/Discord if you need any help!
Template talk:DDOip DC
I create a proposed update to {{DDOip DC}} in the sandbox and posted a demonstration of its use and the new trap DC tables here: Template:DDOip_DC/testcases.
The goal of the redesign was to simplify the process of updating the trap DC pages with a new observation. In the current method, you would have to enter the data in two different locations (the "Modified Roll:Result" and the "Suspected DC range" columns). Not only that but the possible DC range must be manually calculated. I've made the template do this calculation automatically and deleted the second column so all data can be entered in one spot. This should dramatically decrease the chance of simple errors ruining the data. It should also help reduce the number of people who simply leave their observations in the comments instead of actually updating the tables.
My new template has the following features that are upgrades over its predecessor:
1. All parameters are optional. This means the range will display simply and accurately no matter how much or how little information is available.
2. It works for DCs (like disable device) that allow for critical failure and success. If it is possible to critically succeed, a normal success gives both a lower and upper bound for the possible DC and this template accounts for that.
3. It works for DCs (like open lock) that do not allow for critical failure and success. Using the |f= and |s= parameters will accurately determine the range for these types of DCs.
4. For DCs that allow for critical failure and success, the parameters |f= and |s= can still be used to set bounds on the DC without implying that there was an actual non-critical success at that value. For example, if you succeed on a trap with a disable device DC of 40 on Elite, then you can assume that the DC on Hard is 40 or less. However, inputting a success of 40 to the Hard DC using the |sl= parameter will incorrectly set the lower bound of the range to 21. The |s= parameter can be used to avoid this scenario and set the range to ?-40 as it should be.
5. If two observations are input that contradict each other, a red warning message is displayed. This will help prevent mistakes and typos in the data tables.
Since there are very few pages that use this template, I'll just update it if no one is opposed in two days on Saturday (2/15). I would greatly appreciate any feedback or ideas for improvement! :) ⇒ Kkoliver (Contribs • Message • Email) 02:46, February 13, 2020 (EST)