Jump to content
Upcoming
  • asiafortress cup 14

fwishyy

League Owner
  • Content count

    293
  • Joined

  • Last visited

  • Days Won

    35

Posts posted by fwishyy


  1. Banner.png

    AsiaFortress Cup 18 Key Dates and Map Pool

    [Rules] [Unlocks] [Division Administrators] [Key Dates and Map Pool]

    Key Dates (Division 1):

    Regular Season:

    Week 1 (Gullywash Reckoner)

    2 August 2021 - 8 August 2021

    Week 2 (Reckoner Process)

    9 August 2021 - 15 August 2021

    Week 3 (Process Clearcut) + Transfer Window 1

    16 August 2021 - 22 August 2021

    Week 4 (Clearcut Snakewater)

    23 August 2021 - 29 August 2021

    Week 5 (Snakewater Product)

    30 August 2021 - 5 September 2021 + Transfer Window 2

    Break + Transfer Window 2

    6 September 2021 - 12 September 2021

     

    Playoffs (Top 4):

    Upper Bracket SemiFinals (Best-of-three series)

    13 September 2021 - 19 September 2021

    Upper Bracket Finals / Lower Bracket SemiFinals (Best-of-three Series)

    20 September 2021 - 26 September 2021

    Lower Bracket Finals (Best-of-three series)

    27 September 2021 - 3 October 2021

    Grand Finals (Best-of-five for Division 1 / Best-of-three series for Divisions 2-4)

    4 October 2021 - 10 October 2021

     

     

    Key Dates (Divisions 2-4):

    Regular Season:

    Week 1 (Gullywash Reckoner)

    2 August 2021 - 8 August 2021

    Week 2 (Reckoner Process)

    9 August 2021 - 15 August 2021

    Week 3 (Process Clearcut)

    16 August 2021 - 22 August 2021

    Week 4 (Clearcut Snakewater) + Transfer Window 1

    23 August 2021 - 29 August 2021

    Week 5 (Snakewater Product)

    30 August 2021 - 5 September 2021

    Week 6 (Product Sunshine)

    6 September 2021 - 12 September 2021

    Week 7 (Sunshine Gullywash) + Transfer Window 2

    13 September 2021 - 19 September 2021

     

    Break + Transfer Window 2

    20 September 2021 - 26 September 2021

     

    Playoffs (Top 4):

    Upper Bracket SemiFinals (Best-of-three series)

    27 September 2021 - 3 October 2021

    Upper Bracket Finals / Lower Bracket SemiFinals (Best-of-three Series)

    4 October 2021 - 10 October 2021

    Lower Bracket Finals (Best-of-three series)

    11 October 2021 - 17 October 2021

    Best-of-three series for Divisions 2-4)

    18 October 2021 - 24 October 2021

     

    AsiaFortress Cup 18 will run the following maps:

    • Process (cp_process_f7)
    • Gullywash (cp_gullywash_f3)
    • Snakewater (cp_snakewater_final1)
    • Sunshine (cp_sunshine)
    • Reckoner (cp_reckoner_rc6)
    • Product (koth_product_rcx)
    • Clearcut (koth_clearcut_b15d)

  2. Banner.png

    AsiaFortress Cup Rules

    [Rules] [Unlocks] [Division Administrators] [Key Dates and Map Pool]

    1. Teams and Players

    1a. Registration

    Teams are to register for the AsiaFortress Cup in the designated Registration Thread, adhering strictly to the format provided in the opening post of the thread. Registration must be posted by the captain of the team.

    Registered teams are to observe the following restrictions:

    • A minimum of six and maximum of ten total players, inclusive of team captains.
    • A maximum of one primary captain, maximum of two secondary captains. Captains are responsible for all aspects of team management, including but not limited to scheduling, attending matches, and liaising with AsiaFortress administration in the event of a dispute. The primary captain will be our main point of contact and the secondary captains will be contacted in the event they are uncontactable.
    • Rostered players must not be subject to an active AsiaFortress Cup ban.
    • Rostered captains must not be subject to an active AsiaFortress Cup captain ban.
    • Rostered players must have never received a VAC ban for Team Fortress 2.
    • All teams and rostered players must have appropriate names. If a name is deemed to be inappropriate, the team captain will be informed at the earliest convenience and be given until Division seeding is announced to submit a different name to the AsiaFortress administration. Should the team captain fail to do so within the given timeframe, the AsiaFortress administration will select a different name at their own discretion.
    • Each player may only be on one team's roster.

    1b. Roster Lock and Transfer Windows

    Upon conclusion of registration, rosters will be locked until the Transfer Windows. The first Transfer Window will take place during the fourth week of the regular season, while the second will be during the last week of the regular season.

    Roster changes take effect only after the conclusion of the Transfer Window. In other words, players obtained in the first Transfer Window will only be on the roster from Week 5 onwards, while players obtained in the second will only be on the roster for playoffs. In any given Transfer Window, a maximum of two players may be added to the roster.

    1c. Disbanding

    Teams will be considered inactive and disbanded upon forfeiting three or more of their regular season matches, or upon informing AsiaFortress Administrators of their intent to disband. If a team is disbanded in this fashion, all of their previous opponents will be granted retroactive forfeit wins. We encourage teams having internal troubles to contact a Division Administrator either for aid in resolving said issues or to inform them of the team's disbanding. If Administrators deem (on a case-by-case basis) that a disbanded team has failed to take steps towards avoiding disbandment, the captain will be held responsible by being barred from captaining any AsiaFortress team for one season.

    2. Tournament Format

    2a. Divisions

    Teams will be seeded and then split into 3 divisions based on their players' experience and past results in AsiaFortress competitions. While you may indicate your team's preferred division on the registration form, be aware that this allocation is ultimately done at the discretion of AsiaFortress administration in the interest of maximising competition and is therefore non-negotiable.

    2b. Regular Season

    The regular season will consist of seven weeks, during each of which teams will play two maps. Map ties may occur during the regular season; as such, no Golden Caps will take place during the regular season. The top four teams in each division will proceed to the playoffs.

    Division 1 will play the regular season in a round-robin format, where each team plays each other once. Teams will be ranked first by map wins, then (in the event of a tie) the head to head result between tied teams, then (if said result was also a tie) total round wins.

    Division 2 will play the regular season in the Swiss format, where the next match is determined by the results of previous matches. Teams will be ranked first by match wins, followed by map wins, then (in the event of a tie) the head to head result between tied teams, then (if said result was also a tie) total round wins.

    2c. Playoffs

    The top four teams in each division will enter the playoffs, after being seeded according to their results in the regular season. Playoffs will be in the double elimination format.

    Each playoff match will be a best-of-three, with the exception of the grand finals for Division 1, which will be best-of-five. Teams will alternately ban and pick maps from the provided pool to determine what maps are played in what order. Every map must have a winner, hence Golden Cap rules will be enforced during playoffs.
     
    3. Pre/Post-Match Responsibilities
     
    3a. Scheduling
     
    Match threads will be posted on match.tf on the Monday of each match week. Team captains are to discuss with each other over a medium such as Steam Chat or Discord in hopes of finding a suitable time for the match. Upon agreeing on a time, team captains are to post chat logs on the match thread, clearly indicating the date and time of the match and the agreement of both teams.
     
    Should the opposing team captain fail to respond, team captains may also propose a date and time for the match on the match thread. The responsibility then falls on the opposing team to counter-propose an alternate timing on the match thread before whichever of the following timings is later:
     

    • Friday 23:59 (UTC+8) of the match week
    • 24 hours before the proposed match time

     
    Should the opposing team fail to respond by the stipulated time or reject the proposed match time without counter-proposing, the match time will be fixed at the initially proposed time. In the interests of allowing teams sufficient time to respond, all proposed timings must be a minimum of 24 hours from the time of the proposal post.
     
    If neither team leader makes a scheduling post on the match thread by Friday 2359 (UTC+8), a division administrator will post a match time on the thread. This time will be taken as final unless both team leaders are able to agree on an alternate timing and post chat logs on the thread.
     
    3b. Match Postponement

    The AsiaFortress administration provides key dates prior to the season, and hence teams and players are expected to plan around them and ensure they are free at least once a week for the entire duration of the tournament. As such, postponing matches to be played at a date later than the stipulated match week is strongly discouraged. However, if absolutely necessary, approach one of the division administrators to discuss the postpone as soon as possible, and it will be handled on a case-by-case basis.
     
    If a team wishes to postpone a match, the team leader must make a post on the match thread before a time is fixed. In other words, the postpone must be done either within the stipulated response time to the opposing team’s match proposal, or in the event of the other team not proposing a time, by Friday 2359 (UTC+8). The team postponing must clearly state:

    • When they wish to postpone to (a specific date within the following week)
    • The reason for their postpone
    • Chat logs showing the other team's agreement to playing the match in the indicated week


    3c.  Forfeits
     
    In the event that a team fails to attend or is unable to both attend and postpone any given match, a forfeit win will be awarded to their opponents. A team that forfeits greater than two matches will be treated as inactive, and thus disqualified from the tournament. A team disqualified in this way will then be treated as though it had disbanded, and will face similar penalties.
     
    3d. Map Selection
     
    As mentioned earlier, teams must pick and ban maps for each playoff match. Bans and picks will be done from the whole mappool, with the home team banning one map followed by the away team banning one map. The away team will then pick the first map, followed by the home team picking the second and third map. In the event of a best-of-five series, the away team will decide the remaining map order. This process must be completed by 24 hours before the stipulated match time, else the division administrator will select map order himself and post it on the match thread. If this occurs, map order will then be non-negotiable; it is thus the duty of the team captains involved to ensure that the map selection process is completed in a timely fashion. If the opposing team captain fails to respond within a reasonable timeframe, contact your division administrator. A forfeit will be reported as a 1-0 for each map on the challonge brackets.
     
    3e. Score Reporting
     
    Upon completion of the match, the team captain of the winning team is to post the results on the match thread. Score posts should clearly state the winner, scoreline, and if necessary, mercenaries used for each map, as well as link to the logs of the match. If logs are unavailable, a screenshot of the scoreboard at the end of the map should be provided. Score report posts should be done immediately after match completion.
     
    Please note that scores will be finalised and no longer subject to change 24 hours from the first report post. Team captains are responsible for confirming the correct scoreline is submitted before this deadline — late disputes will not be entertained.
     
    4. Matches
     
    4a. Punctuality and Attendance
     
    Each team is expected to have all their players in the server by at most twenty minutes after the scheduled match time. Should a team fail to adhere to this timing, their opponents may opt to claim a forfeit win.
     
    4b. Mercenaries
     
    In the event that a team cannot field a full team at the stipulated match time for whatever reason, they may elect to bring in an unrostered player to act as a mercenary for said match. During the regular season, mercenary usage is subject to the following restrictions:

    • A maximum of two mercenaries may be used in any given match (i.e. a team must field a bare minimum of four players to play the match)
    • Mercenaries may be used a maximum of six times total throughout the season. Take note that using two mercenaries in a single match will be counted as two usages. Using more will result in a team being treated as inactive, and disbandment penalties will apply.
    • Mercenaries may be chosen without the consent of the other team if they are registered in a team participating in a lower division. This must be accompanied with the approval of any Division Manager. Players who do not fulfill this condition may still be brought in as mercenaries, but only subject to the approval of the opposing team.
    • In all cases, the team using a mercenary must clearly and honestly communicate both the identity of the mercenary and the reason he is being employed.
    • In no circumstance may a mercenary be employed in place of an available rostered player.
    • Mercenaries must be reported together with the scores in the match thread.

     
    During playoffs, a further restriction applies. A maximum of one mercenary per match may be used, and mercenary usage must be approved by the division administrator prior to each usage.
     
    4c. Servers
     
    Any server that has been can load the latest AFC configs and maps may be used. Ideally, a server should have minimal choke, loss, stuttering and ping difference between the two teams. If a server satisfactory for both teams cannot be found, they are to use an official AsiaFortress server that provides the lowest average ping difference. 
     
    4d. Unlocks, Map Pool and Rule Set
     
    AsiaFortress competitions use the global whitelist. Please refer here to familiarise yourself with the weapons allowed.
     
    Classes are limited to two each of Scouts, Soldiers, Snipers, and Spies, and one each of Pyros, Demos, Heavies, Engineers, and Medics.
     
    The map pool can be found in the key dates thread. In the event that the server being used is not running the latest version of a given map, an older version may be played provided that both teams agree.
     
    At the time of this writing, all AsiaFortress maps are either in the 5CP or KOTH format. 5CP maps are to be played to either a time limit of 30 minutes or a difference of five rounds, whichever happens sooner. KOTH maps are to be played as a best of five rounds, with no time limit.
     
    During the regular season, map draws are allowed, hence for 5CP maps, the scoreline at the end of thirty minutes is to be taken as final. During playoffs, each map must have a conclusive winner; in the event of a tie after thirty minutes, a Golden Cap is to be played. The Golden Cap is a single round with no time limit, and whoever wins it will win the map.

    4e. Pausing

    Each team is allowed one pause per map at any time for technical issues. These can include:

    • Player losing connection
    • Server issues

    The reason for pausing must be clearly communicated to the other team before any player on the server may pause.

    Each pause may last a maximum of 5 minutes unless given consent by the opponent team. Once the pause limit is up, the opponent team is allowed to resume the game. The pausing team will face penalties if they do not adhere to the pause limit.

    The game cannot be resumed without giving proper warning to the opponent team.

    5. Offenses and Penalties

    5a. Cheating
     
    Cheating of any kind in an AsiaFortress competition is strictly forbidden. Cheating, here, is defined as either exploiting unintended aspects of the game or employing third-party software to gain an unfair advantage over other players. This includes, but is not limited to:
     

    • Using HUD elements to remove the sniper scope
    • Changing loadout to move back a spawn while retaining Ubercharge
    • Using glitches to deliberately exit the normally playable area of the map
    • Any form of aim assistance

     
    In addition, receiving a VAC ban for TF2 at any time will be treated equivalently to being caught cheating in an official match, and similar penalties will apply.
     
    5b. Alternate Accounts
     
    Usage of alternate accounts is not necessarily forbidden; it is, however, discouraged and subject to a number of restrictions. Alternate accounts may not be used to circumvent active AsiaFortress bans, nor may they be used to disguise one's identity to play in a division lower than their actual skill. Account sharing is also strictly prohibited; a single account may not be used by more than one player in AsiaFortress matches. Conversely, players are also not allowed to have more than one account participating in the same competition. Any violation of the above rules will lead to the player in question and possibly his team being subject to penalties.

    6. Post Season

    6a. Receiving of Medals

    Successful completion of an AsiaFortress Cup season earns players in all participating teams medals. To be eligible for a medal, a player must:

    • Be rostered on a participating AsiaFortress Cup team that did not drop out mid-season
    • Play at least TWO FULL MAPS for the team they are rostered on

    This rule also applies to players acquired through the two Transfer Windows. Thus, if a player decides to transfer to another team, they must play at least one match for the destination team to be eligible for the medal that team receives.


  3. admin_poster.png

    banner by concor

    Hey everyone! As the title mentions, AsiaFortress is looking for help to assist in the upcoming AsiaFortress Cup 18. This time, facing a much bigger shortage of manpower to help out with the league than ever before, we're opening up more positions for community members to take up the mantle and make AsiaFortress the best that it can be. This round, we're once again looking for Division Administrators, the linchpin of the AsiaFortress Cup tournaments.

    You may apply to be a Division Administrator for the upcoming AsiaFortress Cup 18 here!

    Applications will close 19 July 2021 23:59PM GMT+8


    View full article


  4. Registration.png

    banner by concor


    It’s the AsiaFortress Summer Skirmish! The first of its kind, the AsiaFortress Summer Skirmish is a middle-of-the-year tournament that will span an entire weekend and will commence this month on the 19th and 20th of June.

     

    Similar to AsiaFortress Cup, the AsiaFortress Summer Skirmish will be run through the match.tf tournament platform. While the rules will be updated there latest next week, the summary of the tournament format is as follows:

    • Tournament matches each day will be played from 8pm GMT+8 to 10pm GMT+8
    • Teams will compete in a series of 4 best-of-one series on the Sat, 19th June 2021
      • Each series will be a single map, played to 30 minutes, or score difference of 5, whichever comes first
      • No ties. In the event that the scores are tied after 30 minutes, a Golden Cap round will be played
      • If the Golden Cap round does not end within 10 minutes, the team that has control of the middle point will be considered the winner of the map
    • The top 4 teams will advance to a best-of-3 single elimination bracket playoffs on Sun, 20th June 2021
    • Teams must show up to matches no more than 10 minutes after each match, at which point the AsiaFortress Administrators have the right to disqualify them from the tournament

     

    Map Pool:

    • cp_metalworks
    • cp_process_f7
    • cp_reckoner_rc6
    • cp_sunshine
    • koth_product_rcx

    To sign up, head over to here page to sign up! Signups will close on Friday, 18th June 2021 8PM GMT+8, so make sure to sign up before then!


    View full article


  5. Banner.png

    AsiaFortress Cup 17 Division Managers

     

    The following Administrators should be your primary contact for any questions, disputes, and problems you may have with regards to AsiaFortress Cup 17. This includes delaying or rescheduling matches or disputing a match due to a cheating allegation. The steam profiles of the Division Managers have been provided, as well as their discord tags in the AsiaFortress discord.

    Division 1

    Division 2

    • ruee / ruee#3418
    • Takuto / Takuto#9773
    • fwishy / fwishy#0338

    Division 3

    • d4le / dddd4444#9169
    • fwishy / fwishy#0338

  6. Banner.png

    AsiaFortress Cup Rules

    [Rules] [Unlocks] [Division Administrators] [Map Pool]

    1. Teams and Players

    1a. Registration

    Teams are to register for the AsiaFortress Cup in the designated Registration Thread, adhering strictly to the format provided in the opening post of the thread. Registration must be posted by the captain of the team.

    Registered teams are to observe the following restrictions:

    • A minimum of six and maximum of ten total players, inclusive of team captains.
    • A maximum of one primary captain, maximum of two secondary captains. Captains are responsible for all aspects of team management, including but not limited to scheduling, attending matches, and liaising with AsiaFortress administration in the event of a dispute. The primary captain will be our main point of contact and the secondary captains will be contacted in the event they are uncontactable.
    • Rostered players must not be subject to an active AsiaFortress Cup ban.
    • Rostered captains must not be subject to an active AsiaFortress Cup captain ban.
    • Rostered players must have never received a VAC ban for Team Fortress 2.
    • All teams and rostered players must have appropriate names. If a name is deemed to be inappropriate, the team captain will be informed at the earliest convenience and be given until Division seeding is announced to submit a different name to the AsiaFortress administration. Should the team captain fail to do so within the given timeframe, the AsiaFortress administration will select a different name at their own discretion.
    • Each player may only be on one team's roster.

    1b. Roster Lock and Transfer Windows

    Upon conclusion of registration, rosters will be locked until the Transfer Windows. The first Transfer Window will take place during the fourth week of the regular season, while the second will be during the last week of the regular season.

    Roster changes take effect only after the conclusion of the Transfer Window. In other words, players obtained in the first Transfer Window will only be on the roster from Week 5 onwards, while players obtained in the second will only be on the roster for playoffs. In any given Transfer Window, a maximum of two players may be added to the roster.

    1c. Disbanding

    Teams will be considered inactive and disbanded upon forfeiting three or more of their regular season matches, or upon informing AsiaFortress Administrators of their intent to disband. If a team is disbanded in this fashion, all of their previous opponents will be granted retroactive forfeit wins. We encourage teams having internal troubles to contact a Division Administrator either for aid in resolving said issues or to inform them of the team's disbanding. If Administrators deem (on a case-by-case basis) that a disbanded team has failed to take steps towards avoiding disbandment, the captain will be held responsible by being barred from captaining any AsiaFortress team for one season.

    2. Tournament Format

    2a. Divisions

    Teams will be seeded and then split into 3 divisions based on their players' experience and past results in AsiaFortress competitions. While you may indicate your team's preferred division on the registration form, be aware that this allocation is ultimately done at the discretion of AsiaFortress administration in the interest of maximising competition and is therefore non-negotiable.

    2b. Regular Season

    The regular season will consist of seven weeks, during each of which teams will play two maps. Map ties may occur during the regular season; as such, no Golden Caps will take place during the regular season. The top four teams in each division will proceed to the playoffs.

    Division 1 will play the regular season in a round-robin format, where each team plays each other once. Teams will be ranked first by map wins, then (in the event of a tie) the head to head result between tied teams, then (if said result was also a tie) total round wins.

    Division 2 will play the regular season in the Swiss format, where the next match is determined by the results of previous matches. Teams will be ranked first by match wins, followed by map wins, then (in the event of a tie) the head to head result between tied teams, then (if said result was also a tie) total round wins.

    2c. Playoffs

    The top four teams in each division will enter the playoffs, after being seeded according to their results in the regular season. Playoffs will be in the double elimination format.

    Each playoff match will be a best-of-three, with the exception of the grand finals for Division 1, which will be best-of-five. Teams will alternately ban and pick maps from the provided pool to determine what maps are played in what order. Every map must have a winner, hence Golden Cap rules will be enforced during playoffs.
     
    3. Pre/Post-Match Responsibilities
     
    3a. Scheduling
     
    Match threads will be posted on match.tf on the Monday of each match week. Team captains are to discuss with each other over a medium such as Steam Chat or Discord in hopes of finding a suitable time for the match. Upon agreeing on a time, team captains are to post chat logs on the match thread, clearly indicating the date and time of the match and the agreement of both teams.
     
    Should the opposing team captain fail to respond, team captains may also propose a date and time for the match on the match thread. The responsibility then falls on the opposing team to counter-propose an alternate timing on the match thread before whichever of the following timings is later:
     

    • Friday 23:59 (UTC+8) of the match week
    • 24 hours before the proposed match time

     
    Should the opposing team fail to respond by the stipulated time or reject the proposed match time without counter-proposing, the match time will be fixed at the initially proposed time. In the interests of allowing teams sufficient time to respond, all proposed timings must be a minimum of 24 hours from the time of the proposal post.
     
    If neither team leader makes a scheduling post on the match thread by Friday 2359 (UTC+8), a division administrator will post a match time on the thread. This time will be taken as final unless both team leaders are able to agree on an alternate timing and post chat logs on the thread.
     
    3b. Match Postponement

    The AsiaFortress administration provides key dates prior to the season, and hence teams and players are expected to plan around them and ensure they are free at least once a week for the entire duration of the tournament. As such, postponing matches to be played at a date later than the stipulated match week is strongly discouraged. However, if absolutely necessary, approach one of the division administrators to discuss the postpone as soon as possible, and it will be handled on a case-by-case basis.
     
    If a team wishes to postpone a match, the team leader must make a post on the match thread before a time is fixed. In other words, the postpone must be done either within the stipulated response time to the opposing team’s match proposal, or in the event of the other team not proposing a time, by Friday 2359 (UTC+8). The team postponing must clearly state:

    • When they wish to postpone to (a specific date within the following week)
    • The reason for their postpone
    • Chat logs showing the other team's agreement to playing the match in the indicated week


    3c.  Forfeits
     
    In the event that a team fails to attend or is unable to both attend and postpone any given match, a forfeit win will be awarded to their opponents. A team that forfeits greater than two matches will be treated as inactive, and thus disqualified from the tournament. A team disqualified in this way will then be treated as though it had disbanded, and will face similar penalties.
     
    3d. Map Selection
     
    As mentioned earlier, teams must pick and ban maps for each playoff match. Bans and picks will be done from the whole mappool, with the home team banning one map followed by the away team banning one map. The away team will then pick the first map, followed by the home team picking the second and third map. In the event of a best-of-five series, the away team will decide the remaining map order. This process must be completed by 24 hours before the stipulated match time, else the division administrator will select map order himself and post it on the match thread. If this occurs, map order will then be non-negotiable; it is thus the duty of the team captains involved to ensure that the map selection process is completed in a timely fashion. If the opposing team captain fails to respond within a reasonable timeframe, contact your division administrator. A forfeit will be reported as a 1-0 for each map on the challonge brackets.
     
    3e. Score Reporting
     
    Upon completion of the match, the team captain of the winning team is to post the results on the match thread. Score posts should clearly state the winner, scoreline, and if necessary, mercenaries used for each map, as well as link to the logs of the match. If logs are unavailable, a screenshot of the scoreboard at the end of the map should be provided. Score report posts should be done immediately after match completion.
     
    Please note that scores will be finalised and no longer subject to change 24 hours from the first report post. Team captains are responsible for confirming the correct scoreline is submitted before this deadline — late disputes will not be entertained.
     
    4. Matches
     
    4a. Punctuality and Attendance
     
    Each team is expected to have all their players in the server by at most twenty minutes after the scheduled match time. Should a team fail to adhere to this timing, their opponents may opt to claim a forfeit win.
     
    4b. Mercenaries
     
    In the event that a team cannot field a full team at the stipulated match time for whatever reason, they may elect to bring in an unrostered player to act as a mercenary for said match. During the regular season, mercenary usage is subject to the following restrictions:

    • A maximum of two mercenaries may be used in any given match (i.e. a team must field a bare minimum of four players to play the match)
    • Mercenaries may be used a maximum of six times total throughout the season. Take note that using two mercenaries in a single match will be counted as two usages. Using more will result in a team being treated as inactive, and disbandment penalties will apply.
    • Mercenaries may be chosen without the consent of the other team if they are registered in a team participating in a lower division. Players who do not fulfil this condition may still be brought in as mercenaries, but only subject to the approval of the opposing team.
    • In all cases, the team using a mercenary must clearly and honestly communicate both the identity of the mercenary and the reason he is being employed.
    • In no circumstance may a mercenary be employed in place of an available rostered player.
    • Mercenaries must be reported together with the scores in the match thread.

     
    During playoffs, a further restriction applies. A maximum of one mercenary per match may be used, and mercenary usage must be approved by the division administrator prior to each usage.
     
    4c. Servers
     
    Any server that has been can load the latest AFC configs and maps may be used. Ideally, a server should have minimal choke, loss, stuttering and ping difference between the two teams. If a server satisfactory for both teams cannot be found, they are to use an official AsiaFortress server that provides the lowest average ping difference. 
     
    4d. Unlocks, Map Pool and Rule Set
     
    AsiaFortress competitions use the global whitelist. Please refer here to familiarise yourself with the weapons allowed.
     
    Classes are limited to two each of Scouts, Soldiers, Snipers, and Spies, and one each of Pyros, Demos, Heavies, Engineers, and Medics.
     
    The map pool can be found in the key dates thread. In the event that the server being used is not running the latest version of a given map, an older version may be played provided that both teams agree.
     
    At the time of this writing, all AsiaFortress maps are either in the 5CP or KOTH format. 5CP maps are to be played to either a time limit of 30 minutes or a difference of five rounds, whichever happens sooner. KOTH maps are to be played as a best of five rounds, with no time limit.
     
    During the regular season, map draws are allowed, hence for 5CP maps, the scoreline at the end of thirty minutes is to be taken as final. During playoffs, each map must have a conclusive winner; in the event of a tie after thirty minutes, a Golden Cap is to be played. The Golden Cap is a single round with no time limit, and whoever wins it will win the map.

    4e. Pausing

    Each team is allowed one pause per map at any time for technical issues. These can include:

    • Player losing connection
    • Server issues

    The reason for pausing must be clearly communicated to the other team before any player on the server may pause.

    Each pause may last a maximum of 5 minutes unless given consent by the opponent team. Once the pause limit is up, the opponent team is allowed to resume the game. The pausing team will face penalties if they do not adhere to the pause limit.

    The game cannot be resumed without giving proper warning to the opponent team.

    5. Offenses and Penalties

    5a. Cheating
     
    Cheating of any kind in an AsiaFortress competition is strictly forbidden. Cheating, here, is defined as either exploiting unintended aspects of the game or employing third-party software to gain an unfair advantage over other players. This includes, but is not limited to:
     

    • Using HUD elements to remove the sniper scope
    • Changing loadout to move back a spawn while retaining Ubercharge
    • Using glitches to deliberately exit the normally playable area of the map
    • Any form of aim assistance

     
    In addition, receiving a VAC ban for TF2 at any time will be treated equivalently to being caught cheating in an official match, and similar penalties will apply.
     
    5b. Alternate Accounts
     
    Usage of alternate accounts is not necessarily forbidden; it is, however, discouraged and subject to a number of restrictions. Alternate accounts may not be used to circumvent active AsiaFortress bans, nor may they be used to disguise one's identity to play in a division lower than their actual skill. Account sharing is also strictly prohibited; a single account may not be used by more than one player in AsiaFortress matches. Conversely, players are also not allowed to have more than one account participating in the same competition. Any violation of the above rules will lead to the player in question and possibly his team being subject to penalties.

    6. Post Season

    6a. Receiving of Medals

    Successful completion of an AsiaFortress Cup season earns players in all participating teams medals. To be eligible for a medal, a player must:

    • Be rostered on a participating AsiaFortress Cup team that did not drop out mid-season
    • Play at least TWO FULL MAPS for the team they are rostered on

    This rule also applies to players acquired through the two Transfer Windows. Thus, if a player decides to transfer to another team, they must play at least one match for the destination team to be eligible for the medal that team receives.


  7. Banner.png

    AsiaFortress Cup 17 Key Dates and Map Pool

    [Rules] [Unlocks] [Division Administrators] [Map Pool]

     

    Week 1 (Snakewater Gullywash)

    15 March 2021 - 21 March 2021

    Week 2 (Gullywash Sunshine)

    22 March 2021 - 28 March 2021

    Week 3 (Sunshine Process)

    29 March 2021 - 4 April 2021

    Week 4 (Process Product) - Transfer Window 1

    5 April 2021 - 11 April 2021

    Week 5 (Product Reckoner)

    12 April 2021 - 18 April 2021

    Week 6 (Reckoner Clearcut)

    19 April 2021 - 25 April 2021

    Week 7 (Clearcut Snakewater) - Transfer Window 2

    26 April 2021 - 2 May 2021

    Catch-up Week - Transfer Window 2

    3 May 2021 -  9 May 2021

    Upper Bracket SemiFinals

    10 May 2021 -  16 May 2021

    Upper Bracket Finals + Lower Bracket SemiFinals

    17 May 2021 -  23 May 2021

    Lower Bracket Finals

    24 May 2021 -  30 May 2021

    Grand Finals

    31 May 2021 -  6 June 2021

    AsiaFortress Cup 17 will run the following maps:

    • Process (cp_process_f7)
    • Gullywash (cp_gullywash_f3)
    • Snakewater (cp_snakewater_final1)
    • Sunshine (cp_sunshine)
    • Reckoner (cp_reckoner_rc6)
    • Product (koth_product_rcx)
    • Clearcut (koth_clearcut_b15d)

  8. Registration.png

    banner by concor

    [Rules] [Unlocks] [Division Administrators] [Map Pool]

    We're back for 2021! Amidst the global COVID-19 pandemic, we hope that everyone in the community has been staying safe.

    Ready for another season? So are we! This season, we're trying new maps, plugins to make the 6s experience the best it can be.

    Maps: Refresh Project

    The Refresh Project is a competitive take on some of the game's most popular competitive maps. AsiaFortress Cup 17 will be running the refreshed versions of both Process(cp_process_f7) and Gullywash(cp_gullywash_f3)

    Maps: 2 Koth Maps?

    Furthermore, this season, we will be including Clearcut (koth_clearcut_b15d), introducing for the first time ever, a second KOTH map in our rotation.

    Plugins

    We've been behind other league in incorporating these Quality-of-Life plugins into competitive play, but this season AsiaFortress Cup 17 will be providing support for the following plugins:

    - Ramp slides fix: Prevents players from stopping when sliding off ramps
    - Projectiles Collision: Prevent projectiles from being blocked by teammates
    - Consistent Fall Damage: Removes randomness present in TF2's fall damage

    match.tf

    Once again, AsiaFortress Cup 17 will be run through match.tf. We think that the system so far has been rather intuitive and convenient for old and new players alike, and will continue to use it. However, please do make sure to join the AsiaFortress Discord and check the AsiaFortress site as all league news will be posted on both of these platforms.

    Signups, found here, are open until 7th March 2021 2359PM GMT+8, so sign up ASAP!


    View full article


  9. Banner.png

    AsiaFortress Cup Rules

    [Rules] [Unlocks] [Division Administrators] [Key Dates and Map Pool]

    1. Teams and Players

    1a. Registration

    Teams are to register for the AsiaFortress Cup in the designated Registration Thread, adhering strictly to the format provided in the opening post of the thread. Registration must be posted by the captain of the team.

    Registered teams are to observe the following restrictions:

    • A minimum of six and maximum of ten total players, inclusive of team captains.
    • A maximum of one primary captain, maximum of two secondary captains. Captains are responsible for all aspects of team management, including but not limited to scheduling, attending matches, and liaising with AsiaFortress administration in the event of a dispute. The primary captain will be our main point of contact and the secondary captains will be contacted in the event they are uncontactable.
    • Rostered players must not be subject to an active AsiaFortress Cup ban.
    • Rostered captains must not be subject to an active AsiaFortress Cup captain ban.
    • Rostered players must have never received a VAC ban for Team Fortress 2.
    • All teams and rostered players must have appropriate names. If a name is deemed to be inappropriate, the team captain will be informed at the earliest convenience and be given until Division seeding is announced to submit a different name to the AsiaFortress administration. Should the team captain fail to do so within the given timeframe, the AsiaFortress administration will select a different name at their own discretion.
    • Each player may only be on one team's roster.

    1b. Roster Lock and Transfer Windows

    Upon conclusion of registration, rosters will be locked until the Transfer Windows. The first Transfer Window will take place during the fourth week of the regular season, while the second will be during the last week of the regular season.

    Roster changes take effect only after the conclusion of the Transfer Window. In other words, players obtained in the first Transfer Window will only be on the roster from Week 5 onwards, while players obtained in the second will only be on the roster for playoffs. In any given Transfer Window, a maximum of two players may be added to the roster.

    1c. Disbanding

    Teams will be considered inactive and disbanded upon forfeiting three or more of their regular season matches, or upon informing AsiaFortress Administrators of their intent to disband. If a team is disbanded in this fashion, all of their previous opponents will be granted retroactive forfeit wins. We encourage teams having internal troubles to contact a Division Administrator either for aid in resolving said issues or to inform them of the team's disbanding. If Administrators deem (on a case-by-case basis) that a disbanded team has failed to take steps towards avoiding disbandment, the captain will be held responsible by being barred from captaining any AsiaFortress team for one season.

    2. Tournament Format

    2a. Divisions

    Teams will be seeded and then split into 3 divisions based on their players' experience and past results in AsiaFortress competitions. While you may indicate your team's preferred division on the registration form, be aware that this allocation is ultimately done at the discretion of AsiaFortress administration in the interest of maximising competition and is therefore non-negotiable.

    2b. Regular Season

    The regular season will consist of seven weeks, during each of which teams will play two maps. Map ties may occur during the regular season; as such, no Golden Caps will take place during the regular season. The top four teams in each division will proceed to the playoffs.

    Division 1 will play the regular season in a round-robin format, where each team plays each other once. Teams will be ranked first by map wins, then (in the event of a tie) the head to head result between tied teams, then (if said result was also a tie) total round wins.

    Division 2 will play the regular season in the Swiss format, where the next match is determined by the results of previous matches. Teams will be ranked first by match wins, followed by map wins, then (in the event of a tie) the head to head result between tied teams, then (if said result was also a tie) total round wins.

    2c. Playoffs

    The top four teams in each division will enter the playoffs, after being seeded according to their results in the regular season. Playoffs will be in the double elimination format.

    Each playoff match will be a best-of-three, with the exception of the grand finals for Division 1, which will be best-of-five. Teams will alternately ban and pick maps from the provided pool to determine what maps are played in what order. Every map must have a winner, hence Golden Cap rules will be enforced during playoffs.
     
    3. Pre/Post-Match Responsibilities
     
    3a. Scheduling
     
    Match threads will be posted on match.tf on the Monday of each match week. Team captains are to discuss with each other over a medium such as Steam Chat or Discord in hopes of finding a suitable time for the match. Upon agreeing on a time, team captains are to post chat logs on the match thread, clearly indicating the date and time of the match and the agreement of both teams.
     
    Should the opposing team captain fail to respond, team captains may also propose a date and time for the match on the match thread. The responsibility then falls on the opposing team to counter-propose an alternate timing on the match thread before whichever of the following timings is later:
     

    • Friday 23:59 (UTC+8) of the match week
    • 24 hours before the proposed match time

     
    Should the opposing team fail to respond by the stipulated time or reject the proposed match time without counter-proposing, the match time will be fixed at the initially proposed time. In the interests of allowing teams sufficient time to respond, all proposed timings must be a minimum of 24 hours from the time of the proposal post.
     
    If neither team leader makes a scheduling post on the match thread by Friday 2359 (UTC+8), a division administrator will post a match time on the thread. This time will be taken as final unless both team leaders are able to agree on an alternate timing and post chat logs on the thread.
     
    3b. Match Postponement

    The AsiaFortress administration provides key dates prior to the season, and hence teams and players are expected to plan around them and ensure they are free at least once a week for the entire duration of the tournament. As such, postponing matches to be played at a date later than the stipulated match week is strongly discouraged. However, if absolutely necessary, approach one of the division administrators to discuss the postpone as soon as possible, and it will be handled on a case-by-case basis.
     
    If a team wishes to postpone a match, the team leader must make a post on the match thread before a time is fixed. In other words, the postpone must be done either within the stipulated response time to the opposing team’s match proposal, or in the event of the other team not proposing a time, by Friday 2359 (UTC+8). The team postponing must clearly state:

    • When they wish to postpone to (a specific date within the following week)
    • The reason for their postpone
    • Chat logs showing the other team's agreement to playing the match in the indicated week


    3c.  Forfeits
     
    In the event that a team fails to attend or is unable to both attend and postpone any given match, a forfeit win will be awarded to their opponents. A team that forfeits greater than two matches will be treated as inactive, and thus disqualified from the tournament. A team disqualified in this way will then be treated as though it had disbanded, and will face similar penalties.
     
    3d. Map Selection
     
    As mentioned earlier, teams must pick and ban maps for each playoff match. Bans and picks will be done from the whole mappool, with the home team banning one map followed by the away team banning one map. The away team will then pick the first map, followed by the home team picking the second and third map. In the event of a best-of-five series, the away team will decide the remaining map order. This process must be completed by 24 hours before the stipulated match time, else the division administrator will select map order himself and post it on the match thread. If this occurs, map order will then be non-negotiable; it is thus the duty of the team captains involved to ensure that the map selection process is completed in a timely fashion. If the opposing team captain fails to respond within a reasonable timeframe, contact your division administrator. A forfeit will be reported as a 1-0 for each map on the challonge brackets.
     
    3e. Score Reporting
     
    Upon completion of the match, the team captain of the winning team is to post the results on the match thread. Score posts should clearly state the winner, scoreline, and if necessary, mercenaries used for each map, as well as link to the logs of the match. If logs are unavailable, a screenshot of the scoreboard at the end of the map should be provided. Score report posts should be done immediately after match completion.
     
    Please note that scores will be finalised and no longer subject to change 24 hours from the first report post. Team captains are responsible for confirming the correct scoreline is submitted before this deadline — late disputes will not be entertained.
     
    4. Matches
     
    4a. Punctuality and Attendance
     
    Each team is expected to have all their players in the server by at most twenty minutes after the scheduled match time. Should a team fail to adhere to this timing, their opponents may opt to claim a forfeit win.
     
    4b. Mercenaries
     
    In the event that a team cannot field a full team at the stipulated match time for whatever reason, they may elect to bring in an unrostered player to act as a mercenary for said match. During the regular season, mercenary usage is subject to the following restrictions:

    • A maximum of two mercenaries may be used in any given match (i.e. a team must field a bare minimum of four players to play the match)
    • Mercenaries may be used a maximum of six times total throughout the season. Take note that using two mercenaries in a single match will be counted as two usages. Using more will result in a team being treated as inactive, and disbandment penalties will apply.
    • Mercenaries may be chosen without the consent of the other team if they are registered in a team participating in a lower division. Players who do not fulfil this condition may still be brought in as mercenaries, but only subject to the approval of the opposing team.
    • In all cases, the team using a mercenary must clearly and honestly communicate both the identity of the mercenary and the reason he is being employed.
    • In no circumstance may a mercenary be employed in place of an available rostered player.
    • Mercenaries must be reported together with the scores in the match thread.

     
    During playoffs, a further restriction applies. A maximum of one mercenary per match may be used, and mercenary usage must be approved by the division administrator prior to each usage.
     
    4c. Servers
     
    Any server that has been can load the latest AFC configs and maps may be used. Ideally, a server should have minimal choke, loss, stuttering and ping difference between the two teams. If a server satisfactory for both teams cannot be found, they are to use an official AsiaFortress server that provides the lowest average ping difference. 
     
    4d. Unlocks, Map Pool and Rule Set
     
    AsiaFortress competitions use the global whitelist. Please refer here to familiarise yourself with the weapons allowed.
     
    Classes are limited to two each of Scouts, Soldiers, Snipers, and Spies, and one each of Pyros, Demos, Heavies, Engineers, and Medics.
     
    The map pool can be found in the key dates thread. In the event that the server being used is not running the latest version of a given map, an older version may be played provided that both teams agree.
     
    At the time of this writing, all AsiaFortress maps are either in the 5CP or KOTH format. 5CP maps are to be played to either a time limit of 30 minutes or a difference of five rounds, whichever happens sooner. KOTH maps are to be played as a best of five rounds, with no time limit.
     
    During the regular season, map draws are allowed, hence for 5CP maps, the scoreline at the end of thirty minutes is to be taken as final. During playoffs, each map must have a conclusive winner; in the event of a tie after thirty minutes, a Golden Cap is to be played. The Golden Cap is a single round with no time limit, and whoever wins it will win the map.

    4e. Pausing

    Each team is allowed one pause per map at any time for technical issues. These can include:

    • Player losing connection
    • Server issues

    The reason for pausing must be clearly communicated to the other team before any player on the server may pause.

    Each pause may last a maximum of 5 minutes unless given consent by the opponent team. Once the pause limit is up, the opponent team is allowed to resume the game. The pausing team will face penalties if they do not adhere to the pause limit.

    The game cannot be resumed without giving proper warning to the opponent team.

    5. Offenses and Penalties

    5a. Cheating
     
    Cheating of any kind in an AsiaFortress competition is strictly forbidden. Cheating, here, is defined as either exploiting unintended aspects of the game or employing third-party software to gain an unfair advantage over other players. This includes, but is not limited to:
     

    • Using HUD elements to remove the sniper scope
    • Changing loadout to move back a spawn while retaining Ubercharge
    • Using glitches to deliberately exit the normally playable area of the map
    • Any form of aim assistance

     
    In addition, receiving a VAC ban for TF2 at any time will be treated equivalently to being caught cheating in an official match, and similar penalties will apply.
     
    5b. Alternate Accounts
     
    Usage of alternate accounts is not necessarily forbidden; it is, however, discouraged and subject to a number of restrictions. Alternate accounts may not be used to circumvent active AsiaFortress bans, nor may they be used to disguise one's identity to play in a division lower than their actual skill. Account sharing is also strictly prohibited; a single account may not be used by more than one player in AsiaFortress matches. Conversely, players are also not allowed to have more than one account participating in the same competition. Any violation of the above rules will lead to the player in question and possibly his team being subject to penalties.

    6. Post Season

    6a. Receiving of Medals

    Successful completion of an AsiaFortress Cup season earns players in all participating teams medals. To be eligible for a medal, a player must:

    • Be rostered on a participating AsiaFortress Cup team that did not drop out mid-season
    • Play at least TWO FULL MAPS for the team they are rostered on

    This rule also applies to players acquired through the two Transfer Windows. Thus, if a player decides to transfer to another team, they must play at least one match for the destination team to be eligible for the medal that team receives.


  10. Banner.png

    AsiaFortress Cup 16 Division Managers

    [Rules] [Unlocks] [Division Administrators] [Key Dates and Map Pool]

    The following Administrators should be your primary contact for any questions, disputes, and problems you may have with regards to AsiaFortress Cup 16. This includes delaying or rescheduling matches or disputing a match due to a cheating allegation. The steam profiles of the Division Managers have been provided, as well as their discord tags in the AsiaFortress discord.

    Division 1

    Division 2

    • ruee / ruee#3418
    • Takuto / Takuto#9773
    • fwishy / fwishy#0338

    Division 3

    • d4le / dddd4444#9169
    • fwishy / fwishy#0338

     


  11. Banner.pngAsiaFortress Cup 16 Key Dates and Map Pool

    [Rules] [Unlocks] [Division Administrators] [Key Dates and Map Pool]

    Key Dates

    Registration Open

    • 22 January 2020

    Registration Close

    • 9 February 2020

    Week 1 (Process Snakewater)

    • 2 March 2020 - 8 March 2020

    Week 2 (Snakewater Gullywash)

    •  9 March 2020 - 15 March 2020

    Week 3 (Gullywash Sunshine)

    • 16 March 2020 - 22 March 2020

    Week 4 (Sunshine Product) / Transfer Window 1

    •  23 March 2020 - 29 March 2020

    Week 5 (Product Granary)

    • 30 March 2020 - 5 April 2020

    Week 6 (Granary Reckoner) / Transfer Window 2

    • 6 April 2020 - 12 April 2020

    Notes

    Division 1 will end after 6 weeks due to only have four teams. As such the following will be used to denote Division 1 schedules and Division 2/3 schedules

    Catchup Week + Transfer Window 2 / Week 7 (Reckoner Process) + Transfer Window 2

    • 13 April 2020 - 19 April 2020

    Playoffs Upper Bracket Semifinals / Catch-up Week + Transfer Window 2

    • 20 April 2020 - 26 April 2020

    Playoffs Upper Bracket Finals and Playoffs Lower Bracket Semifinals/ Playoffs Upper Bracket Semifinals

    • 27 April 2020 - 3 May 2020

    Lower Bracket Finals / Playoffs Upper Bracket Finals and Playoffs Lower Bracket Semifinals

    • 4 May 2020 - 10 May 2020

    Grand Finals / Lower Bracket Finals

    • 11 May 2020 - 17 May 2020

    Grand Finals

    • 18 May 2020 - 24 May 2020

    Map Pool

    • Process (cp_process_final)
    • Snakewater (cp_snakewater_final1)
    • Gullywash (cp_gullywash_final1)
    • Sunshine (cp_sunshine)
    • Product (koth_product_rcx)
    • Granary (cp_granary_pro_rc8)
    • Reckoner (cp_reckoner_rc4a)

  12. Banner.png

    banner by concor

     

    Happy New Year everyone! With the new year upon us, we’re back with the 16th installment of the AsiaFortress Cup. This year we’re determined not to start three months late, and thus here we are!

     

    Map Pool and Whitelist

    Each season, the league aims to keep the map pool exciting by rotating and bringing in new maps. Last season, cp_propaganda_b14 was not the most well-received maps. Therefore, this season, we’re letting everyone vote for the last map that will go into the AsiaFortress Cup 16 map pool.

     

    The poll will feature one experimental map that has not been played in AsiaFortress since its initial release during Mercenary Cup 6, cp_logjam, as well as refreshed old maps like cp_prolands and cp_granary_pro. Players vote for the map they would like to see in the AsiaFortress Cup 16 map pool here. Polling with close together with signups.

     

    Pending Rule Updates

    As of this post, the AsiaFortress Administrators are still looking over the ruleset, striving to create a stronger and fairer set of rules. We urge teams, especially team leaders to keep a look out for any changes made, and thank everyone for their patience while we look through them!

     

    Match.tf

    Continuing from last season, AsiaFortress Cup 16 will be run on match.tf. With one season under our belt, the AsiaFortress Administrators aim to provide an even smoother tournament experience this season!

     

    Teams can sign up for the tournament through match.tf here! Signups will end on 2nd February 2020.


    View full article


  13. image.png

     

    (banner by concor)

     

    Hi everyone, as the title says, AsiaFortress is looking for willing community members to assist in the upcoming AsiaFortress Cup 16.

     

    For the past 15 seasons, AsiaFortress has continued to rely on the efforts of people who have stepped up to the task of making this community a better place. Before I dive into the recruitment details, I would like to thank every single person who has contributed in some way to put the league where it is today. Unfortunately, this also includes the various AsiaFortress Administrators who have recently departed their duties due to external commitments. For some, despite having long left their competitive Team Fortress 2 days behind, continued to serve as advisors to myself, and stepping up to leadership positions in a community they no longer actively benefited from. Fearing I will leave some people out, I will refrain from naming every single one of them (there are too many to count), but I have the utmost gratitude and respect for all of them.

     

    As such, AsiaFortress is currently facing a shortage of manpower, even more so than before. Therefore, we are once again looking to the community for members whom these past administrators may pass the baton to.

     

    The foundation of the AsiaFortress Cup lies in its Division Adminstrators. These are the people to turn to for any questions regarding the league. During the tournament, they are responsible for enforcing the rules, and ensuring match disputes are judged and dealt with in a fair manner.

     

    We are looking for disciplined individuals who are strong and willing communicators to take up this position.

     

    If you are interested, please fill out the form here.

     

    Applications will close on the 29th of December!


    View full article


  14. AF#0: connect sg2.asiafortress.com:27080
    AF#1: connect sg2.asiafortress.com:27081
    AF#2: connect sg2.asiafortress.com:27082
    AF#3: connect sg2.asiafortress.com:27083
    AF#4: connect sg1.asiafortress.com:27084
    AF#5: connect sg1.asiafortress.com:27085

     

    Server STVs have been updated!


  15.  

    afc15_banner.png

    AsiaFortress Cup 15

    [Rules] [Unlocks] [Division Administrators] [Key Dates and Map Pool]

     

     

    After a painstaking three month delay, we welcome everyone back to the fifteenth installment of the AsiaFortress Cup!

    Having made huge changes, make sure all of you read to the end of the post to ensure you don't miss anything out. With that, let's kick start the list of changes.

    Map Pool and Whitelist Updates
    To keep the map pool fresh season after season, we want to keep experimenting with new maps. Therefore, this season, we are introducing cp_propaganda_b14! We will also be welcoming back to the map pool, an updated cp_reckoner_rc4a which hasn't been played since AFC11. Make sure to start practicing these maps. In their place, cp_sunshine and cp_granary_pro2 have been removed from the mappool.
    Whitelist changes are inclusive of the banning of both The Scorch Shot and the Detonator, in accordance with the global whitelist update. Other than that, there will be no major changes to the whitelist.

    Migration to Match.tf
    We are always trying to improve user experience and with the gracious provision of match.tf services, we are experimenting on doing just that. For AsiaFortress Cup 15, the match system will be ported over to match.tf! We hope this will allow for a smoother registration and score submission process for both present and future seasons.
    To sign up on match.tf:
    1) Ensure all of your team members have a match.tf account
    2) Create a team on match.tf here
    3) Add players to your team
    4) Head over here, to sign your team up
    Signups are open until the 24th of March!

    Roster sizes are still limited to 10 players, with a minimum of 6 players required to sign up. Captain bans and player bans found on the list here still apply.

    Do note that as this is our first season utilizing the match.tf system, technical difficulties are bound to happen. We ask for your understanding as the AsiaFortress Admins learn and fine-tune the system. Thank you.

    So what are all of you waiting for, head over to match.tf to sign up now!


    View full article


  16. afc15_banner.png

    AsiaFortress Cup 15 Server Bookings

     

    [Rules] [Unlocks] [Division Administrators] [Key Dates and Map Pool]

    [Server Bookings] [Match Threads] [Cast Requests] [Ban List]

     

    Due to foreseen server usage conflicts, we have created this thread for team leaders to book official AsiaFortress servers for their official AFC 15 matches.

     

    While this is not compulsory, booking a server will be to your team's advantage as you will be given priority to use the server by AsiaFortress administrators.

     

    Please note the following:

    • Servers can only be booked for official AFC 15 matches. Teams found to have booked the servers for their personal usage (i.e. scrims) will be penalized
    • If your team does not show up within 15 minutes after the scheduled time, your booking will be considered invalid and other teams/players may use the server instead
    • Server bookings can last for at most 3 hours
    • One team is only allowed to book one server per day
    • You are expected to post in this thread to make known you have released a booked server if your match is cancelled, forfeited or rescheduled

    Follow the format below to book a server for your match:

    Follow the format below to book a server for your match:
    Name:
    Team Name:
    Team Playing Against:
    Server Area (SG/HK):
    Server # (0/1/2/3/4/5):
    Booking Start Time:
    Booking End Time:
    Any Remarks: 

  17.  

    afc15_banner.png

    AsiaFortress Cup 15 Key Dates and Map Pool

     

    [Rules] [Unlocks] [Division Administrators] [Key Dates and Map Pool]

    [Server Bookings] [Match Threads] [Cast Requests] [Ban List]

     

    Key Dates

    Registration Open

    • 3 March 2019

    Registration Close

    • 24 March 2019

    Week 1 (Gullywash Snakewater)

    • 1 April 2019 - 7 April 2019

    Week 2 (Snakewater Process)

    •  8 April 2019 - 14 April 2019

    Week 3 (Process Prolands)

    • 15 April 2019 - 21 April 2019

    Week 4 (Prolands Reckoner)

    •  22 April 2019 - 28 April 2019

    Transfer Window 1

    • 22 April 2019 - 28 April 2019

    Week 5 (Reckoner Product)

    • 29 April 2019 - 5 May 2019

    Week 6 (Product Propaganda)

    • 6 May 2019 - 12 May 2019

    Week 7 (Propaganda Gullywash)

    • 13 May 2019 - 19 May 2019

    Catch-up Week and Transfer Window 2

    • 20 May 2019 - 26 May 2019

    Playoffs Upper Bracket Semifinals

    • 27 May 2019 - 2 June 2019

    Playoffs Upper Bracket Finals and Playoffs Lower Bracket Semifinals

    • 3 June 2019 - 9 June 2019

    Lower Bracket Finals

    • 10 June 2019 - 16 June 2019

    Grand Finals

    • 17 June 2019 - 23 June 2019

    Map Pool

    • Prolands (cp_prolands_rc2p)
    • Process (cp_process_final)
    • Gullywash (cp_gullywash_final1)
    • Reckoner (cp_reckoner_rc4a)
    • Product (koth_product_rc9)
    • Snakewater (cp_snakewater_final1)
    • Propaganda (cp_propaganda_b14)

     

×