We’re making two important updates to CCE: a new point system and an updated SQL schedule for weeks when ALGS is running.

These changes will take effect starting Tuesday.

📈 New Point System

After reviewing player feedback and the results of the community vote, we’re officially introducing a reworked point system.

Our goal with this update is to place more value on consistent placement and end-game performance, while reducing the incentive for overly aggressive early-game plays.
- 1st 120
- 2nd 110
- 3rd 100
- 4th 90
- 5th 80
- 6th–7th 60
- 8th–10th 40
- 11th–13th 30
- 14th 20
- 15th 10
- 16th–20th 0

Additional Changes

Match Cost: -40 points
This is a 10-point increase from the previous match cost.

KP Cap: 14 KP per game. Yes — the KP cap is back.
We spoke with a large number of regular CCE players about bringing the cap back, and roughly 95% of the feedback we received was positive.

We hope the combination of the new placement values, increased match cost, and KP cap encourages teams to prioritize reaching and playing out end-games while reducing unnecessary early-game inting.

🕐 SQL Schedule Changes

Because of ALGS and Challenger Circuit events, we’re also adjusting how SQL is scheduled during active ALGS weekends.

This week, SQL will not take place on Monday due to the CC EMEA and NA Finals, which require more than eight hours of hosting.
Instead, this week will mark our first official on-season SQL schedule:

Tuesday / Wednesday / Thursday

Going forward, the schedule will depend on whether ALGS is taking place that weekend.

When ALGS events are taking place over the weekend, SQL will move to weekdays:

Tuesday / Wednesday / Thursday - Where server times will look as such
- EU: 3:00 PM – 6:00 PM ET
- NA: 6:00 PM – 9:00 PM ET

When there is no ALGS event taking place over the weekend, SQL will follow its normal schedule:

Friday / Saturday / Sunday - Where server times will follow the normal schedule
- EU: 2:00 PM – 5:00 PM ET
- NA: 5:00 PM – 8:00 PM ET

Thank you to everyone who voted, provided feedback, and helped us work through these changes. We’ll continue monitoring how the new system performs and make adjustments where necessary.

See you in SQL!