Lan Dropbox Multiplayer.

[RippeR7420]

So, I have sort of gotten it to work. But the major issue I ran into is this, your "Data.file" only refreshes when you close the game on of the computers. So, If Comp. A was playing the game, Comp. B wouldn't get the update until Comp. A closed GE. Is there a way to make your "Data.file" constantly refresh without having to close GE?

[RippeR7420]

I guess what my question is, is would I be able to use the "fopen" function to save the "data.file" file and reopen it contiouslly? I have two .ged's, one for the "server" and the other for the "client". I know this way won't work for online multiplayer, but I just want to see if GE and DropBox can do this together.

[savvy]

Repeatedly? no,
say dropbox is uploading the file... 50% complete
you save to it again.
dropbox re-starts the upload at 0% again.

(or am i not getting your point?)

savvy

[Fojam]

I think its because the file is in use by a program already so it cant be edited

[RippeR7420]

Ahh both of your answers are helpful +1

But is the "data.file" really always in use? or just when you Save a Variable? the size is under 500 kb also.

[savvy]

When you save a variable, dropbox has to realise the file has changed, upload it to the website and verify stuff.
This is why it takes some time before it even starts uploading, miniscule time in reality... but for gaming or dropbox 'LAN' type stuff as you called it (xD) it is an obvious gap.

savvy

PS: When nothing is being changed in the file, it does not upload at all.

[RippeR7420]

Ya I wish GE had online(or LAN) capabilities! But, oh well. Hopefully soon!

[savvy]

Hopefully! would be very cool.

[Game A Gogo]

me and lcl already attempted in creating a multiplayer game through dropbox.

We were using a different kind of method to write the files so when dropbox needs to save to them or upload from them, the file would be considered unused.

Even with that put aside, we had problems. We kept having duplicates of our files, because we were trying to save while dropbox was loading it.

Later on, Savvy figured out that the least amount of time for sending and receiving frequency is 20 seconds... think about it, 20000ms ping. And yet, there was still some information lost