Nexon's decline in traffic

Additional frame data has zero overhead in the files. Actually, having the frame data stored locally in each img file would be faster than using a link because there's no redirection involved.

Also, adding frame data to one file would not affect seek/read performance of any other file. Of all the things you nark on Nexon for, you choose the WZ format? If anything, the WZ format is the best, most efficient thing Nexon has. Their patch format is also very efficient.

If you want to attack Nexon's bloat, try poor programming practices in the game client. That will bring more bloat much more than additional frame data ever could.

Also, adding more data to the WZ files has very little cost on Nexon's behalf. The only time where it would become an issue to add more data is if you were to approach the 2.1GB mark, and then Windows might poop a brick or two. Considering their largest file is about 900 MB, Nexon has nothing to worry about considering file size.

I was looking at this from the consumer point of view. The only real reason Nexon would care about their Setup file size would be download costs, which they seem to have already taken care of through their sneaky game manager. Thus, we have established the fact that they do not give a chinchilla's ass.

But consumers do care, and from that perspective, the .WZ files are pretty inefficient at doing what they're meant to do, which is host only relevant game data while minimizing file size.