Loop on offline players

[kamilleon]

I want to make that this code works on offline players too: (I want to make a somewhat custom cookie clicked kind of game)

every 1 seconds:
  loop all players:
    if {f2.%loop-player%} is true:
      add 1 to {s.%loop-player%}

 

[Donut]

loop all offline players

However I would not recommend doing this every second. It would be better set a variable to ‘now’ when they leave then when they rejoin check the difference between ‘now’ and the variable. Then you can give them a certain amount of cookies based on this elapsed time.

 

[kamilleon]

loop all offline players

However I would not recommend doing this every second. It would be better set a variable to ‘now’ when they leave then when they rejoin check the difference between ‘now’ and the variable. Then you can give them a certain amount of cookies based on this elapsed time.

Im just started on skript, so i don't really know, how to do that, you know.
I know that much, that a good way of starting a "new language" by creating a minigame or playing with it.

 

[Donut]

Look at the example cooldown.sk that is generated. It’s the same concept. If you deleted it then you can google it and it’ll come up

 

[kamilleon]

Look at the example cooldown.sk that is generated. It’s the same concept. If you deleted it then you can google it and it’ll come up

I have it, but how do i make an offline player time checking contraption from a command cooldown?
[doublepost=1513700241,1513700068][/doublepost]Like do i need to get how many seconds have been bypassed, and give that number of cookies to the player? And if yes, how?

 

[Donut]

look at how they find the elapsed time but instead of checking if the elapsed time is greater than the cooldown length, you can convert it to seconds and give them cookies

 

[kamilleon]

on quit:
  set {_offlinetime} to now

 
on join:
  check the difference between {_offlinetime} and now
  add {_offlinetime} to {s.%player%}

Maybe this would work? (Checking)

 

[Donut]

No. Don’t use local variables (no underscore). Have a variable for each player I.e {time::%player%}. And line 6 isn’t right, look at the cooldown.sk, it’s the same concept but different application

 

[kamilleon]

No. Don’t use local variables (no underscore). Have a variable for each player I.e {time::%player%}. And line 6 isn’t right, look at the cooldown.sk, it’s the same concept but different application

I don't get it.. Sorry..

 

[FinalPlayer024]

I don't get it.. Sorry..

Local variables are "{_test}", variables with an underscore at the start.

So, use a variable like {time.%player%.logout} on player quit, and call it back on player join with "set {_time.hasbeen.offline}" to difference between {time.%player%.logout} and now, then add {_time.hasbeen.offline} to {total.time.offline.%player%}. I don't know if you meant that.. :\

This should be the code

on quit:
  set {time.%player%.logout} to now
  stop
on join:
  set {_time.hasbeen.offline} to difference between {time.%player%.logout} and now
  add {_time.hasbeen.offline} to {total.time.offline.%player%}
  stop

#!Optional:
command /check [<offline player>]:
  trigger:
    send "%arg 1% has been %{total.time.offline.%arg 1%}% minutes/offline." to executor
    stop