I was confused as to why they started at 30, until I found another great Shared Object reference on SourceForge - which showed that 30 in ascii is "0". All of the array indexes are written in this format 00 01 30, 00 01 31, 00 01 32 etc. This shows the number of tracks you have got saved. (just one here in this case): 4 bytes. All Line Rider files are the same up to this point.
The list of tracks is called the "trackList".
'trackList' - the root object name : 9 bytes The data block has the file name - in our case "undefined" (nice naming work there :)Ġ0 09 // Length of the root object name : 2 bytes 'undefined' - the name of the shared object : 9 bytes The header is standard to all Shared Object files.Ġ0 09 // Length of Shared object name : 2 bytes Heres what I got:Ġ0 00 00 BF // Files size: 4 bytes (from after this byte)ĥ4 43 53 4F // Ascii - 'TCSO' - Filetype : 4 bytesĠ0 04 00 00 00 00 // Always these 6 bytes The rest was just drawing lines, and seeing the effect it had on the file. sol file format on SourceForge which helped a lot. After changing a few of the values I noticed that I did indeed make a line move, so further investigation would be required. I opened this file up in a hex editor and started poking around. "undefined.sol" contains all your Line Rider tracks. The directory will contain a file called "undefined.sol". It will vary depending from what web site you loaded Line Rider flash file. On Windows, Shared Objects are stored under the \documents and settings\username\Application Data\Macromedia\Flash Player\#SharedObjects directory. Line Rider stores its track data using a Flash Shared Object. I chose this one because there is supposed to be a new version of Line Rider due out very soon - once this happens this information will be totally useless, instead of just mostly useless. The Line Rider File Format is the first such post. In an effort to get some more posts happening around here I've decided to unleash a few of these 1/2 finished projects. I mostly figured it out - but owing to my extremely short attention span it quickly entered my immense "1/2 finished projects" repository. The idea was to add a much required "erase" function. You can see how using the correct line through a curve has a big impact on how well you are able to negotiate the curve.A while back I tried to "reverse-engineer" the Line Rider shared object - the file that stores your Line Rider Tracks. The later turn in allows the rider to apex the corner later, putting them in a much straighter line through the curve and in a much better position at the end of the curve. Rider 2 approaches the corner with more confidence and has a later turn in. Rider 2 is a MCrider subscriber and has been practing his motorcycle skills. Because of their nervousness about the corner they begin their turn in early thinking this will give them plenty of time to get through the corner.īecause they turn in early they also reach the apex early causing them to either run wide on the exit or substantially increase their lean angle to get through the corner without crossing the center line. Rider 1 approaches the corner a bit nervous and they they want to make sure they get through the corner successfully. Where you reach the apex of the corner has a big impact on your success in the corner. There are 4 main benefits of using the appropriate line: Outside: The rider finishes the curve on the outside of the lane Inside: The rider then turns to the inside of the lane at the apex of the curve, or the point at which they are closest to the inside of the lane. This gives the rider starting on the outside of the curve a visual advantage because the can see further through the curve. Outside: To follow the basic cornering line a motorcyclist begins the curve from the outside of the lane.
The basic cornering line – Outside – Inside -Outside Riding a narrow, single-track vehicle means we are able to select the left, center or right positions within the lane. A “ cornering line” is the path you follow around a corner.