Talk:Druid (Evaluational Base Class Layout)/Bots?

From D&D Wiki

Jump to: navigation, search


  • Replaced all the L5s with semicolons bold mark-up (great reduction in ToC).
  • Bumped up all L2s though L4s to the next bigger header. (i.e. What were L2s are now L1s, L3s to L2s, and L4s to L3s.)
  • After taking another look at the new format in Tome of Battle and Dragon Magic, it seems that the Hit Die info in the table captions is centered, not right-justified.

Go here to see previous version. —Sledged (talk) 12:07, 21 March 2007 (MDT)

I'm a little scared to ask, but how are we going to implement all these retroactively? >.> Anyone got an uber-smart bot? Armond 14:32, 21 March 2007 (MDT)
I have built a relatively flexible bot base. If all of the ideas are solidified then I would be willing to implement it. — Blue Dragon (talk) 16:46, 21 March 2007 (MDT)
A bot will not work as basically every class is formatted incorrectly and different from the other incorrectly formatted classes. We are just going to need a lot of help from a lot of people and slowly remove Template:Wikify from each one as it gets done. --Green Dragon 16:57, 21 March 2007 (MDT)
We're going to also need many eyes. I'm pretty good at formatting these things, and after I update a class, sledged or green dragon come behind me and make even more changes. There's just a whole lot of detail to making these classes all come out right and consistently.--Dmilewski 14:19, 22 March 2007 (MDT)
Jeez. Is there a way we can make the finalized information easily available to anyone who visits the wiki, in the hopes that anon editors will be able to make a good sized contribution too? Armond 14:29, 22 March 2007 (MDT)
A good policy might be to start any major work with: can we automate this? Maybe it will require a standardized workflow. Or maybe it will simply add too much complexity. After all, if a wiki becomes to complex, it is not worth editing it anymore. Sorry for being unconstructive.
David Latapie ( | @) — blog 13:56, 10 April 2007 (MDT)
The reason automation will not work in this scenario, at least not be worth the effort, is because virtually every class is formatted differently from all the other classes. Because their are no standards a bot would have a very, very, hard time formatting classes and making a bot that can complete this task would probably take longer than doing it by hand. --Green Dragon 16:33, 10 April 2007 (MDT)
Would a Class Formatting standard make sense (real question?).
David Latapie ( | @) — blog 01:10, 11 April 2007 (MDT)
Most likely, but what would *really* help would be quickly implementing these into the preloads so we don't make our workload any bigger. Armond 08:52, 11 April 2007 (MDT)
My agenda does not leave me time to implement (or even write anything). Out of discussions and tips, my contributions here will mainly be minor edits. I hope you understand.
David Latapie ( | @) — blog 09:09, 11 April 2007 (MDT)
It's best to wait for everything to get finalized first, so we don't have to keep changing the preload. —Sledged (talk) 10:19, 11 April 2007 (MDT)
(indent was previously reset but now is back) Aye, but once we get everything finished the preload will get a huge revision. I was thinking of making sure that new classes don't use the old formatting, thus adding to our workload. Armond 11:12, 11 April 2007 (MDT)
I’d prefer you do not reset it. Maybe Green Dragon could modify the CSS for a smaller indentation
David Latapie ( | @) — blog 11:59, 11 April 2007 (MDT)
Sorry, it's just that once it goes over this far it gets hard to read on lower resolutions (I use 1024×786 or whatever it is; the school computers are set on it and I can't change it) and starts bunching up. Armond 12:13, 11 April 2007 (MDT)
Anyway, I agree. Change new classes if you want however we will wait for this discussion to be done to change the preload and change all the old classes to the new standards. --Green Dragon 16:30, 11 April 2007 (MDT)
Home of user-generated,
homebrew pages!
system ref. documents

admin area
Terms and Conditions for Non-Human Visitors