c:sort is not working for me

Welcome! Happy to help on Census questions.

C:sort affects the order of Census search results. It does not affect the contents of returned data. There is no way to reshuffle data within a returned result set. Most folks using Census have taught ourselves some kind of rudimentary programming in PHP, Javascript, VB.NET, etc. so we can shuffle the data around to what we need, and to display it in cool ways.

People have asked me over the years to write a Census-to-Excel tool. There are numerous situations where such a tool would fail. But maybe I should reconsider it. Something about perfect being the enemy of the good.

Quest exports in EQ2 Census were setup so that expansion quests could be hidden/blocked from exporting until a few weeks after that expansion's release. This was a compromise to ensure no "spoilers" or head starts. For example all quests with a filepath (Yes all EQ2 data is in xml files) including "exp14" could be blocked until a few weeks after expansion 14 is released.

For... reasons... when the EQ2 team started working on Kunark Ascending, rather than putting their Epic Weapon 2.0 quests in the appropriate exp13 folder, they put them in the exp08 folder. I alerted Kander that some of these quests were leaking into Census and he flipped his lid. Even though none of us captured this data or did anything with it, he had platform hand-remove the data from Census and had the code side add more rigorous code to block any future quest data from being exported. Eventually there was 1 more export, but that's pretty much it.

Most of the expansion-specific quests of the last 3 years are missing from Census and for EQ2U, with the help of players, we have had to painstakingly recreate this data manually. Extremely frustrating and so unnecessary as quests are usually documented within 2 days of the expansion launch on EQ2 Wikia.

TL;DR: When Epic Weapon 2.0 were in development, some of the quests leaked into Census. Even though we were extremely responsible, destroyed all copies, and reported it immediately to Kander, he flipped out and blocked pretty much all future expansion quest data from being published.