Ah i see. Yes this could be done but the only way to actually do it is the way i explained earlier with the quest data binaries and it is very complex.
This is what you get when you believe people who aren't from here
There are no bugged quests or dungeons that i know of and i have personally done almost all of them (recently too). The person that told you this clearly doesn't understand what causes the error and therefore doesn't understand the server and client enc data relationship so they probably aren't the best people to be taking advice from.
Whenever you touch a warp or an NPC your client looks in it's enc file data for the destination location of the warp or the NPC text for your quest. It also asks the gameserver to verify these entry numbers against the copy of this data the server files have. If they don't match, exactly, then you d/c. It's a method of protecting the client data against being hacked.
Each different cabal client (EU/US etc) has slightly different variations of this data and obviously different versions where things were changed around, item prices, quest rewards and stuff like that. A good example is the quest text for b1f, the entries for the text are completely different between the US and EU enc files of the same date. It works but all of the text is completely in the wrong order even though you are using the exact same entries.
Because of this the server data must be aligned to match the enc data exactly as we can't actually edit enc files. Because of the variations in the enc files you can't use just any old set you have to use a set that the server has been aligned to so you don't get the d/c errors. The current recommended set is the patch (both server and client) posted by Lost-Spirit in the releases section recently.
:
