---

Bans

The following ban/s are all Infraction Threshold bans, split between New Bans, and Ban Resets.

New Bans

The following player/s accrued enough points to reach an Infraction Threshold Ban.

Pestilence STEAM_0:0:192340355
This player has accrued a total of 60 ozfortress infraction points. As such, the player has been banned from ozfortress.com, the community's competitions, and all other ozfortress properties for 1 year, after which they will serve a 12-month probation, in which any reoffence will double the severity of the penalty. Their ban duration will be extended if they are found ban-evading during their ban.

Ban Resets

A newly introduced alternative to our old Ban Extensions, see our news post discussing this change here. Ban Resets will reset a person's ban back to its original duration.

Xstroyer STEAM_0:1:567280780
This player has accrued 30 ozfortress infraction points whilst serving their ban. As they accrued these infraction points during their ban, the player has had their ban reset back to a total duration of 1 year. After their ban, they will serve a 12-month probation, in which any reoffence will double the severity of the penalty. Their ban duration will be extended if they are found ban-evading during their ban.

---

Should any teams or groups within any ozfortress competitions be found housing the listed player, that team will be permanently banned from our competitions and all members involved will face hefty league bans.

---

TLDR for the Zoomers

If you have tried to, or believe you have signed up your roster/s for the Winter '24 seasons, please ensure your roster is signed up to the season. we had incorrectly set the maximum roster size value for Sixes at 8 players for the majority of the signups period. Compounding this mistake further, our website does not properly make users aware that their signup application was invalid (for example, exceeding the maximum roster size), meaning many may not even be aware that their roster was not signed up.

---

Hang on, what?

In the post-season meetings for the Autumn '24 seasons (initially in the Highlander meeting) a proposed roster size change was suggested, where the maximum roster size would be lowered during the signups period, and would then return to the traditional maximum roster size once the season had commenced. The primary intention of this change was to see if it could have an impact on substitute player choice, in the hopes of encouraging the rostering of only reliable substitute players, emphasising a focus on roster health first before rostering potential roster riders. Whilst there were other reasons, this was the primary reason for exploring this change. This proposal was also raised at the Sixes post-season meeting, but it was decided that Sixes would not experiment or test this change, thus leaving Highlander to test it alone.

So why is this an issue?

Initially, the suggestion was to test having the maximum roster size for Sixes set to 8 during the signups period, with it returning to the traditional maximum roster size of 10 once the season started, similar to Highlander and allowing the change to be tested "globally". However, as Sixes would not be following through on this proposed change, the settings for the Sixes Winter '24 season page should have been set back to the traditional maximum roster size setting, but at our fault we failed to do so.

Compounding the issue further, our website doesn't make users aware that their signup application failed to go through due to their roster exceeding the maximum roster size, meaning many Sixes and Highlander captains may not even be aware that their roster was not signed up to the season.

What are we doing to remedy this?

• Sixes

  • We will not be making any changes to the maximum roster size for Sixes Winter '24.
  • The maximum roster size setting for this season has been set back to 10 on the Sixes Winter '24 season page. If you had previously thought that you had signed up for this season, please double-check that your roster is listed as signed up.
  • We will be monitoring signups closely, and we are ready to extend the signups period to June 26th if necessary. Please note that the signups period is still set to close 11:59PM June 19th as originally planned, but we will let everyone know if we extend the signups period.

• Highlander

  • As the roster size changes for Highlander were properly documented with the launch of the season's signup period, we will be staying the course and capping the maximum roster size for Highlander at 12 until the season starts, then raising the maximum back to the traditional 15 during the first transfer window.
  • During the first transfer window, you will be able to request enough transfers to fill your roster.
  • If you were not aware of this change, please double-check that your roster is listed as signed up.
  • If deemed necessary, we will extend the signups period by a week, but please note we are less likely to extend the Highlander signups period due to the changes being announced with the launch of the season.

An Apology

Whilst for Highlander everything is as intended, for Sixes we failed to set the season page settings correctly, and for that we are sorry. After what was for some a rough season (particularly for those in High or Intermediate last season), we understand this is not a good start to a fresh season. We are to improve the signup application handling, adding success or error notices so users know if their signup application was accepted by the system, or if not why it failed.

More Rule Changes Coming

We haven't forgotten about the issues raised by you all in the previous Sixes season regarding late team signups and roster disbanding/undisbanding, and will be releasing a docs update post before the start of the Sixes and Highlander seasons documenting all of the rule changes and where to find them, including more reasoning as to why some changes were made. In general, we need to get better at providing our reasoning as to why we are making changes, and that will be a particular focus of this upcoming post. The current public version of our docs does not accurately or correctly reflect the changes for this season, and will be updated alongside the release of our docs update post shortly.

---

---

Ultiduo 18 is just hours away!

Sorry it took us so long to get this out, that one sits squarely on me being busy. Team Placements are below, along with any and all crucial info you will need for Ultiduo 18. Please take the time to read through, we've put a lot of work into (particularly) the Ultiduo Ruleset this time around. Many of the old questions/answers were moved to the Ultiduo Ruleset.

