UnFreeZe Tournament Summer 2026

[^Walnut*]

I will give you btw final answer about the date for next week fight probably tommorow, Wednesday looking good so far though!

[adminless]

ok no problem, they are already ready for such date and awaiting picks so when you know just tell me. ok, everything done now with today games and YouTube videos just finishing to post them after I write this, ggs. now a few comments about things that got brought this evening. first about the maps, I haven't barely talked so far because I believe that by this point it should be well know that everything that's there is there for a reason as can be seen with the picks every week so if something it's played it's people pick it. nothing is forced upon anyone, there's no tie-breaks among other things for that reason as well, the map pool is as large and varied precisely to account for that (i.e. so every team can have sensible choices) and ultimately there's even one map block per game per team so I don't really think that with the current format there should be much to argue about that. in particular just for reference even without the full tournament compete this is the summary of all that has been played so far along with the frequency:

Code: Select all

      6 - reqdm5
      6 - hub3tourney1
      5 - bal3dm3
      4 - q3shw14
      4 - q3dm14
      4 - 7++
      3 - teddm1
      3 - 6++
      2 - storm3tourney1
      2 - q3dm8
      2 - pro-q3tourney7
      2 - pro-dcmap7
      2 - bloodcovenant
      1 - q3dm7
      1 - pro-q3dm6
      1 - pro-q3dm13
      1 - nodm9a
      1 - goldleaf
      1 - focal_p132
      1 - charon3dm9

as can be seen there up to 20 maps has so far been played out of 26 in total and three other were selected as well but got blocked, overkill/pro-q3tourney2 and most notably poq3dm5 that got blocked 100% of the times. that means that only the classic well known solid map phantq3dm1_rev has not been picked yet which clearly shows that (virtually) everything is there for a reason indeed. speaking of which this is probably not the moment but since it was brought apparently the only that has been cast aside is 13excave and 13hell that are pretty two maps that I just dropped there to help any potential team in the pubs to better transition into the tournaments. obviously with teams rated in the 1700+ range such thing is not going to happen so given that they have already ran long enough in the pool and they are just not being played for the next edition I'll probably remove/replace them.

other than that it was also asked about the round limits and servers. about the first I think it should be well known that some two years ago the current two top rated team, ass and dt, encountered in q3dm7 and spend all the game shooting corners and thawing which led to a score of something like 1:1 after some solid 20 minutes which is what led to the introduction of the round limitations. as explained back then and reminded today in-game, there's no such hard round limits like that but simply the game slowly transition from the usual competitive UnFreeZe ruleset to strict clan arena (i.e. team elimination with no pickups) between 3 and 5 minutes of round time in order for it to finish in a sensible amount of time which is more than a generous time. about the server once again remain everyone that there's two available different routes for a reason so before going for a free proxy/vpn or any other random 'solution' that most likely than not, it's gonna break out like five minutes later, always check both routes first in the event of some issues. both servers are available at all times on both routes in the usual ports. and I think that's all for now.

[^Walnut*]

We can play Wednesday next week 21th at 19:00 CEST!

[adminless]

breaking ilm just turned around the 1:3 score from the first leg just a couple of weeks ago in a pretty similar fashion where ofp beat everyone's expectation without their flagship players and took the opening map to then end up conceding the three remaining in favor of a strong ilm that looked pretty nervous but managed to pull off the score somehow. probably ofp biggest mistake was their second home map choice, storm3tourney1, that was greatly favorable for ilm and ended up deciding the ilm victory this night. in any case a fight that will definitively deserve some synthetic analysis to truly understand what happened. as usual I go post and update everything so stay tuned for more commentary afterwards.

[adminless]

@walnut ok perfect then noted for the next Wednesday and when you know what you want to play just tell me in the next days to proceed as usual. remember that 7++, teddm1, poq3dm5, q3dm14, bal3dm3, goldleaf was chosen in the first leg.

[^Walnut*]

Update about time btw, 19:40 CEST instead of 19:00 for our match! Will give map picks soon

[adminless]

they always struggle with the time so I think that probably 19:30 CEST and start a little later is a better option so I'll ask them now.

[adminless]

nevermind they just agreed now Wednesday 21 of October of 2026 19:40 CEST (UTC+02) so that will be the date. regarding this evening fight, actually looking now at the stats for other than the first map where ofp beat expectations given the formation it wasn't even that close. even when top tier player blrskj joined them in the second half he was unable to carry them and deliver a win. kind of surprising as ilm focused more on individual play and their thaw performance was a bit weak while ofp for other than the third map played pretty much their usual self. as said, I assume this is a great example of why the second leg and the maps I was talking about are there for. if it were all about teddm1, the tournament would have been way over already but it's clear it's not. other than that let's clear once again a few things that were brought up in the game. first, although as I often say things aren't black and white so I'm not gonna be with a clock there to kick anybody by the second the warmup time between maps should be limited to no more than 5 mins more or less just the necessary to assemble and briefly discuss a few tactics. games can not simply be consistently dragged +5 mins over and over waiting for some player to show up, other player to install the map, other to update social media with the results (was not the case but just saying, you get the point) and the likes, all that needs to be sorted beforehand and the same goes for the initially noted match start time, fights can not systematically start (almost) 10+ mins later. as said, it didn't get to the point where I needed to intervene but it was definitively a annoyance. second there was the topic passwords, as reminded literally dozens of times due a client bug people using community files need to enter the password twice to not lose it on map start due, I repeat, a client bug or simply use some of the provided packages in this site that have such bug patched. once again as with the timing, things aren't black and white and, no, I'm not gonna ban anybody for missing a password or now start messing up games because of that so when someone happens to drop on map start I simply fairly restart the map and I'm gonna continue doing it. that being said, obviously everything has a limit, I'm not gonna be restarting a map forever, I might do it once or twice at most, if after that some people is still missing the password and dropping then it will come down to them to get it right and the game will proceed even if there's less players and they will late join then. in that regard I would also like to specifically point as there seems to be some confusion that the drop happens exactly on map start before even spawning so beside wasting everybody's time there's nothing to exploit there. it's not like they spawn eat two rails and as the third is reloading they panic and press the password key to get dropped. no, it does not work like that, and any delay between the drop and map cycle simply comes from me reviewing the situation and issuing the commands so rest assured that for other than getting on your nerves that does not have any impact in the result.

[^Walnut*]

The 19:40 CEST was actually already agreed before I send the message, I gave it as an update for both clans