Showing posts by core
Thread: ozfortress Ban: Lain
core League Director

The user below has received a Permanent Ban. This ban type will prevent them from using our services indefinitely. If you are found aiding this person in evading their ban, you will face hefty league bans.

Permanent Ban
Lain STEAM_0:1:94475789

This person has been permanently barred from all ozfortress properties due to severe breaches of our Community Guidelines.

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.

Posted 6 days ago
Link
Thread: Winter '24 - Round Bans
core League Director

The users below are banned from playing a certain amount of rounds in both Sixes and Highlander during Winter '24. Users can receive round bans when accruing Player Behaviour Infractions or League Penalties. See these pages for more information each.

Winter '24 Round Bans

  • noemie Banned until next season (Spring '24)
  • Doctrine Banned Rounds 2 & 3 of Highlander and Rounds 3 & 4 of Sixes.
  • lizzo Banned Rounds 2 & 3 of Highlander and Sixes
  • bill Banned Rounds 3 & 4 of Highlander and Rounds 4 & 5 of Sixes.
  • omni Banned Rounds 3, 4 & 5 of Highlander and Rounds 4, 5 & 6 of Sixes.
  • jv Banned Rounds 3 & 4 of Highlander and Rounds 4 & 5 of Sixes.
  • mira Banned Rounds 3 & 4 of Highlander and Rounds 3 & 4 of Sixes.
  • homer Banned Rounds 4, 5 & 6 of Highlander and Sixes
  • Kyle Banned Rounds 4 & 5 of Highlander and Sixes.
  • smallrat Banned Rounds 4 & 5 of Highlander and Sixes.
Posted about 1 month ago
- edited 6 days ago
Link
Thread: Highlander Winter '24 (S7) - Transfer History
core League Director

Below you can find the transfer history for all divisions. Please note this history is directly copied from our internal transfer management panel, so the formatting is rather rough.

Premier History

Transfer Window #1
Transfer Window #2

Main History

Transfer Window #1
Transfer Window #2
Posted about 1 month ago
- edited 3 days ago
Link
Thread: Sixes Winter '24 (S40) - Transfer History
core League Director

Below you can find the transfer history for all divisions. Please note this history is directly copied from our internal transfer management panel, so the formatting is rather rough.

Premier History

Week 1

Thu Jun 27 22:04:02 2024 Hawk approved zias's transfer into this stuff is so good, out of skywalker in Premier (requested by Maximus)

Week 2

Wed Jul 3 17:34:36 2024 Hawk approved ayr's transfer into munchie paradox (requested by kbn)
Fri Jun 28 18:18:36 2024 Hawk approved bishaminty's transfer into skywalker (requested by Susu)
Wed Jun 26 23:18:48 2024 Hawk approved hif's transfer into this stuff is so good (requested by Maximus)

Week 3

Mon Jul 15 18:18:10 2024 Hawk approved Doge.exe has stopped working's transfer into ASIO (requested by wilsonoid)
Thu Jun 27 22:37:28 2024 Hawk approved lizzo's transfer into this stuff is so good (requested by Maximus)

High History

Week 1

Mon Jun 24 23:09:14 2024 HUNGRY.4.EGGS approved tetrx's transfer into Maxwell Verstappen (requested by Ghost)
Sat Jun 22 13:14:01 2024 HUNGRY.4.EGGS approved heavenslept's transfer into 100 (requested by sinsa)
Sat Jun 22 01:12:29 2024 HUNGRY.4.EGGS approved altfs's transfer into general-2 (requested by Tenous)

Week 2

Fri Jun 28 22:50:23 2024 HUNGRY.4.EGGS approved gaw$'s transfer into obese gaming (requested by 2345y.)
Sat Jun 29 02:24:03 2024 HUNGRY.4.EGGS approved Delphinoid's transfer into First & Lost (requested by Ravu4)
Mon Jul 1 18:56:59 2024 HUNGRY.4.EGGS approved peep's transfer into general-2 (requested by Tenous)
Tue Jul 9 12:36:08 2024 HUNGRY.4.EGGS approved homeslice's transfer into altombo's kittens (requested by alt)
Tue Jul 16 00:01:23 2024 HUNGRY.4.EGGS approved L0RD 8071CU5 0F 80T5W4N4's transfer into Maxwell Verstappen (requested by Ghost)

Week 3

Wed Jul 17 23:26:09 2024 HUNGRY.4.EGGS approved core's transfer into Geezer Gamers (requested by Hawk)

Intermediate History

Week 1

Wed Jun 26 21:49:47 2024 emgee approved K13R7N's transfer into God-Fearing Nuns (requested by ♥ Emily the Goldfish ♥)
Wed Jun 26 20:25:08 2024 emgee approved michael soup's transfer into The Oxyconnoisseur's (requested by Lain)

Week 2

Fri Jun 28 12:58:12 2024 emgee approved vonixyy's transfer into The Oxyconnoisseur's (requested by Lain)
Mon Jul 1 18:40:35 2024 emgee approved dorkson's transfer into DLLM (requested by woozy)
Tue Jul 9 21:05:33 2024 emgee approved Disturbed's transfer into taking my gamer poison (studying) (requested by dezi)

Week 3

Tue Jul 9 21:05:37 2024 emgee approved crispin's transfer into taking my gamer poison (studying) (requested by dezi)
Sat Jul 13 22:12:51 2024 emgee approved ShuZ's transfer into The Oxyconnoisseur's (requested by night)
Mon Jul 1 11:39:46 2024 emgee approved Titan's transfer into DLLM (requested by woozy)

Main History

Week 1

Wed Jun 26 13:54:56 2024 inStinct approved silent* transfer into Shrimps (requested by ScEshay)
Sun Jun 23 23:19:45 2024 inStinct approved goblxn's transfer into Hexabromocyclododecane (requested by Maxyvee)

Week 2

Thu Jul 11 20:25:02 2024 inStinct approved Chungus McBungus's transfer into Level 1 Crooks (requested by ItzSak_47)

Week 3

Thu Jul 11 20:25:06 2024 inStinct approved sle_epy's transfer into Level 1 Crooks (requested by ItzSak_47)

Open History

Week 1

Sun Jun 23 00:57:04 2024 Celph approved Hose_'s transfer into Decepticons (requested by Conner)
Tue Jun 25 19:09:29 2024 Celph approved INFERN0O71's transfer into Zest Fest (requested by dndinsomniac)

Posted about 1 month ago
- edited 4 days ago
Link
Thread: Demo Recording Rule Change, Docs Updates, Infractions Ruleset Changes & Game Server Bans
core League Director

POV Demo Rule Changes

POV Demos can now be requested from any match played on an ozfortress server

To better our league's Anti-Cheat, we will now be able to request POV demos from ANY match played on an ozfortress server - official, scrim, pug game or otherwise. Whilst we understand there will be some apprehension to this change, it is only happening because we feel it will contribute to improving the league. Scrim POV demo requests will be worked into the existing failure penalties. Unlike official match POV demo requests, the first penalty for failing to provide a scrim POV demo is a warning. After this, the next second penalty follows the same guidelines as the official match POV requests, meaning that if you fail two scrim POV demo requests you will receive a six-month ban. It is important to note that we will not conduct random demo checks for any match that isn't an official match. This means that if you receive a request for a POV demo from a scrim or pug, it is related to an active Anti-Cheat report.

Please see the ruleset for more information on failure penalties.

Docs Updates

Global Ruleset Changes (or otherwise Global changes)

  • Soon: Name Change Policy.
    • We are working to create an exhaustive Name Change Policy for our website. We have no details to release now, only that we will be releasing a post dedicated to this sometime during the season. Please be reasonable with your expectations as to what this policy will entail, but keep in mind we are not trying to work entirely against the wishes of our players, we just want to see some sensibility come to name changes in ozfortress.
  • Removed: Secondary Match Days.
    • If teams are unable to play their match within the Playable Match Days for their format, they will need to be granted an extension via their division admin to play on days not within the Playable Match Days. Extensions will be more lenient than they were before Primary/Secondary Match Days were added.
  • Changed: Mercenary Requests & Usage Policy.
    • When admin intervention is required for mediating denied mercenary usage, the proposed mercenary will be valued against the player they are replacing. It is not just a blanket check of the division they are playing in. This is staying in line with restricting mid-season transfer requests to avoid teams upgrading their roster mid-season.
  • Changed/Added: More severe Disband Penalties for Captains.
    • For incidents where it is clear the captains of a roster do not care for their roster or the penalties that come from a disband, or in cases where a captain is purposefully destructive to their roster - captains could see harsher penalties at the discretion of the league administration.
  • Added: Purposeful Sniper scoped-in crouch exploitation is prohibited.
    • When a sniper scopes in whilst crouched, it is possible to obscure up to or above 50% of that sniper's character model whilst still maintaining vision around the objects obscuring their model.
      • We understand that this is potentially difficult to police, however, it will often be very clear when someone is intentionally abusing this mechanical oversight. We will be reviewing each reported case of this behaviour individually, and not blanket banning any instance that could be purposeful exploitation.
  • Added: Any form of complete animation break or exploitation.
    • Some examples are T-Posing or "Civilian mode", Contracker exploits, or ragdoll "mods" that break the intended effect of a Spy's Dead Ringer item. This does not include disabling ragdolls or their physics via a config file, but specifically targets modifications that break animations or ragdolls.
  • Updated: Best of three (BO3) Picks and Bans order has been unified between Sixes and Highlander.
    • The process is now Team A Ban, Team B Ban, Team A Pick, Team B Pick, Team B Ban, Team A Pick. This Pick/Ban process has seen more extensive use in Highlander and other regions/leagues.
  • Updated: Ping Limit and Ping Exception rules to allow for neighbouring regions (Asia) to play within ozfortress.
  • Added: Non-official matches are now required to be recorded by players.
  • Moved: 2.4. Playable Match Days moved to 7.3. Match Organisation & Playable Match Days.
  • Updated: User Policy Conditions now prohibit permanently banned Steam accounts and known sold Steam accounts.

Sixes Ruleset Changes

  • Upper and Lower division terminology removed. This often proved confusing for many, and with us returning to one single 5CP config, there is no longer a need to distinguish beyond just the division names.

Highlander Ruleset Changes

  • Updated: ABBA explainers throughout the Highlander Ruleset, and added 1.3.4. ABBA in preparation for ABBA in the Regular Season.
  • Added: Roster size reduced during signups.
    • Rosters may only sign up for the season with a maximum of 12 players. During the first transfer window, the roster size will be increased back up to 15 and will then remain at that number for the rest of the season. We will be seeking feedback on this post-season.
  • Updated: KOTH map scores should be submitted as 1-0 to the victor.
    • This change works in tandem with the Tiebreakers we have added to the ruleset.
  • Updated/Added: League tiebreakers have been changed to de-emphasize round score as heavily. We have also added additional manual tiebreaking measures.

Clarifications & Addressing Issues

  • Late Roster Signups will not be allowed past the seedings, period. The conditions where late signups can be safely entered into an active season are so unlikely that we will just be ruling it out entirely.
  • Rosters who wish to disband, disband. We will no longer be restoring rosters, even within the same round. The process of disbanding will now be irreversible.
  • ozfortress is now trialling "Trial Admins". Trial Admins within ozfortress will act with the full capacity and ability of League Admins. The new role is merely to indicate newer staff members.
  • Round bans from Infractions and/or League Penalties will now be recorded in the Team Captain Discord.
  • Transfers will now be manually listed publicly within the Team Captain Discord and that season's league page. This process will be entirely manual for now, so we ask for some lenience whilst we get in the swing of doing this consistently.
  • If a division is using Round Robin, all matches will be generated at the beginning of the season.
  • Mercenary approval or denial by league administrators in the case of a dispute will be purely based comparatively on the player that the mercenary is replacing.
    • This is not a requirement for teams when negotiating mercenaries with each other, but will be the primary consideration for us when resolving disputes.
  • End-of-season awards requirements are being changed. Teams may no longer be required to nominate their players but are required to submit votes. Please note however, we do expect a reason from team captains as to why they do not wish to nominate their players, and it is up to our discretion as to whether or not you will be required to submit nominations for your roster.

Infraction Ruleset Changes

Infraction Threshold Ban Levels Changed

  • Changed: 20 points = 3-Round Match Ban:
    • This ban level was previously set at 30 points, however with fewer Tier 1 and Tier 2 infractions than we had in the past - we feel three Tier 1's before any action is taken is too lenient. Additionally, the Tier 2 infraction for impersonating ozfortress players is still yet to be applied in any case - but we will continue monitoring cases leading to this ban level and make changes if this change appears to be too heavy-handed.
  • Added: 40 points = 6-Round Match Ban:
    • New: For some time, we have been looking to add a less severe, middle-of-the-road ban level that could act as a deterrent without letting behaviour and punishment graduate to a 1-Year Ban. With only one Tier 1 and one Tier 2 infraction, both of which are used far less than the current Tier 3 infractions - we feel this ban level is a second deterrent that has been needed for some time.
  • Unchanged: 60 points = 1-Year League Ban:
    • This ban level is identical to what it was previously.
  • Unchanged: Every +30 points above 60 points is another year:
    • Ban lengths above one year are far rarer these days, and only reserved for large/multiple breaches.
    • Previously, there was a two-year ban level set at a 90-point threshold, however, it operated identically to this, and every 30 points above this threshold was still an extra year in ban length.

Probation Multipliers Updated

The Probation period multipliers have been updated to be 2x across the board, rather than Tier 2's previous multiplier of 1.5x.

Ban Reset Maximum Threshold Lowered

The Ban Resets maximum threshold has been lowered from 90 points to 60 points. This means any offender who receives more than 60 points during their ban will likely have their ban extended at the discretion of the Behaviour Panel. We've made this change to ensure we can effectively remove bad seeds from our community.

Infraction Offences Updated/Reworded

Going forward, we're working to ensure every part of our ruleset has a purpose, minimizing any confusing overlap. 

  • The previous "General bigotry/use of derogatory slurs" infraction, along with the "Discrimination of any kind" infraction, have been combined into one infraction. This is in a general effort to simplify the ruleset, but to also ensure every offence encompasses its own potential behaviour breaches.
    • "Bigoted, derogatory or discriminatory remarks of any kind. Some examples are:
      • Racism
      • Sexism
      • Homophobia
      • Transphobia"
  • "Impersonation/implied affiliation of ozfortress staff" infraction has been reworded to emphasize maliciousness.
    • "Malicious impersonation or implied affiliation with ozfortress staff."
  • "Impersonating an ozfortress player" Tier 2 infraction has been reworded.
    • "Malicious impersonation of ozfortress players."
  • Witch-hunting example removed from "Repeated serious abuse/harassment" infraction. Please note that witch-hunting is still considered harassment, but it alone as the only example often overshadows what this infraction is meant to encompass.

Behaviour Reporting

We want to remind everyone to report poor behaviour that they see. We aren't omniscient, so even if you think we may have seen it, please still report it. Additionally, we do not go out of our way to hunt for infractable behaviour. If it's not reported to us, we won't know. The only exception to this logic is those who are dumb enough to drop it in our laps on our website or in our discord.

Behaviour Panel Lead Role Dissolved

The Behaviour Panel Lead role will be dissolved, in favour of allowing myself, Head Admins and Public Behaviour Panel Members to process and issue infractions.

We're looking for Behaviour Panel Members

If you think you may be a good fit for the Behaviour Panel, please apply!

Game Server Bans Becoming Automated

A pain point for some is how inconsistent game server bans are for those who are banned. This process has always been entirely manual, meaning it was often reliant on me (core) to set reminders to ban/unban players. So, starting soon we'll be significantly improving this process, so all that will need to happen is for either myself or someone with permission to add a ban, and it will start/end by itself. Additionally, we're changing the length of game server bans to allow banned players to begin reintegrating into the community. We feel it's important for us to recognize that we are in a position unique to our league, as we are the only server provider - so we're making the following changes:

  • Regardless of the ban length (excluding 3-Round Match Bans and 6-Round Match Bans), in the last three months of the league ban, banned players will be able to join servers once again, but will be muted on the server. We're open to feedback on this, so if you want to chat, contact core directly.
Posted about 1 month ago
- edited about 1 month ago
Link
Thread: ozfortress Bans: June 2024
core League Director

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.

Posted about 1 month ago
Link
Thread: Important Notice Regarding Roster Sizes for Sixes/Highlander Winter '24
core League Director

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.

Posted about 1 month ago
- edited about 1 month ago
Link
Thread: Ultiduo 18 - Team Placements, Weapon Unlocks / Whitelist, Maps, Servers & Expectations
core League Director

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.

Posted 3 months ago
Link

Competitions

League Partners

Socials