Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
I collected about a week's worth of lobby data, at one second intervals. What things would you find useful in it (as a trend or something else)? I'm considering graphing it and showing the interesting things that you say. I'm not exactly sure why I'm doing this, I guess it's an interesting project.
I will use your responses in EE Analytics to find out what most people want in the data, and try to make graphs and dynamic charts that graph similar things in worlds.
Offline
Well, I'm going to be starting an EEIndex project to index as many worlds and users in the game as possible. I might find a way to keep the data in such a way that it can be used for statistics but it'll mostly be for world and user search.
Offline
I do like to see the average timespan each world is online for, and maybe categorize them into worlds that reach e.g. 10+ people and those that don't. I believe there is a magic number after which worlds tend to sustain their population.
Data about open worlds would also be interesting.
Oh and:
at one second intervals.
You could be querying every minute too, it wouldn't make a lot of difference. Don't spam the servers <3, I'm pretty sure ours couldn't handle 10 bots running like that
I have never thought of programming for reputation and honor. What I have in my heart must come out. That is the reason why I code.
Offline
You could be querying every minute too, it wouldn't make a lot of difference. Don't spam the servers <3, I'm pretty sure ours couldn't handle 10 bots running like that
Don't worry about spamming servers, they can handle 166+ events/s for hundreds of users, meaning that almost 16,000 events are sent per second. Every minute would probably be fine (would be lower CPU which is nice), but 15 minutes worth of secondly data can be compressed using some fancy stuff to be around 20kb.
Offline
[ Started around 1732491596.2151 - Generated in 0.043 seconds, 13 queries executed - Memory usage: 1.4 MiB (Peak: 1.5 MiB) ]