Search the Community
Showing results for tags 'official'.
Found 4 results
Jump server has been updated with new maps and maplist. IP is asiafortress.mooo.com:27050 New Maplist jump_4starters_rc1 jump_abuq jump_annex_v5 jump_aridia jump_aviator jump_ayers2_a8 jump_ayers_v2 jump_azure jump_baqu_a2 jump_bigbutt_b1 jump_bomb jump_bounce jump_cheval jump_collab jump_dystopia jump_edgebug_b2 jump_elysium_v3 jump_endurance_rc2 jump_everest_a2 jump_facility jump_heaven_a3 jump_hopstep_a3 jump_hotcoffee_b1 jump_impact jump_joa_v2 jump_junk_a4 jump_junk_solly_b1 jump_kilo jump_klanana jump_lite_a0 jump_littleman_v3 jump_majoras_a3 jump_momentum jump_mouser jump_natural_b2 jump_propel_fixed_v2 jump_quake_beta4 jump_QuBa jump_rebound_v3 jump_redplanet_v2 jump_rook_beta jump_silly_a12 jump_soar_a4 jump_style jump_tholos jump_twist_beta jump_underground_final jump_who jump_yucca rj_rckteer_adv_v2 jump_sync jump_dink_b2 jump_duey_v2 jump_emulation_alpha jump_ExileNPals jump_flow_alpha2 jump_fruh_a1 jump_foundation_a2 jump_future_rebuild jump_glow_v4 jump_hangar_18 jump_jurf_a2 jump_legion_beta3 jump_lion_a3 jump_pushittothelimit_b3 jump_sexydev_v3 jump_sharp_b3 jump_squared_b2 jump_synth_a2 jump_taylor_swift jump_torii jump_asdf jump_aurora_a3 jump_air_beta2 jump_around_cr jump_cake_b2 jump_contact jump_demolition jump_devils_redo jump_drexen jump_drexen2 jump_fisyx jump_gman_beta_4 jump_hobo jump_hobo2 jump_ice_v4 jump_junk_a4 jump_koi jump_muffin_b4 jump_nbn_b4b jump_puni_a4a jump_pure_b2 jump_revenge jump_ring jump_ring2_a5 jump_scorpion_b1 jump_sheer_final jump_speed2 jump_tissue jump_tsao_final jump_up jump_volcanic jump_what jump_daylight jump_drenched jump_frayb_a4 jump_over_beta jump_shiver jump_sync jump_termywermy_beta2 conc_AandO_b1 conc_arc_b1 conc_retry_a11 conc_school conc_speed_b1 concmap concmap2 concmap3 concmap_cave concmap_exist defrag_pizzanbeer defrag_xelerate quad_meow quad_rocket12 quad_shock quad_tyrant_tf2 quad_tyrant2_tf2 Old Maplist jump_bigbutt_b1 jump_ABuQ jump_allstars jump_annex jump_aridia jump_ayers_v2 jump_ayers2_a8 jump_BAQu_a2 jump_cake_b2 jump_cellshaded_b4 jump_cheval jump_devils_redo jump_dink_b2 jump_drenched jump_dystopia jump_elysium_v3 jump_everest_a2 jump_glow_v4 jump_heaven_a3 jump_heavy_b1 jump_ice_v4 jump_junk_a4 jump_junk_solly_b1 jump_khoa jump_kilo jump_koi jump_klanana Jump_majoras_a3 jump_momentum jump_noob2_ab jump_pagoda jump_QuBa jump_rebound_v3 jump_rook_beta jump_rush jump_sexydev_v3 jump_sharp_b3 jump_sheer_final jump_silly_a12 jump_skip_b3 jump_soar_a4 jump_speed jump_style jump_tholos jump_tissue jump_trix jump_vendetta rj_rckteer rj_rckteer_adv_v2 rj_training_v3 rocket_tower_jump jump_bomb jump_collab jump_legion_beta2 Jump_beef Jump_littleman_v3 jump_adventure jump_noob_a1a
AsiaFortress Administrator and Staff Team Last updated 19th September 2016 by Caldoran The following is a comprehensive list of members in the AsiaFortress Administrator and Staff Team along with their roles and what you should (or should not) contact them for. In general, while we prefer posts on this forum since it provides an open discussion platform and is more convenient, should you require assistance, wish to give feedback or want to report an incident, feel free to contact the appropriate person by referring to the list below. Administrators or Staff with an asterisk (*) beside their name indicates that they are holding multiple positions of varying administrative powers within the team. Casting Team Administrator The Casting Team Administrator is in charge of managing our official Casting Team. If you are interested to help out in our Casting Team as a Caster, Assistant or other roles you think you're suitable for, this is who you should contact. Яednaxela Community Managers These are the people who you should be looking to contact first to give suggestions, feedback and bug reports. Because they are unable to take administrative action in-game, reporting players who have broken rules should be directed towards the General Administrators instead. fwishy vetia* General Administrators General Administrators are the people you should be reporting players who have broken PUG rules to, either in-game when they are present or after the game if necessary. Providing them with demos and other evidence will help greatly in your case. Aqua Apples bait iridescentFUZZ moosepi* Himari oro* vetia* erio iMauriceiNoob Senior Administrators Senior Administrators are in charge of the General Administrators. If you wish to report wrongful behaviour within the Administrators and Staff Team, they are a possible avenue. While General Administrators are more suitable for reporting rule-breaking PUG players, you can also report them to the Senior Administrators if you deem necessary. Hirasagi Gothmog* Jump, MGE and Ultiduo Administrators Jump and MGE/Ultiduo Administrators handle the official AsiaFortress Jump, MGE and Ultiduo servers. You may contact them if you wish to report an outdated plugin, exploitative players or other problems related to those servers. Combustion [Jump] oro [MGE/Ultiduo] Head Administrators You may contact the respective Head Administrators directly to report wrongful behaviour by players in the community, including any AsiaFortress Administrators and Staff. Suggestions, ideas and other concerns are also welcome if you do not feel comfortable contacting the other Administrators and Staff. Teejay [south East Asia and Overall] Competition Administrators You should contact the Competition Administrators in the case of any conflicts or problems that occur during an official AsiaFortress tournament or event. Examples include having difficulties in scheduling matches and reporting rulebreaking/cheating by another team. Competition Administrators have many administrative powers but are only able to use them to ensure official league matches or events go smoothly, and not in PUGs. Hence, you should direct reports of players breaking rules in PUGs to the General Administrators. Teejay [Major Tournaments] Gothmog* [Minor Tournaments and Events] Content Creators These members contribute their creative prowess through things like writeups and artwork. If you wish to join them in expressing your artistic or literary talent, then you should contact a Head Administrator. vetia* [Writeups] moosepi* [Writeups] himari* [Writeups] Cell [Design] Concordia [Design] Robin [Design] League Owner There should be no need to contact the League Owner directly. Crash/bug reports and other suggestions can either be posted in the Forums or directed towards the other Administrators and Staff. natapon
The official asiafortress configs are available for download as attachments below. The latest version of these configs must be used in all asiafortress 6 v 6 based competitions As of now, the latest version is version 1f (30th January 2013). This update is compulsory for all competitions played after AFC 6 The configs will be maintained here. afc_1f.zip
Table of Contents (i) Summary of Changes 1. League Format 1A. Fixtures 1B. Ranking 1C. Key Dates 2. Teams 2A. Joining 2B. Roster 2C. Captain 2D. New Player Additions 2E. Player Transfers 2F. Transfer Widows 2G. Roster Lock 2H. Disbanding 3. Scheduling 3A. Round Schedule 3B. Acceptable Match Times 3C. Negotiating Match Times 3D. Rescheduling 3E. Forfeits 3F. Technical Forfeits 3G. Map Selection 4. Matches 4A. Pre-Match Responsibilities 4B. Minimum Number of Eligible Players 4C. Mercenaries (Regarding Teams) 4CA. Mercenaries (Regarding Mercenary) 4D. Demo Recording 4E. Spectators 4F. Sportsmanship 4G. Class Restrictions 4H. Critical Hits, Damage Spread and Weapon Unlocks 4I. Maps 4IA. Time Based Maps 4IB. Mirrored Maps 4IC. KOTH Maps 4ID. Draws and Golden Cap 4J. Pausing in Game 4K. Post-Match Responsibilities 4L. In-Game Penalties 4M. Disputing a Match 5. Servers 5A. Server Configuration 5B. Acceptable Servers 5C. Foreign Teams 6. Cheating, Exploits and Bans 6A. Exploits 6B. Third Party Software 6C. Malicious Server Administration 6D. Steam Account Sharing 6E. Asiafortress Forum Bans (i) Summary of Changes The Asiafortress Cup: Series 6 ruleset contains changes that teams are required to be familiar with. If clarification is required on any section, contact your AFC6 Division Administrator in #asiafortress on irc.gamesurge.net. Ignorance of the rules will not be taken into consideration if a breach has occurred. Key Changes: The old AFL (Asiafortress League) series is now renamed to AFC (Asiafortress Cup) and its iteration continues as AFC6 (Asiafortress Cup 6). We have made some notable changes the unlocks list. Click here to view allowed unlocks. Servers must be running the AFC6 configs and whitelist to be considered eligible to host matches Key admins still have the power to veto any rule should the need arise. [back To Top] 1. League Format 1A. Fixtures Regular season match fixtures will be posted prior to the start of the season. Fixtures are set at weekly intervals to be played between Sunday and Thursday. Match organisation/discussion threads will be posted roughly two weeks prior to that round's fixtures. Playoffs and finals fixtures and rules will be posted at the conclusion of the regular season. [back To Top] 1B. Ranking Teams may score Match Points from any match. During the regular season teams are ranked by round points. If two teams or more are so tied then additional play-offs may be organised to determine who advances to any finals matches. The following points will be awarded after a match has been completed. Match Points: 2 Points for a round win 1 Point each for a round draw 0 Points for a round loss The top 4 teams qualify for the playoffs. The playoffs rounds are single-elimination best of 3 maps. [back To Top] 1C. Key Dates Click here for afc6 key dates [back To Top] 2. Teams 2A. Joining Teams apply pre-season to enter the league and nominate their desired division. A minimum of six eligible players (refer to section 2B) are required for the application to be considered. Application does not guarantee entry into the league. [back To Top] 2B. Roster To be eligible to participate: Player must be listed on the teams roster thread (can be accessed here.). Players must use a name similar to their asiafortress account name or must match their alias, which can be entered via their roster. Players must have a valid Steam ID set in their user profile (Set your Steam ID here). Players must not be under any exclusion penalties (such as cheating or disbanding). Players and teams CAN BE registered for the afl (asiafortress ladder). [back To Top] 2C. Captain One player from each team must be nominated to act as a captain to represent the team in organising matches and liaising with afc6 Administrators. [back To Top] 2D. New Player Additions Players who are not competing in afc6 are free to join a clan, but only during the player transfer period. Players who are not competing in afc6 but are competing in afl for a different clan are free to apply to join during the transfer window also. [back To Top] 2E. Player Transfers Players who are a member of one afc6 clan and wish to transfer to another may do so, but only during a transfer window. 2F. Transfer Windows The transfer windows will allow players who are a member of a clan competing in afc6 to move to another clan, pending admin approval. While we appreciate the need for clans to add additional players to their roster mid-season, our transfer approvals are based on the legitimacy of the transfer/addition. We aim to provide a league that is fair and competitive and we judge all cases based on that premise. The transfer windows will be 24 hours long and will occur on Wednesday 25th July 2012 & Wednesday 15th August 2012. See the full list of Key Dates for more details. [back To Top] 2G. Roster Lock Rosters will be locked on Sunday 22th July 2012. Rosters will be locked for the entire duration of the season and are only unlocked during the set transfer window period. Whilst the roster lock is in effect, no player additions or transfers are allowed. [back To Top] 2H. Disbanding Teams who disband during the regular season will be denied entry to the next league season. A team that disbands during the league season, only to reform at a later date, will be required to play in the afl for an extended period before being granted entry to another league season. The captain of a disbanded team will not be permitted to lead another team in an asiafortress League. Where responsibility for an imminent disband is the sole fault of the captain, a simple majority of registered team members may elect to nominate a new captain, or remove the captain entirely, at any point of the season. The team at large will then remain unpenalised. To avoid penalty, captains and/or team members should approach League Administrators at the first sign of trouble to work through a solution. [back To Top] 3. Scheduling 3A. Round Schedule The Asiafortress Cup: Series 6 schedules fixtures every week, and all match fixtures will be posted pre-season. Match discussion threads will be posted in the match discussion forum approximately 2 weeks before the upcoming round, for teams to negotiate a suitable day and time for their match. The weekly round fixtures must then be played between the specified Sunday and Thursday of the fixtures schedule. [back To Top] 3B. Acceptable Match Times Generally acceptable match start times for Asiafortress Cup 6 matches are as follows: Greenwich Mean Time +8(GMT): 7:30pm to 10:30pm These times are only general guidelines and teams are given all flexibility in finding mutually beneficial arrangements. However, where two teams are unable to agree on a time, an Administrator will set a match date and time using the above guideline. [back To Top] 3C. Negotiating Match Times Once the match schedule for the round has been posted, teams can begin negotiating with each other to arrange a time and date for their match. It is important to note that only the Clan Leader's can organise the match (as indicated on their team roster). Non Clan Leaders who put forward proposed Times and Days, joking or serious, will be punished. There are two ways this can be done: Teams can make contact with each other through the Asiafortress League Captains Steam Community Group or over other mediums such as IRC if that is more convenient to organise their matches, but the arranged date & time must be posted in the match discussion thread. The lower ranked team is to initially propose (in the match discussion thread) three acceptable (see rule 3A/3B) time & dates for the match and also mention if they are able to organise an acceptable server (see rule 5B) for them. The higher ranked team must then reply and either accept one of the proposed dates or, if none are acceptable, propose three new dates and if they are able to organise a server for them. Repeat if needed until an agreement on the date and time is reached. If it is proving difficult to get in contact with the other team or they are not making a reasonable effort to organise the match with you, please bring it to the attention of your division's Administrator immediately. Once teams have agreed to a date and time, the consent of both teams is required to organise a new date & time. All match details must be finalised in the match thread by 11:59pm on the Thursday prior to the round commencing. This includes the map selections (see3G below). Failure to do so without valid reason will see both teams penalised 1 match point. [back To Top] 3D. Rescheduling If for whatever reason a match cannot be played within the time frame outlined in rule 3A/3B, and both teams consent to a round extension, they are required to contact their division's assigned Administrator as soon as possible for approval. [back To Top] 3E. Forfeits A maximum of one forfeit is permitted in the Asiafortress Cup: Series 6, on the second forfeit a team is considered inactive and removed from the league. Exclusion penalties will then apply for future asiafortress participation. It is the team's responsibility to contact your division's Administrator as soon as possible if there is a change in circumstances that will affect your team's ability to field a team each round. If it's a temporary problem (e.g. if a number of your team will be absent next round) When a forfeit is recorded the team they were scheduled to play will be awarded a default win unless both teams forfeited. [back To Top] 3F. Technical Forfeits A technical forfeit will be awarded in the following circumstances: Technical problems (e.g. Steam connectivity issues) prevent the match being played at the arranged time and the match cannot be rescheduled to a later date within the acceptable time frame outlined in rule 3A/3B. Server/Network problems render the server unplayable and an alternative server cannot be found nor match rescheduled to a later date within the acceptable time frame outlined in rule 3A/3B. A new update is released which alters gameplay of a map significantly during the round which it is scheduled. In the case of a technical forfeit being awarded, teams may opt to reschedule the match, or split the points (awarding three points to each team). Technical forfeits, unlike regular forfeits explained in rule 3E, do not count against a team. [back To Top] 3G. Map Selection In each match thread, the home and away team will be specified as well as the map pool for that round. Maps are fixed for each round. [back To Top] 4. Matches 4A. Pre-match Responsibilities The home team has the responsibility of organising the server should set up the server for the match with the required settings outlined in rule section 5. Once the server is ready, contact the other team via the prior agreed method during the match time negotiation and give them the appropriate server details. Both teams should be in the server and ready to start the match no later than 15 minutes after the agreed match start time. [back To Top] 4B. Minimum Number of Eligible Players Teams must have a minimum of five rostered (i.e. does not include any mercenaries) players ready to start or continue a match. [back To Top] 4C. Mercenaries (Regarding Teams) A maximum of one mercenary may be used during a regular season round, and a maximum of 2 mercenaries per season. No mercenaries are permitted during the playoffs and finals. A mercenary can be used without the permission of the other team if they are a member of a team currently active in the same division or below. If the proposed mercenary is not a member of any team participating in the Asiafortress Cup: Series 6 the opposing team’s captain and your division administrator must agree to allow them to play. The following guidelines apply: It is clearly and honestly communicated to the other team who the mercenary is and why they are being used. A mercenary cannot be used in place of an available eligible player. The mercenary must be named when reporting or confirming results in the match thread. [back To Top] 4CA. Mercenaries (Regarding Mercenary) A mercenary may only play once at most for each team during the season. [back To Top] 4D. Demo Recording It is the home team's responsibility to arrange for a recording STV to be present for their match. If one cannot be arranged or the STV does not record, one player from the home team MUST be able to provide a POV demo (we recommend using P-REC). Demos must be uploaded and published no later than 1 week after the match date. Screen-shots of in-game scoreboard must be taken Any team not submitting either an STV or POV demo within 1 week of the match will be penalised 1 Match point. (Teams new to AFC may receive 1 warning before penalties will arise) All players must be able to provide a POV demo should a dispute arise. Failure to do so may result in penalties. [back To Top] 4E. Spectators Under no circumstances are spectators allowed in a game with the exception of ShoutCasters and League Administrator (unless they are members of either team). A team with more than 6 players in a server will be disqualified. [back To Top] 4F. Sportsmanship Teams participating are required to conduct themselves in a sportsmanlike manner both in the match thread and in the actual game. Global chat during live rounds is restricted to only captains or designated representatives for team management. Any other mm1 use by other team members is prohibited. Point deductions will occur for teams who breach this rule. Decisions made by administrators regarding these disputes are considered final. [back To Top] 4G. Class Restrictions The following class restrictions apply in afc6 1 Medic 1 Demoman 1 Heavy 1 Engineer 1 Spy 2 Scouts 2 Snipers 2 Soldiers 2 Pyros These must be enforced using the 'tf_tournament_classlimit_X' commands. The full listing of these can be found in rule 5A. [back To Top] 4H. Critical Hits, Damage Spread and Weapon Unlocks CriticalHits: Off Damage Spread: Off For a complete list for what unlocks are allowed click here [back To Top] 4I. Map Pools Click here to view the current map pools for afc6. [back To Top] 4IA. Time Based Maps cp_gravelpit asiafortress Leagues use the scoring format of ABBA(AB) to ease calculation of results. A reminder of what ABBA(AB) is: With stopwatch ON. The home team will attack first, the away team will then respond to the home teams attack. Once completed the winning team will receive ONE (1) point. The teams will then switch sides and the away team will set the stopwatch time first, following by the home teams response. The winner of this will receive one point. Draws are not permitted on cp_gravelpit. What this means is that if the map result is 1-1 after ABBA, an additional AB round will be played to determine a map winner. The score is to be reported as how many rounds you win. eg: 2-1, or 2-0. [back To Top] 4IB. Mirrored Maps First to win difference of five or 30 minutes. [back To Top] 4IC. KOTH Maps Best of 7 Rounds / First to 4 round wins. No time limit. [back To Top] 4ID. Draws Map draws in afc6 are allowed (with the exception of koth_pro_viaduct_rc3, koth_ashville_rc1 and cp_gravelpit) Matches are played out over 2 maps with individual map wins being the focus. [back To Top] 4J. Pausing in Game Pausing during a match will now be allowed where players clearly exhibit (technological) performance issues. As a guideline, the pause should not last longer than five minutes before teams attempt to find a replacement. Both teams must give the all clear to un-pause. Excessive use of this function or use for inappropriate matters will be heavily punished. Reporting such inappropriate use should be done as a dispute to a match upon which the League Administrators will make a ruling. [back To Top] 4K. Post-Match Responsibilities Both teams must reply to the match discussion thread with the results of both maps within three hours of the match ending. Screenshots of each map must be attached to the thread. Teams must clearly state who the winner of each map was and by what margins Example: cp_granary: 4-1 execute crew cp_badlands: 3-3 draw If a team has used a mercenary, they must post the mercenaries name in the same post which reports the outcome of the match. If only one team submits results, then they will be accepted without verification, so make sure you either confirm the posted results or challenge them if they are incorrect. In the case of neither team submitting results, a forfeit will be recorded against both teams. A link to the mediacentral page the demo was uploaded to (Read: Section 4D) should be provided in the match thread. [back To Top] 4L. In-Game Penalties Misconduct, including use of mm1, by any members of a team other then the team captain or designated representative for team management will be actively enforced in afc6. Teams found breaching unacceptable behavior or caught intentionally breaking any afc6 rules during live matches will face collective penalties as outlined below. The severity of a breach will be handled case by case. The following guidlines apply: First minor team offence: warning Second team offence: 1 point ladder penalty Repeated or major team offences: technical forfeit (loss of all points won that round) Gross misconduct or cheating: Removal from current and potentially future afc competitions Teams with offending players under probation, see rule 6e, will not be afforded a first-offence warning. [back To Top] 4M. Disputing a Match To lodge a dispute or report misconduct, please contact your division's assigned League Administrator. [back To Top] 5. Servers 5A. Server Configuration Instructions on how to download & install afc6 configs can be found here. [back To Top] 5B. Acceptable Servers To be regarded as acceptable, servers must: Be physically located in Asia, unless the match is between two New Zealand or two Australian based teams. Have the afc6 configs & whitelist installed and be running on sv_pure 2. Admins reserve the right to choose which server a match will be played on. If teams cannot agree on a server, an official asiafortress server must be arranged by contacting an Administrator in #asiafortress on irc.gamesurge.net. If the asiafortress servers are unavailable, gamersun will be the next server to default to. If you require a SourceTV relay, please try to provide us as much notice as possible. For retrieving the automatically recorded SourceTV demos of your match, please following the instructions in this page for asiafortress pug servers or this thread for gamersunited ozfortress bookables. JOIN #OZF-HELP TO BOOK A SERVER [back To Top] 5C. Foreign Teams Any match pitting a foreign team against a local team must use an alternative Asian server, if one is available, that provides a fairer playing field. This server must also meet the acceptable server criteria outlined in rule 5B. It is the foreign team's responsibility to bring this to the attention of the local team when negotiating the match details and book or organise the server in advance. However, if an agreement can not be reached, the match will be played on an asiafortress server. [back To Top] 6. Cheating, Exploits and Bans 6A. Exploits Exploiting game or map bugs or flaws for an unfair advantage, whether they are listed in the rules or not is prohibited. The following is an incomplete list of known unfixed exploits: Exploiting flaws in map design to enter areas that put you underneath or above the map. Causing damage through the Control Point A floor on cp_gravelpit. Building Sentry Guns, Dispensers or Teleporters in indestructable areas. Shooting through gates or walls during the setup phase. Using any map entities to reach areas that cannot be mirrored by the other team in the same situation Using scripts, macros or key combinations that allow you to bypass movement restrictions (e.g. the "Mega Jump" exploit). Any other script which is deemed disruptive to hitboxes or gameplay. Medics changing hat/items/weapons in spawn to back spawn and preserve uber percent. If you are unsure if something is considered an exploit, please contact a League Administrator and request a ruling be made on it. [back To Top] 6B. Third Party Software The use of any third-party addons, hooks, programs or wrappers that interact with or alter the Team Fortress 2 client, its appearance or behaviour for the purposes of gaining an unfair advantage are banned. [back To Top] 6C. Malicious Server Administration The use of any server commands, variables or plugins for the purposes of gaining an unfair advantage or to interfere with an afc6 match is prohibited. Once the match is underway, the server administrator must let the match run its course and not make any changes without the consent of both teams. [back To Top] 6D. Steam Account Sharing A Steam account may only be used by its owner in any afc6 match. Sharing your login details with a third party for use in an afc6 match is strictly prohibited and if found out will result in lengthy bans for all involved parties. [back To Top] 6E. Asiafortress Forum Bans Members who are banned on the asiafortress website are also banned from leading clans in afc6. Players banned from the asiafortress website may also be subject to competition bans, and are considered under probation; see Rule 4L. Please read the infraction information thread for more information. Bans issued that affect a players ability to play will be listed here. Please contact your division's administrator for further clarification. [back To Top]