Removing leavers/afks Trigger Question

[AImentality]

Is it possible to have a trigger that removes a player if they have been standing in the same place for like 5 minutes or have not issued any commands for 5 minutes?

Also a simpler question I have is what trigger would I use to remove someones units when they leave the game?

Plz answer both, Thanks!!

 

[Myzteryz]

uhmm...would be possible

but im not quite sure how...



by the way...thats not a good idea doing that trigger...wat if they r healing or like choosing between items...its just gonna get ratings down on ur game...trust me

second question

Event-Player leaves game
condition-none
action-remove all units from matching player from entire playable map


i think thats it

 

[ArusSage]

Wouldn't the action be:
remove all units from triggering player from playable map, not matching player?

 

[Myzteryz]

oh,....yes true....my bad

 

[Prometheus]

Hope this helps

Thsi will only work for one unit, you probally make a better trigger but this is all i came up with.

MeLikeMonkeys
Events
Time - Elapsed game time is 300.00 seconds
Conditions
((Player 1 (Red) controller) Equal to Computer) or ((Player 1 (Red) controller) Equal to None)
Actions
Unit - Remove Player1RedsUnits from the game

and

Player1RedsUnuts
Events
Map initialization
Conditions
Actions
Set Player1RedsUnits = (Random unit from (Units in (Playable map area) owned by Player 1 (Red)))


I'm not sure if the Map initialization Event should be there


Edit: You would probally need to make one of these for eatch player and you could just use a -kick system for the players that just pretend to bo AFK

 

[Im_On_56k]

What is that trigger suppose to do?

 

[Prometheus]

Not 1

Theres 2 Triggers as you can see and "Player1RedsUnits" is a variable...........

 

[Im_On_56k]

I will ask you again since you didn't answer me.
What is that suppose to do.

 

[Prometheus]

Um it is the answer to the origional posts question 1.

 

[zll7]

that has nothing to do with question1... doesent really do much but remove 1 random unit...

as far as question one goes you could do domething with triggers and regions so that if a units owned by a player is still in that same regions 5 minutes into the game you would remove all of the players units... or kick the player.

 

[Im_On_56k]

Make a integer, every second of the game set the integer +1
If the integer reaches 1000 lets say boot the player.

But
Make multiple events for another trigger like
A unit is issued an order with no target
A player selects a unit
A unit aquires an item ect
Then set the integer to 0 for that player.

 

[phyrex1an]

If you mean kick a player if he is inactive for 5 mins even if those 5 mins is after 30 mins of play this will do it:

Required: A timer array variable with size 12.

Triggers:

    Events
        Unit - A unit Is issued an order targeting an object
        Unit - A unit Is issued an order targeting a point
        Unit - A unit Is issued an order with no target
    Conditions
    Actions
        Countdown Timer - Start AFK_Timer[(Player number of (Owner of (Ordered unit)))] as a One-shot timer that will expire in 300.00 seconds

    Events
        Time - AFK_Timer[1] expires
    Conditions
    Actions
        Game - Defeat Player 1 (Red) with the message: AFK!


   Events
        Time - AFK_Timer[2] expires
    Conditions
    Actions
        Game - Defeat Player 2 (Blue) with the message: AFK!

Repete for all players
(it there no timer comparission?)


-Edit-
Mine and 56k is equal.
I dont know wich is least laggy. To have 12 timer running or to set 12 varibles +1 each secund.

-Edit again-
When I think about it: 56k's is esier to do, you only need two triggers.
One to add to the varibles and check if each index is over 1000 and then kick the player and one to set the varible to 0.

 

[AceHart]

Lots of triggers, lots of timers.
Here's a more compact version:

PlayerStillHere
    Events
        Unit - A unit Is issued an order targeting an object
        Unit - A unit Is issued an order targeting a point
        Unit - A unit Is issued an order with no target
    Conditions
    Actions
        Set PlayerStillThere[(Player number of (Owner of (Ordered unit)))] = True



GoneToBed
    Events
        Time - Every 300.00 seconds of game time
    Conditions
    Actions
        For each (Integer A) from 1 to 12, do (Actions)
            Loop - Actions
                If (All Conditions are True) then do (Then Actions) else do (Else Actions)
                    If - Conditions
                        PlayerStillThere[(Integer A)] Equal to False
                    Then - Actions
                        Game - Defeat (Player((Integer A))) with the message: Go to bed!
                    Else - Actions
                        Set PlayerStillThere[(Integer A)] = False

