Wouldn't think so, the data root is actually read-only (it's inside an ISO image, and mounted on the fly, but still read only) The problem is that the data directory is expected to be in /usr/share/0ad/data, which doesn't exist, as the data directory will be inside /tmp/some_random_mountpoint/usr/share/0ad/data, or ../share/0ad/data, relative to the usr/bin directory from where 0ad is launched. However it's is not a huge issue, a simple sed hack on the 0ad binary fixes the problem. I think the only possible problem would be that, besides not being very elegant, it does change the binary md5, which in some games is used as an anticheat method AFAIK.