Talk:Chronomancer (5e Class)

Canidate for Deletion

If an user is actively working on an article, should {{delete}} be on it for this article's reasons? BigShotFancyMan (talk) 07:50, 4 September 2018 (MDT)

I for one don't think it should be deleted if it's actually being improved on. Quincy (talk) 07:51, 4 September 2018 (MDT)

I agree. That seems to defeat the purpose of the template. This appears to be consensus, so I've taken the liberty of removing it. - Guy 08:48, 4 September 2018 (MDT)

If an article is actively being worked on, then {{delete}} should be removed from the page. The consensus we have reached is that new, or WIP pages should not be candidates for deletion. --Green Dragon (talk) 08:54, 4 September 2018 (MDT)

Fixes, changes, and possible suggestions

I've linked every spell to their rightful spell page[] and revised abilities, is there anything that you guy's suggest? --Bigdad881 (talk) 22:57, 4 September 2018 (MDT)

In regards to spells, you should be listing the names of spells instead of copying them here and the links should look like this "Halt (5e Spell)" instead of like this "". Which is written like this "[[Halt (5e Spell)]]" instead of like this "[https://www.dandwiki.com/wiki/Halt_(5e_spell)]". On a more general note, there are still a lot of issues here that mostly can be addressed by reading through the 5e_Class_Design_Guide and checking off the various do's and don'ts as well as constantly comparing the class to the first parties is the way to go. However, I will point out that there still is a lack of clarity, the random capitalizations, and the incorrect title headers. See the ToC on the Pyromancer (5e Class) page for an idea of what the headers should look like and the Help:When to Italicize and Capitalize for the capitalization errors. —ConcealedLight

(talk) 00:44, 5 September 2018 (MDT)

thanks for the advice, I tried implementing a spell table but can't figure out how to imbed it into the topside version of it so I went with the long way version of creating it below, and had followed your advice on making the words hyper links, I also tried to create hyperlinks for which subclass allows choices, but I couldn't figure it out as you can tell x.x' --Bigdad881 (talk) 01:08, 12 September 2018 (MDT)

I don't really deal with classes that much, but I was wondering: Can you replace the spell lists with a phrase somewhere along the lines of "You can also cast spells from the cleric, paladin, etc. spell list"? As of right now those spell lists take up about 80% of the page. Coaldstone (talk) 10:36, 31 October 2018 (MDT)

You can and this normally goes in the spellcasting feature. Though, I'd recommend adding an "as well as the following spells..." afterward. Not sure why this class would be able to use divine magic though :thinking: —ConcealedLight

(talk) 22:04, 1 November 2018 (MDT)

Hello guys, this is my first time trying to edit here, but I do see numerous problems with this class. I am currently using it for a session actually, because the DM and I thought it was a lot of fun, but we have made many edits to things and done balance changes. Time stop, for one, is a very broken feature, and I think we found some very reasonable balance changes for this page. The ordering of spell unlocks and the balance work definitely needs some help, and a lot of wording on spells was really bad for awhile. All together, this is a very cool class, and I would love to make some changes with my current DM so more people can try and play it! Also, sorry if I didn't format or put this comment in the wrong spot, I just wanted to help out. Thank you! -Fellow Chronomancer Player. --Armo27 (talk) 16:30, 7 May 2019 (MDT)

gollark: Unless I can just get the "stack depth" or something somehow.

gollark: I could make the code-using ones check if they're going to *directly* recurse. But mutual recursion is not really fixable.

gollark: So how can metagollarious recursion be prevented?

gollark: Technically, not tail recursion.

gollark: ```schemeWarning: "exit" called while processing on-exit tasksError: uncaught exception: #<condition: (user-interrupt)> Call history: <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <eval> [metagollariosity] (z y x z) <--```How exciting.

This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.