With "PlayerStillThere" an array of booleans, of size "number of players" (I assumed 12 here).

 

[phyrex1an]

but that only kicks players every 5 min not after 5 mins of AFK. So you can be afk with a max of 9 min and 59 sec with that trigger.

But I am maybee a perfectionist?

I think 56k's is the best. You dont have to add each sec with that but maybee every 10 sec. Then you can be afk with a max of 5 min and 9 sec.

 

[AceHart]

> but that only kicks players every 5 min not after 5 mins of AFK.

Yes. All players are treated equal.

> So you can be afk with a max of 9 min and 59 sec with that trigger.

No. 5 mins at most.

> But I am maybee a perfectionist?

That's not necessarily bad. Or good
But, for people that went to bed (or whatever)
does it really matter whether you kick them after precisely 2'39'' or is around 2'40'' Ok too?

 

[phyrex1an]

No. 5 mins at most.

1. The trigger GoneToBed has just runned so PlayerStillThere[my number] is false

2. After 1 sec I order my SuperMegaUltra hero to blow the enemy into pieces so PlayerStillThere[my number] is set to true by PlayerStillHere.

3. SuperMegaUltra is killed and i left the computer to cry in a corner

4a. 299 sec after (2) GoneToBed checks if PlayerStillThere[my number] is true. It is that and I am still in game, and my corner starts to be wet.

4b. PlayerStillThere[my number] is set to false by GoneToBed.

5. I am still in my corner and cries.

6. 300 sec after (4a-b) GoneTo bed checks if PlayerStillThere[my number] is true and it isnt. I am kicked from game after 599 sec.

7. I have drovned in my corner.

No offense

But, for people that went to bed (or whatever)
does it really matter whether you kick them after precisely 2'39'' or is around 2'40'' Ok too?

You have a point here.

 

[Grundy]

my way is the best way:

Update AFK Timer
    Events
        Unit - A unit Is issued an order targeting an object
        Unit - A unit Is issued an order targeting a point
        Unit - A unit Is issued an order with no target
    Conditions
    Actions
        Countdown Timer - Start AFK_Timer[(Player number of (Owner of (Ordered unit)))] as a One-shot timer that will expire in 300.00 seconds

Kick AFK
    Events
        Time - AFK_Timer[1] expires
        Time - AFK_Timer[2] expires
        Time - AFK_Timer[3] expires
        Time - AFK_Timer[4] expires
        Time - AFK_Timer[5] expires
        Time - AFK_Timer[6] expires
        Time - AFK_Timer[7] expires
        Time - AFK_Timer[8] expires
        Time - AFK_Timer[9] expires
        Time - AFK_Timer[10] expires
        Time - AFK_Timer[11] expires
        Time - AFK_Timer[12] expires
    Conditions
    Actions
        For each (Integer A) from 1 to 12, do (Actions)
            Loop - Actions
                If (All Conditions are True) then do (Then Actions) else do (Else Actions)
                    If - Conditions
                        (Remaining time for AFK_Timer[(Integer A)]) Less than or equal to 0.00
                    Then - Actions
                        Unit Group - Pick every unit in (Units owned by (Player((Integer A)))) and do (Unit - Remove (Picked unit) from the game)
                        Game - Defeat (Player((Integer A))) with the message: AFK too long!
                    Else - Actions

AFK_Timer is obviously a timer array, 1 for each player.

 

[Axe.killer]

Moving
    Events
        Unit - A unit Is issued an order targeting a point
    Conditions
    Actions
        Trigger - Turn off Timed <gen>
Timed
    Events
        Time - Timer expires
    Conditions
    Actions
        -------- Initially off --------
        Unit - Kill No unit
Not moving
    Events
        Unit - A unit Is issued an order with no target
    Conditions
    Actions
        Countdown Timer - Start Timer as a One-shot timer that will expire in 300.00 seconds
        Trigger - Turn on Timed <gen>

 

[Grundy]

nope. my way is better. i only use 2 triggers.

 

[Axe.killer]

Its not a contest buddy, urs is better happy?

Mine has 3 but is easier to understand