The problem with PHP is that it is almost impossible to tell what went wrong if you aren't the system's administrator. You can't see the files before PHP has done its magic (okay, no problem here as I know the files very well) and the (error) log is also kept secret. All I can do is describe the symptoms and deduce what might have happened. To give you some hints: If you open up the Cheat Sheet, there are a bunch of links in there to showcase the different filters. Those links point to the "Card and Item Query" tool. If you click such links, the query tool opens and the filter you clicked on gets inserted into the top text-box. This is done by PHP-code working on url-parameters (the "?id=xx&gender=m"-like things) and everything is fine. Another working PHP-code example is the signature badge on the top of each page (the dark gray one with the forum-link). This html-segment is inlined from an XML-file that is available locally. In contrast, all (!) tools that rely on the game server's csv-files aren't working because while loading those pages from your server the PHP-preprocessor is recognizing the PHP-code segments, removes them but replaces them with nothing (instead of the csv-file's content). If the PHP-preprocessor isn't completely messed up, the error log should mention why it wasn't able to load those files from the game's servers (probably a firewall/network issue). And this should be true for every single time someone requests one of the utils' pages, meaning there should be hundreds of errors logged (and you can trigger them yourself by loading the collection analysis for example, such that you know which time-stamp to look for). If the logs are empty perhaps restarting PHP could help. The weird thing here is, that there was a version, where this all worked right. And since then, the tools haven't changed significantly (at least in this aspect). So, if you haven't reconfigured your PHP-environment, I can't tell why this came up (now). At least my PHP-(development-)environment (that hasn't changed since the first time I used it) was able to correctly parse all tools. Otherwise, the non-dev version archive would be broken, too. If everything else fails (and assuming that it is - unfortunately - very unlikely that there will be many new adventures, card and items in the future) you could use the non-dev versions for those that rely on the server files. They are relatively easy to spot because the references to server files are always the last thing in each tool (pm me, if I should provide you a list). Sticking to the dev-versions for the remaining tools would be preferable. But that would also mean that auto-updates aren't possible anymore, sadly.