New Pug Rules :D

I say we go back to the old rules where everyone is pickable not the first 12. Used to be fun and stuff now everyone argues about it and no one even knows the rules and the "new" people always think their right and it is a big mess. New thought in next LO meeting

I vote no right now ... Although its confusing, it still gives everyone the same opportunity to play, including new people.

I would be more willing to going back to a 13 slot server rather than a 16 like now (which would just eliminate confusion now).

To be honest, that's a really bad idea. I remember when I was a noob, and I would be the 4th one or there abouts in the server then we get 12. And before I get picked someone strolls in and gets picked and I have to sit even though I was waiting there for 20 minutes.

To be honest I was thinking to apply something the opposite of this. Lets say a pug ends and there are 15 players that are pickable (no one leaves from last pug, and all 3 spectators were waiting throughout the pug), I think it is only fair that those 3 spectators have to be picked. This hasn't really been a problem recently, but it has happened before.

Warcat wrote:To be honest, that's a really bad idea. I remember when I was a noob, and I would be the 4th one or there abouts in the server then we get 12. And before I get picked someone strolls in and gets picked and I have to sit even though I was waiting there for 20 minutes.

To be honest I was thinking to apply something the opposite of this. Lets say a pug ends and there are 15 players that are pickable (no one leaves from last pug, and all 3 spectators were waiting throughout the pug), I think it is only fair that those 3 spectators have to be picked. This hasn't really been a problem recently, but it has happened before.

that

Interesting idea... What if there is a sub in that situation? Like the sub waits till the 25 minute mark in the pug, gets subbed in and plays for 5 minutes. Forced to be picked next pug or not?

Either way, I will be making an LO post about that rule (just to try it out for now).

EDIT : I have already thought of 2 issues with this rule... 1 being that if someone that watched the whole previous pug is not picked, and then the rule is implemented, who subs out for him? The 2nd issue is deciding how long the subs would have the be in the pug before. I do not believe if they join 3 seconds before the previous pug ends that they should be forced to be picked.

idk i just liked it back then . for i reason i would say now but its kinda obv

1.) How is it confusing as to who joined? Just go to your steam friend's list, find someone thats in the server, right click their name, view server info......the 12 people who have been in there the longest are the 12 that can play....the others are late. Nothing to argue about, nothing to be confused over.

2.) The proposed rule of forcing people to be picked if they have sat through a pug and no one leaves the server for the next pug, although I can see the point your trying to make, just seems too cumbersome. It is a very circumstantial situation that really doesn't happen all that often and I think a rule regarding it would be more problematic than beneficial. It seems like it would just be confusing and difficult to implement appropriately.

^^^My 2 cents

~Dill

How hard would it be to implement an int counter in the soccer mod script? As people join or leave the server the counter is incremented by 1, and if you join and the counter is <= 12 then you have a (NOT LATE) displayed next to your name. Else you have a big red (LATE).

I could attempt to do this but as stinger knows I don't know python D:

I don't believe that would be the difficult part of it. I would think the difficult part would be the exceptions to being late. Such as joining while the pug is going, and having more than 12 pickable for the next pug. There is our also our time out rule, which allows you to come back if you time out as long as its by a certain time. There are just some exceptions that make this script equally, if not more, confusing then the way we have it set up now.

As Dill said, server info is the easiest and most efficient way to see who is late, and its not very hard to do so.

Stinger wrote:As Dill said, server info is the easiest and most efficient way to see who is late, and its not very hard to do so.

Agreed. Still may have the issue of people doing restarts for invisible ball, white nets, voice_enable 0, etc. Doing restarts before people start picking usually causes the issues and debates over who was in first.

Personally and the only way I know how to combat that is to wait to be picked then do your restart. I think a good outline of such things as, being afk at the start of the pug, should you get your spot back or do you forfeit your spot to the readily available lates/extras? Also for those who refuse to play their assigned positions, and who should be deemed new captain if the captain has to leave/sub out. I know there has been issues with players arguing their spots and assigning themselves positions.

But really, it's a pug guys. Should be a lot more mature about the whole situation and to let things go if they don't go your way. If you want to play wing or center and the captain puts you defense or goalie, then type ".c" to volunteer for captain next time and put yourself wherever the hell you want.

Edit: Just another thought, if we have some afks and the team with the kickoff decides to wait. THE OTHER TEAM NEEDS TO STAY THE HELL OUT OF THE CIRCLE AND THE OPPOSING TEAMS SIDE. Yeah it's cute if you want to hump someone's leg you know on the other team, but there is no reason for you being in the circle before kick off.

Some quick pseudo code that models what I think would benefit everybody... of course this implies that we create a player class and each player in the server has an object associated with them.

if(player.join()) {
if(totalPlayers <= 12) {
//mark player as not late (sets a boolean var as true)
player.notLate();
}
else {
//mark player as late (sets a boolean var as false)
player.isLate();
}
}

//When we start picking...
for(all players) {
//prints whether player is late or not depending on status of boolean var
print player.getStatus();
}


________________________________________________________

IDEA:

//Restart Counter gives a non-late player 2 minutes to restart or rejoin without loosing their not late status

