Author Topic: User Content alpha  (Read 29465 times)

I already said there was no difference starfish



As much of a jackassand moronBlocki is, I'm wrong.
Stop randomly trying to insult me and just tell why you think I'm stupid

I apologize for randomly insulting you.
« Last Edit: June 26, 2012, 02:14:52 PM by Electrk »

I also apologize for randomly insulting you.
Thank you

bump

Anyway, Link not working ;c

Well this is nice, the link has stopped working.


Setting the read-only flag on files could cause the Blockland Launcher to horribly crash and burn. It doesn't...
...but Badspot has himself said he might make the Launcher just not start Blockland if it finds read-only files.

On the other hand, this COPIES the files AFTER the game has already launched.
(However, I believe this still slows down the launch process because it has to re-download the changed files.)

(However, I believe this still slows down the launch process because it has to re-download the changed files.)
Does it?

Wouldn't the original files be stored in cache.db?

I don't think so, but the downloader downloads any incorrect or missing files. As a result, the files you change, which become incorrect from the Launcher's point of view, get updated each and every launch.

EDIT: As I understand it, the cache is a list of files and their sizes, and possibly their CRC. However, I don't think it actually has every file saved in it.

I don't think so, but the downloader downloads any incorrect or missing files. As a result, the files you change, which become incorrect from the Launcher's point of view, get updated each and every launch.
That seems a bit counter-intuitive. Why would it re-download files and add them to the cache when those files are correct to replace the ones that aren't correct which aren't in the cache?

Actually, I believe you're right, because the cache is ridiculously large. (76.2% of my entire Blockland folder.)

Of course, it might also just be to hold models and sounds downloaded from servers.

Actually, I believe you're right, because the cache is ridiculously large. (76.2% of my entire Blockland folder.)

Of course, it might also just be to hold models and sounds downloaded from servers.
Pretty sure it does all that.

The cache contains the downloaded contents but it still causes every file to be rewritten, while the read-only trick pretty much has no cons.

The cache contains the downloaded contents but it still causes every file to be rewritten, while the read-only trick pretty much has no cons.

Setting the read-only flag on files could cause the Blockland Launcher to horribly crash and burn. It doesn't...
...but Badspot has himself said he might make the Launcher just not start Blockland if it finds read-only files.


:/


:/
If that happens then just use a custom launcher instead. Problem solved.