I have 3 quests that I'm working on. One of them stopped working completely a while back and I couldn't find the problem. It was still on an early stage so I decided to delete it and start it from scratch. Soon into the process, the new quest stopped working too. At that point, I realized that, by deleting one alias, it would work again. I still didn't know why this was happening, but I started working on other things that didn't need that alias until I figured it out. Well, today, all the quests stopped working completely and the actors have no dialog. I deleted most alias from the new quest and I even set it to start disabled. Nothing's changing.

A while ago, when I first started having problems, I read http://www.creationkit.com/Quest_Debugging on the wiki. I changed those files but there's no WarningsQuest.txt file anywhere on my pc.

I really need help to figure this out. Either a guess so I can try something out or just general advice on how to debug quests because I feel like I don't have any tools to do so other than trial and error.

The most common reason for quests not starting is that their aliases are not being filled. If a single non-optional alias is not filled, the quest will not start. So I suggest you make all the aliases optional to start with, and see if that fixes your problem.

I think this may be related to the dialogue bug which is being discussed. Don't do anything too radical but try a save and load with your .esp enabled (it worked for me but is not 100% reliable)

I didn't think it sounded like the Dialog Bug (upgraded now to Quest Bug), but I agree with 300dpi and should at least be aware of it: http://www.gamesas.com/index.php?showtopic=1399783

That'll come in handy, much easier than deleting the aliases as I've been doing. I'll try that but what I'm experiencing is no dialogs in all quests, after working on just one.

Saving the game and loading did indeed enable all dialog again. (I've been doing coc from the main menu)

This is also probably the first time I tested it after the patch was applied so it seems very likely that's the problem.

I missed that thread. I'll follow it now, I'm convinced I'm in the same boat.