Team Placements

Please note that the placements below are not final. We are more than happy to accept feedback on these seedings, but we ask that you make a ticket using our bot via #admin-support or DMing @Alfred directly.

Division 1

1. Chunkopop Enthusiasts
2. GET LIQUIDATED!
3. Team 2
4. Eclipse
5. two men kissing
6. but how washed is tesla??
7. animetv
8. 2 chooks
9. Minji + Danielle
10. Stroketrine & Strokey

Division 2

1. smol cats
2. mhazakey
3. sun with face
4. rolled and smoked
5. Vi(e)t Gang
6. cheese sandwich #1
7. noob ultiduo
8. Ownage + Pure

Division 3

1. Charles and Eddie
2. cheese sandwich #2
3. HoT whEElZ
4. I aint gay but a kiss and a cuddle goes a long way
5. Poopy joe
6. 3 syllable word
7. Sigma nation
8. for every kill you get ill give you a

Division 4

1. MR PEABODY AND GERMAN
2. giant alien spiders are no joke!
3. AvoCado
4. aubdrey
5. Morb Fortress 2 - Morbheads
6. SEMI SLEEPERS
7. Margret Thatcher
8. big challenges
9. hi miku...
10. Peace And War

Weapon Unlocks / Whitelist for Ultiduo 18

As we noted in our previous posts, we ran some Discord Polls to see if players would like to see new unlocks added to the Ultiduo 18 whitelist to spice things up. The results are in, and the following weapons will be added:

• Disciplinary Action added.
• Solemn Vow added.

No other unlocks are being added for Ultiduo 18. You can view the updated whitelist here.

Maps & Poll Results

With the Discord Polls for Weapon Unlocks came polls for new maps. Ultiduo in ozfortress hasn't seen more than one map for what feels like a millenia, so we've added the ones you voted for.

• Baloo added.
• Swine added.
• Champions added.
  • Please note that Champions has Passtime style powerups. We ran a follow-up poll to ensure players were aware of this, and out of everyone who voted, nearly 60% (58%) wanted Champions, so it will remain.
• ozfortress' Ultiduo map will be remaining to bring us to a total of four maps in the pool.

Servers

For Ultiduo 18, teams will need to coordinate with their opponents and book the server themselves from serveme.tf. We have upped the available servers to 20 servers, two over the amount we need. We've left a buffer to allow for some servers that aren't Ultiduo games, but please be aware - if we need a server for an Ultiduo game, we will be unbooking your non-Ultiduo server. However, we will prioritize unbooking empty Ultiduo servers first. If you cannot get a server, please let us know via #ultiduo18-support.

In addition to teams needing to book/reserve their own server, they will also be responsible for changing the map and setting the config. To find these commands, please see our Ultiduo 18 Resources page. It contains the map aliases, configs and everything else you'll need.

If you notice any server stability issues, please do not hesitate to poke is in #ultiduo18-support immediately. Whilst in theory server stability should be fine, we are running a higher amount of servers (although with far less players) than we have before.

Expectations

You've likely heard the first expectation before, but we'll put our expectations (and a few notices) in list form so you know what we need from you.

• Do not delay the match for your opponents.
  • Please start each game as soon as possible as there is a tight schedule, and delaying will delay the entire cup. If the other team has not shown up five minutes after the server has been booked, message an administrator to claim your forfeit win. Please DO NOT delay for the other team as a courtesy.
• The Team Captains Discord will not be used for Ultiduo 18.
  • Instead, there will be an #ultiduo18-feed channel in our main Discord where we will be pinging all participants. If you are not in the ozfortress Discord, please join. We will need at minimum one player from each duo to be present in the ozfortress Discord for the duration of the event.
• A quick reminder, we have an Ultiduo 18 Ruleset now! Please peruse it prior to the event.
• All support should be directed to #ultiduo18-support.
• KritzKast may cover playoffs, it entirely depends on how busy we are.

Most importantly, have fun!

We're hoping the map and weapon changes will put a new spin on Ultiduo for Ultiduo 18. As always, we'll be running a follow-up survey.

---

Resources

Below are some quick aliases for setting up for au.serveme.tf server. To book a server, please head over to serveme.tf.

Server Config

• rcon ozf-ud-ultiduo

Maps

• rcon changelevel ultiduo_ozf_r
• rcon changelevel ultiduo_baloo_v2
• rcon changelevel ultiduo_swine_b06
• rcon changelevel ultiduo_champions_b1

Map Downloads

Map downloads are available on the Ultiduo 18 cup page.

---

serveme.tf Servers Updated!

We want to thank Arie for sorting the servers so quickly. Any player using 64bit or 32bit TF2 clients should be able to play on au.serveme.tf servers without issue. The servers will remain on 32bit for a while until updates and solutions are found/made. To reiterate, 64bit clients can play on 32bit servers.

The majority of the plugins needed for competitive games are functioning as expected, but please report any issues you find immediately to the serveme.tf Discord. We've also updated our #book-a-server channel to now point to serveme.tf for server support.

POV Demo Recording

