BlockGardens wrote:

This is actually possible, you just have a limit. Let's say the limit is 256, to simplify things. There must be one variable, called “tick”. If all 256 slots are full, it should look something like this.
0001011101101010101… and so on.
What we need is to be able to keep track of all of the digits at once. Your tick should be changing from 0 to 1 every 0.1 seconds, and there can be 256 clones to keep track of their individual tick. (I'd tell you how to use CloneID, but i'm assuming you're not a noob.)
They should wait 3 times, and check if all times are the same. They wait 0.1 seconds each time (obviously), so it should take 0.3 seconds to delete a player if they're inactive.
For example, if their recording is 000 or 111, that player is inactive and can be kicked out. But if it's 001 or 110 or 010 or such, that player can be ignored for now.
This is just a quick summary of how it works. Actually doing it would be considerably harder.
To measure the number of players, that's easy, just do length(allTicks).

DerpyHead0 wrote:

BlockGardens wrote:

This is actually possible, you just have a limit. Let's say the limit is 256, to simplify things. There must be one variable, called “tick”. If all 256 slots are full, it should look something like this.
0001011101101010101… and so on.
What we need is to be able to keep track of all of the digits at once. Your tick should be changing from 0 to 1 every 0.1 seconds, and there can be 256 clones to keep track of their individual tick. (I'd tell you how to use CloneID, but i'm assuming you're not a noob.)
They should wait 3 times, and check if all times are the same. They wait 0.1 seconds each time (obviously), so it should take 0.3 seconds to delete a player if they're inactive.
For example, if their recording is 000 or 111, that player is inactive and can be kicked out. But if it's 001 or 110 or 010 or such, that player can be ignored for now.
This is just a quick summary of how it works. Actually doing it would be considerably harder.
To measure the number of players, that's easy, just do length(allTicks).

that acutally doesn't work, because online players set the ENTIRE variable. so if someone that has bad internet joins, they'll keep overwriting the cloud variable with old data (which means overwriting everyone's ticks) and stop the ticks from working properly.

also, 256 clones just sitting in the background isn't a good idea, that would cause tons of unneccecary lag and leaves less room in the project for other clones.

BlockGardens wrote:

Maybe we can use Translate and forbid anyone with bad internet from joining?

_THEBOSS_7 wrote:

guess its not as simple as i thought…. clones are no problem for me, lag sure, but i am not using clones.

_THEBOSS_7 wrote:

whitelists only stop certain words, this ONLY allows words in the list, so it is not technically an open chat.

diggy5555 wrote:

um my game isn't working and i don't have much experience with online games game issue

DerpyHead0 wrote:

BlockGardens wrote:

Maybe we can use Translate and forbid anyone with bad internet from joining?

it would be almost impossible to check if someone is messing up other players ticks, and if this means preventing people from playing the game properly, it's a really bad idea.

_THEBOSS_7 wrote:

guess its not as simple as i thought…. clones are no problem for me, lag sure, but i am not using clones.

lag can prevent a lot of people with worse computers from playing the game, and again, preventing people from playing the game properly is a terrible idea.

what do you even need this online counter for? is it acutally important for the game, is the game multiplayer, or is it just something cool? because if it's not needed i don't think it's worth adding, if it's just some counter to try and show how popular the game is, there's lots of other things you can do, like a top score list, a counter for players that have beaten the game, etc.

when green flag clicked
change(☁ players)by (1)