Ladle 31+ Also concerning ladle 30(event that took place)

[Cody <3]

This ladle was very fun indeed, me and my team had a great time but there was a downfall.

IN TSP NY, most of the members (on both teams) could not shuffle, therefor I had to /op 80% of ST and 100% of my team so we could shuffle.

Also ST had no TeamLeader at the start. I tried oping Bsy to team leader and couldn't do it, only could op him to team member.

My question is since supposedly in ladle 31+ we're going to have GM's does this mean Team Leaders get kicked to the side? If team leaders do return for ladle 31+ can we have oping power to op other people to Team Leader If needed????

Really thats was the only problem I ran into this ladle.

I did go ahead and post a new topic for this so I hope i don't get flamed for it.

[LucK]

Was psy the person trying to login because if so he is not set as the team leader so only the team leader can sign in as team leader.

[sinewav]

Is compguygene still keeping his servers up to date? Maybe we should look for alternatives. I can probably get one up for next Ladle if we need it.

Gene, where are you!?

[Cody <3]

Is compguygene still keeping his servers up to date? Maybe we should look for alternatives. I can probably get one up for next Ladle if we need it.

Gene, where are you!?

They said Ladle 30 so I thought they would be up too date but then that shuffle problem came up.

Was psy the person trying to login because if so he is not set as the team leader so only the team leader can sign in as team leader.

He was not set for team leader/ but the team leader was running late so in these situations I think another Team Leader should be able to op someone on the opposite team to Team Leader

[compguygene]

I am still around. I thought i had the proper permissions set.

[þsy]

Ahh yeah, the problem with my login was that I was team leader of SP, but the overall captain was Puuquie and he didn't turn up till late

[Titanoboa]

I noticed in ladle 31, the shuffle issue still wasn't solved.

ACCESS_LEVEL_SHUFFLE_UP 20

Must be something in gene's server settings that overwrites this setting.
I know it's obvious, but since it potentially slows down the tourney it should be fixed.

As for the /op problem if it isn't solved already:

Code: Select all

ACCESS_LEVEL_OP 7
ACCESS_LEVEL_TEAM 8

[sinewav]

The problems with settings should be solved pretty soon. Not too long ago, kyle rewrote the Ladle CFG just for this reason. Flex and I checked it, and I think some other looked over it too. I imagine we'll start using it after the next vote (I think that was the plan anyway).

Since authority is still a problem occasionally, we should look for a solution. It would be nice to just INCLUDE the authority.cfg right into the Ladle.cfg and overwrite the authority.cfg when needed. I know that's the totally wrong way to manage a resource, but I'm just throwing ideas out there.

[compguygene]

There is a very simple reason that server was not up to date. The actual Texas server that was up to date became borked. The server you were in was never meant to be up, period! I quickly threw up 2 servers out of NY, which I am trying to not use anymore. Unfortunately, in the heat of doing this, 5 minutes before the ladle start, I accidentally put up 2 servers out of NY that did NOT have the proper config. As soon as I realized what had happened, I went to the server where the CT match was happening and gave admin to Owned! Then they were able to sort out the proper rights and get the match going.
At the time, I did not realize that a match was going on in the other NY server. The authentication configs were proper one's in the servers that were to be used in the Ladle. Unfortunately, for the first time ever, the VPS that the Texas server is on ran out of memory. Before the next ladle, as in this week, gameservers that were on that VPS will have been moved, leaving that resource of my pretty much unused, except for tourneys. When I am done moving GameServers around, the servers that I host GameServers for tournaments from will be pretty much dedicated to tournament use only with almost no other traffic. Unfortunately, I was unable to complete that process before Ladle 31. After all the work that I put into making sure my Ladle Servers that were being used in the Ladle were optimally configured, this was a extremely frustrating! The darned Texas server was working fine 3am the night prior to the Ladle! Grrrrrrrr!
The new TheServerPharm PA servers worked well this time! The configs were right, and the servers appeared to have none of the lag bombs and sliding that the NY servers had in the past. Within 2 weeks, the NY servers will be gone! In related news, TheServerPharm EU servers went down, as my provider messed up a memory upgrade that I had purchased about a week ago. Thankfully, none were actually being used in the ladle. I cannot access the hosting server at this time, but that should be rectified soon.

[Titanoboa]

As for gameplay, I think most players agree that your server was better than Z-man this ladle (I'm talkin PA1 vs Z-man's), the only issue I had was that access_level_shuffle_up was on 15-19 in the finals. Luckily we managed to pull through the round where our right side was not covered.
Not trying to put blames, just trying to help.

[compguygene]

I noticed in ladle 31, the shuffle issue still wasn't solved.

ACCESS_LEVEL_SHUFFLE_UP 20

Must be something in gene's server settings that overwrites this setting.
I know it's obvious, but since it potentially slows down the tourney it should be fixed.

As for the /op problem if it isn't solved already:

Code: Select all

ACCESS_LEVEL_OP 7
ACCESS_LEVEL_TEAM 8

I realized that those setting were wrong in my servers, fixed.