You may have heard, you may not have. P-REC, our staple POV demo recording tool of the last decade has not been, and likely will not be updated for 64bit TF2. P-REC does still work on the 32bit version of the game, which can be run from the SteamLibrary\steamapps\common\Team Fortress 2 directory, however, there is an alternative if you don't want to give up the performance benefits of 64bit. Whilst some may not like it, the in-game demo recording tool does allow for similar functionality to P-REC. We will be leaving the two main commands to run below, which will help you get the "demo system" setup correctly. We have also finally added our own POV Demo Recording guide to help you get the demo system set up and provide you with all of the commands you need to get it working as closely to P-REC used to.

To be crystal clear, regardless of which TF2 client version you use:

It is the responsibility of the player to ensure they are recording POV Demos when playing official matches. Ignorance of this is not an excuse.

Custom File Issues

Depending on your choice of custom HUD, you may run into issues with certain parts of your HUD. For example, some HUDs are having issues with the loadout section of the inventory. We would suggest joining the HUDS.TF Discord for diagnosing HUD issues if you can't wait for the HUD's creator to update it. Additionally, if you want to see all of the HUD changes, see this GitHub commit.

If you are running into stability issues with your game, we would suggest ruling out your configs and other custom files, and then reporting it to Valve. Some things to note that were changed with the move to 64bit (and that were fixed separately or as a result of 64bit):

• HUD player model has received optimizations in the update thanks to a fix from Team Comtress 2, so it's basically a couple of frames cost instead of dozens.
• If you have -noquicktime in your launch options, it's no longer needed.
• DX8 is causing crashes for people, might be worth going up to DX9.

Match Play Issues

If your match has been impacted or you fear it will be, please feel free to contact your division administrator via the Team Captain's Discord, or by using our #admin-support channel. Please note, however, we do expect everything to run "business as usual", but we're here if you need help.

"What else came with 64bit?"

Again if you don't already know, performance improvements. Anywhere between 15-35% depending on hardware configurations. Check out shounic's video discussing the now finished beta for 64bit.

"Once more for those at the back"

Please be patient with us, Valve, serveme.tf, HUD and CFG makers, everyone. 64bit is a huge move and win for TF2's longevity, but it may come at a cost short term. Issues more than likely will arise, but we'll deal with them.

Sorry this took so long to get out. We wanted to make sure we had a guide ready and could answer some of the questions you may have had. Again, thank you to Arie and the rest of the serveme.tf team for their tireless work getting servers up-to-date and ready.

---

Ultiduo is back in 2024 with Ultiduo 18!

ozfortress' famed Ultiduo returns, this time as a part of our May Madness off-season. Ultiduo 18 will kick off a series of tournaments between the Autumn '24 and Winter '24 seasons.

---

Signups

You can sign up for Ultiduo 18 from now (Wednesday the 17th of April 2024), up until Wednesday the 1st of May 2024. We aim to have initial seedings out by Friday the 3rd of May at the latest. As always, Ultiduo will be on a Saturday, Saturday the 4th of May 2024.

Maximum Signups

We may look to limit the maximum team signup numbers to somewhere between 40-48 teams, as we are worried we will not have enough servers to effectively cover any more teams. It's not ideal, but sadly may have to happen. We will let everyone know how things are looking as we find out ourselves.

SIGN UP TO ULTIDUO 18!

---

Proposed Changes Poll Results

We've included the three most voted-for maps in Ultiduo 18. We are also currently considering the two most voted-for weapon unlocks, those being the Disciplinary Action and Solemn Vow. In addition to those changes, we now have a fresh new Ultiduo ruleset!

For more in-depth info on the results, please see the league page.

---

---

Creating a Team and Signing Up

On the ozfortress website, captains can create Teams using the "Start Team" button on the Teams page. Once created, captains can invite players to the team. Team invites are shown on a player's profile, which can be accessed by clicking on your name next to the bell on the top right-hand corner of your screen. Teams provide a pool of players that can be signed up for a tournament. Players may be in the pool for multiple teams but only one active roster for any given tournament. Captains may sign up a roster for tournaments under the league page.

By signing up, you acknowledge that you may be placed in any division the administrators deem fit for your roster, and thus you should be reasonable in your expectations on division placement. We will endeavour to let duos know of changes in initial seedings before the final release. Please ensure you specify the division you truly believe your team should be in, this will make it easier for administrators to consult with you on your seeding. Along with selecting your desired division, please also list who you expect to play, and what class/role. We've left a template below, please include it in your signup application's description.

Soldier:
Medic:
Discord Handles:

For questions regarding substitutes or mercenaries, please see 1.6. Substitutes & Mercenaries.

---

---

Finding a Partner

---

If you're new and not sure how to get started, don't fret! Check out the Recruitment category of the ozfortress Discord where you can see if anyone is also looking for a partner (you will need to get the Sixes recruiting roles in the "channels and roles" part of the Discord, otherwise you will not be able to see these channels). Ultiduo duos consist of one soldier and one medic.

Once you've signed up your team or have joined one, your part is done.

---