EX: Player types !restart and a counter starts. That player now has 2 minutes to rejoin the server, if they rejoin within the 2 minutes then they keep their not-late status. If they are unable to do so then they loose it. This option is not available once a pug starts.

loading wrote:

Stinger wrote:As Dill said, server info is the easiest and most efficient way to see who is late, and its not very hard to do so.

Agreed. Still may have the issue of people doing restarts for invisible ball, white nets, voice_enable 0, etc. Doing restarts before people start picking usually causes the issues and debates over who was in first.

Agreed x2. As far as those questions / concerns go :

I think a good outline of such things as, being afk at the start of the pug, should you get your spot back or do you forfeit your spot to the readily available lates/extras?

Our current ruling is that you have to be afk 30 seconds during the time your expected to be playing. So if the ready timer is going for 2 minutes and the player sits in the spec for those 2 minutes afk, but comes back 10 seconds into the game he/she is expected to still have their spot. We feel this is best because you never wait a crazy amount of time for a single player, but yet players are still able to go do something quickly at an appropriate time.

Also for those who refuse to play their assigned positions, and who should be deemed new captain if the captain has to leave/sub out.

There is no official ruling on this YET. But normally what I suggest is that the first pick turns into the captain. 9 times out of 10 the first pick of the team is experienced veteran who could be perfectly fine to be captain.

Edit: Just another thought, if we have some afks and the team with the kickoff decides to wait. THE OTHER TEAM NEEDS TO STAY THE HELL OUT OF THE CIRCLE AND THE OPPOSING TEAMS SIDE. Yeah it's cute if you want to hump someone's leg you know on the other team, but there is no reason for you being in the circle before kick off.

I don't have a huge issue with this at the moment. I completely agree that its funner to hit a ball around / run around in stands then just sit and wait for the afks to return. Not to mention that most likely the non-afk players won't be paying attention so there is the potential of a unexpected krypt goal (or even just a quick kickoff play). There are admin commands that can get the pug up and running within a second if the admin knows what to do (Stop Pug -> Start Match -> Force Players Ready).

meh wrote:Some quick pseudo code that models what I think would benefit everybody... of course this implies that we create a player class and each player in the server has an object associated with them.

if(player.join()) {
if(totalPlayers <= 12) {
//mark player as not late (sets a boolean var as true)
player.notLate();
}
else {
//mark player as late (sets a boolean var as false)
player.isLate();
}
}

//When we start picking...
for(all players) {
//prints whether player is late or not depending on status of boolean var
print player.getStatus();
}


________________________________________________________

IDEA:

//Restart Counter gives a non-late player 2 minutes to restart or rejoin without loosing their not late status

EX: Player types !restart and a counter starts. That player now has 2 minutes to rejoin the server, if they rejoin within the 2 minutes then they keep their not-late status. If they are unable to do so then they loose it. This option is not available once a pug starts.

I see no huge benefit to implementing this script... We can already easily tell who is late and who is not, and id rather have that kept monitored by players than a script..

ok it was just an idea no need to blow it up

We are way past your idea :O This has now pretty much turned into a suggestion topic lol.

[quote="Stinger"][quote="loading"]

Stinger wrote:I don't have a huge issue with this at the moment. I completely agree that its funner to hit a ball around / run around in stands then just sit and wait for the afks to return. Not to mention that most likely the non-afk players won't be paying attention so there is the potential of a unexpected krypt goal (or even just a quick kickoff play). There are admin commands that can get the pug up and running within a second if the admin knows what to do (Stop Pug -> Start Match -> Force Players Ready).

As easily as it would be to run those commands, what should we do if the pug is 23 minutes in after a TO and someone decides to bump the ball?

Be pretty sick if you guys could implement the script from the 2007 soccer map via the "push" when it's not your ball that wouldn't allow players to cross over midfield and/or circle before kickoff.

But it might not even be a good idea. A heavier code usually results in a more easily broken script.

A !to freezes all players :O But that script wouldn't be bad I suppose.

We should have a script on psl that makes the people who aren't late have a sign that shows they're not late or something wa. and same with the late people

Dice-K wrote:We should have a script on psl that makes the people who aren't late have a sign that shows they're not late or something wa. and same with the late people

that's exactly what I was proposing

However it seems that most people are in agreement that it's just as easy to check the server info and implementing this is not worth the effort.

We should do this script:

if {player.join = Late}
"@ban {player.join};

lolwut ^

But anywase the only problem I really have with lates and stuff is when the server crashes right before picks, it really fucks up shit.

Yeah old ass topic.... but whats the problem with just having 13 slots

The main pro to having 16 slots is having easy subs for matches, but ill make another vote just to make sure we want 16.

Ah, I just dont understand why the extra people can't go in STV. I feel like the pro to having 16 slots isnt that big and i think it just creates problems. But thats just my opinion

new picking order

1st pick doesnt get u last pick anymore

that is all

Bazooka Joe wrote:Ah, I just dont understand why the extra people can't go in STV. I feel like the pro to having 16 slots isnt that big and i think it just creates problems. But thats just my opinion

agreed, all the new people cry about being late and rules while they dont know them and people are to lazy to read them so i would still like a 13 slot server!