search

OvercastNetwork / Issues

Public issue tracker for Overcast Network
https://oc.tc
53 stars 42 forks source link

Teams can be severely stacked #413

Open bcbwilla opened 11 years ago

bcbwilla commented 11 years ago

Teams can be severely stacked. Example

There should be a check in place that prevents someone (even with a shop package) from joining a team that is some percentage larger than the other.

legobmw99 commented 11 years ago

I think that staff should still be able to join for official purposes such as reports for spamming in team chats, etc

Jolt151 commented 11 years ago

Premium Access Join full servers Choose teams Join full teams (up to 20% more than capacity) (taken from the "Revaming Donations" thread"

it seems that this was originally planned, but was never implemented.

bcbwilla commented 11 years ago

This is a separate but related issue to joining a team that is over capacity. I've never seen a discussion about preventing teams that have a large size difference even if they are below total capacity.

Ideally the relevant line would be changed to something like: Choose teams (such that the team sizes are within 20% of each other)

(20% is just an example, that can be worked out later)

bcbwilla commented 10 years ago

With the addition of the sever "Mini", this problem can be particularly detrimental to gameplay as only a few more people on a particular team can throw off the balance.

Yukon commented 10 years ago

Fixed with OvercastNetwork/PGM@e0fe46a57badc056e95a06200dbf5292ef9f09d9, maps just need updating.

bcbwilla commented 10 years ago

Does the fix actually prevent relative stacking, or does it only prevent stacking above the cap? Please clarify, because I was suggesting preventing relative stacking (independent of map capacity) with this issue, which is still a problem given recent objective farming events consisting of, for example, 5v1 matches.

rmsy commented 10 years ago

Yes, this only prevents stacking above a given (either defaulted to 125% or provided by the map) overflow percentage. A ratio enforcement would be more effective to combat stacking.

bcbwilla commented 10 years ago

Can this issue be reopened then, since what I originally requested appears to have not yet been completed?

Yukon commented 10 years ago

I was just thinking about fixing this today.

tonybruess commented 9 years ago

This was fixed with team capacities.

bcbwilla commented 9 years ago

Are you sure? Is this a new fix to team capacities? Remember, this issue is for RELATIVE stacking, not stacking over the limit. Team capacity does not fix relative stacking issues. This issue was mistakenly closed before due to that confusion.

tonybruess commented 9 years ago

Fair enough, I'm stupid.

ghost commented 9 years ago

https://oc.tc/forums/topics/54b0a8cb5f35b9f495000652 http://gyazo.com/b4ebaf908d6df30afe0c3328b5d29a02

Matic0B commented 9 years ago

@TiTi-418

Do not: Bump issues to receive a response (all issues are acknowledged)

From the README file.