QUOTE(kyleh613 @ Jun 26 2010, 07:20 PM)

Node21 helps people steal work that costs millions of dollars, hundreds of man hours, and years to develop. He does not get to complain about a leak that quickly disappeared.
This isn't true. My unlock code was never very good. People were getting their content elsewhere. xm360 just helped them manage it. There's no such thing as a leak that quickly disappears. Have you ever tried getting the toothpaste back in the tube? It was merely broken trust. People who didn't want to be trusted didn't have to donate, simple as that.
Anyway, 1.8 seems to be wrapped. I'll try to get it out tomorrow.
Features:
* Fixed fact that you couldn't sort by ratings or raters in the collection manager
* Fixed new scraper (1.7b) getting ratings wrong. I made a change to the file format that breaks compatibility with old xbla_titles.csv, so make sure you are not using an old version of the file.
* Fixed initial scan crashing the 360 if there was no existing content.bin file.
* xm360_server is now aware of the last time xbla_titles.csv and dlc_titles.csv were generated. Every 360 that connects to xm360_server will *automatically* update the xbla_titles.csv and dlc_titles.csv on that 360. Furthermore, you can regenerate, or replace those files without stopping xm360_server from running. So, I leave the server running all the time, 24/7. I have scheduled a /X and a /D every night at midnight as well. It's all invisible without any hands on maintenance. Basically, this feature means you shouldn't ever have to worry about moving these files to your 360 anymore. On the server, these files should be in the same place as content.bin.
* Also, if you put an xm360.xex in that same directory, xm360 will *also* update itself if the version there is newer than the version that is running. It will automatically restart if this happens. This is a moot feature though, unfortunately.
-node