Frag-o-Matic26.0

Home
/ Tournaments
/ GRAND - CS:GO
/ Team

Team name: BASTARDS.AF9K
Team status: Complete
Compo: GRAND - CS:GO
Compo status: Brackets in progress

TEAM Members

Poederbaas

Leader Seat : I-5

Kyo

Member Seat : I-7

DeurneWest

Member Seat : I-4

Rupel

Member Seat : G-35

KM.

Member Seat : G-36

yookes

Member Seat : I-2

WARS OF BASTARDS.AF9K

Compo	Opponent	Score
5v5 GRAND - CS:GO	SM1L3RS	0 - 16 SM1L3RS VS BASTARDS.AF9K
5v5 GRAND - CS:GO	Schizophrenic	2 - 0 Schizophrenic VS BASTARDS.AF9K
5v5 GRAND - CS:GO	iNTERMiXED	1 - 0 iNTERMiXED VS BASTARDS.AF9K
5v5 GRAND - CS:GO	Vlamski	6 - 16 BASTARDS.AF9K VS Vlamski
5v5 GRAND - CS:GO	Born2Throw	4 - 16 BASTARDS.AF9K VS Born2Throw
5v5 GRAND - CS:GO	Pertinax eSports	1 - 16 BASTARDS.AF9K VS Pertinax eSports

History
+

Request History

No previous requests logged.

====
Session
+
Session
- Config(array)
  userAgent2d719f172f7f358731866d9b421abf46
  time1755003345
  countdown10
- nrMessages0
====
Request
+
Request

Cake Params
- plugin(null)
- controllerteams
- actionview
- named(empty)
- pass(array)
  010265
- isAjax(false)
Post data

No post data.

Query string

No querystring data.

Cookie
- 0(empty)
Current Route
- keys(array)
  0controller
  1action
- options(empty)
- defaults(array)
  plugin(null)
- template/:controller/:action/*
====

Sql Log

Sql Logs

default

Total Time: 37 ms
Total Queries: 36 queries

Query	Affected	Num. rows	Took (ms)	Actions
SELECT `MenuItem`.`id`, `MenuItem`.`title`, `MenuItem`.`type`, `MenuItem`.`link`, `MenuItem`.`layout`, `MenuItem`.`enabled` FROM `fom_site`.`menu_items` AS `MenuItem` WHERE `MenuItem`.`enabled` = '1'	5	5	0
SELECT `MenuSubItem`.`id`, `MenuSubItem`.`menu_item_id`, `MenuSubItem`.`title`, `MenuSubItem`.`layout_position`, `MenuSubItem`.`enabled` FROM `fom_site`.`menu_sub_items` AS `MenuSubItem` WHERE `MenuSubItem`.`enabled` = '1' AND `MenuSubItem`.`menu_item_id` IN (1, 2, 3, 4, 5)	9	9	0
SELECT `MenuLink`.`id`, `MenuLink`.`menu_sub_item_id`, `MenuLink`.`title`, `MenuLink`.`url`, `MenuLink`.`link_type`, `MenuLink`.`internal_compo_id`, `MenuLink`.`internal_newspost_id`, `MenuLink`.`internal_content_id`, `MenuLink`.`target`, `MenuLink`.`image`, `MenuLink`.`position`, `MenuLink`.`enabled` FROM `fom_site`.`menu_links` AS `MenuLink` WHERE `MenuLink`.`enabled` = '1' AND `MenuLink`.`menu_sub_item_id` IN (1, 2, 3, 4, 5, 6, 7, 8, 9)	35	35	0
SELECT `Config`.`id`, `Config`.`currentEvent`, `Config`.`contactEmail`, `Config`.`technicalContactEmail`, `Config`.`organisationStreet`, `Config`.`organisationNr`, `Config`.`organisationZip`, `Config`.`organisationCity`, `Config`.`organisationCountry`, `Config`.`organisationWebsite`, `Config`.`organisationName`, `Config`.`vatNr`, `Config`.`bankAccount`, `Config`.`bic`, `Config`.`iban`, `Config`.`paypal`, `Config`.`cartLifeTime`, `Config`.`orderLifeTime`, `Config`.`orderWarningTime`, `Config`.`defaultNoProductImage`, `Config`.`defaultNoProductOutImage`, `Config`.`defaultNoUserImage`, `Config`.`ticketsCounterFrontpageOffset`, `Config`.`ticketsCounterFrontpageFixed`, `Config`.`ticketsCounterFrontpageOption`, `Config`.`compoWarTracker`, `Config`.`maxTicketInCart`, `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal` FROM `fom_site`.`configs` AS `Config` LEFT JOIN `fom_site`.`events` AS `Event` ON (`Config`.`currentEvent` = `Event`.`id`) WHERE `Config`.`id` = 1 LIMIT 1	1	1	0
SELECT `Config`.`id`, `Config`.`currentEvent`, `Config`.`contactEmail`, `Config`.`technicalContactEmail`, `Config`.`organisationStreet`, `Config`.`organisationNr`, `Config`.`organisationZip`, `Config`.`organisationCity`, `Config`.`organisationCountry`, `Config`.`organisationWebsite`, `Config`.`organisationName`, `Config`.`vatNr`, `Config`.`bankAccount`, `Config`.`bic`, `Config`.`iban`, `Config`.`paypal`, `Config`.`cartLifeTime`, `Config`.`orderLifeTime`, `Config`.`orderWarningTime`, `Config`.`defaultNoProductImage`, `Config`.`defaultNoProductOutImage`, `Config`.`defaultNoUserImage`, `Config`.`ticketsCounterFrontpageOffset`, `Config`.`ticketsCounterFrontpageFixed`, `Config`.`ticketsCounterFrontpageOption`, `Config`.`compoWarTracker`, `Config`.`maxTicketInCart`, `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal` FROM `fom_site`.`configs` AS `Config` LEFT JOIN `fom_site`.`events` AS `Event` ON (`Config`.`currentEvent` = `Event`.`id`) WHERE 1 = 1 LIMIT 1	1	1	0
SELECT `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal` FROM `fom_site`.`events` AS `Event` WHERE `Event`.`id` = 49 LIMIT 1	1	1	0
SELECT count(Ticket.id) AS amount FROM `tickets` AS Ticket LEFT JOIN `products` AS `Product` ON Product.id = Ticket.productId WHERE Ticket.eventId=49 AND (Product.productTypeId = 1 OR Product.productTypeId = 4) AND Ticket.statusId != 4 AND Ticket.`typeId` IN (1,3,4,6,7,8)	1	1	1
SELECT Orderline.quantity FROM orderlines AS Orderline LEFT JOIN products AS Product ON (Product.id = Orderline.productId) LEFT JOIN orders AS Orders ON (Orders.id = Orderline.orderId) WHERE Product.eventId = 49 AND Orders.orderstateId IN (2,3,5,6) AND Product.productTypeId IN (1, 4) AND Product.productCategory = 1	177	177	1
SELECT count(Ticket.id) AS amount FROM `tickets` AS Ticket LEFT JOIN `products` AS `Product` ON Product.id = Ticket.productId WHERE Ticket.eventId=49 AND (Product.productTypeId = 1 OR Product.productTypeId = 4) AND Ticket.statusId != 4 AND Ticket.`typeId` = (8)	1	1	0
SELECT `Order`.`id`, `Order`.`defaultPaymentProviderId`, `Order`.`orderStateId`, `Order`.`refundable`, `Order`.`memberId`, `Order`.`orderDate`, `Order`.`orderDueDate`, `Order`.`totalPriceIncVat`, `Order`.`orderNumber`, `Order`.`notes`, `Order`.`orderWarningSent`, `Order`.`orderWarningDate`, `Order`.`paypal_verification`, `Order`.`transactionFee`, `Orderstate`.`id`, `Orderstate`.`name`, `Customer`.`id`, `Customer`.`facebook_id`, `Customer`.`username`, `Customer`.`new_username`, `Customer`.`nickname`, `Customer`.`password`, `Customer`.`firstname`, `Customer`.`lastname`, `Customer`.`active`, `Customer`.`validationCode`, `Customer`.`mailValidationCode`, `Customer`.`group_id`, `Customer`.`created`, `Customer`.`modified`, `Customer`.`last_login`, `Customer`.`street`, `Customer`.`nr`, `Customer`.`bus`, `Customer`.`zip`, `Customer`.`city`, `Customer`.`country`, `Customer`.`phone`, `Customer`.`gsm`, `Customer`.`gender`, `Customer`.`birthdate`, `Customer`.`clanId`, `Customer`.`clantrust`, `Customer`.`clanjoinId`, `Customer`.`hwbudget`, `Customer`.`education`, `Customer`.`profession`, `Customer`.`hoursaweek`, `Customer`.`language`, `Customer`.`oldId`, `Customer`.`receive_newsletter`, `Customer`.`imageUrl`, `Customer`.`slug`, `Customer`.`fb_link`, `Customer`.`fb_location`, `Customer`.`CPU`, `Customer`.`MOBO`, `Customer`.`GFX`, `Customer`.`RAM`, `Customer`.`steamName`, `Customer`.`steamId`, `Customer`.`originName`, `Customer`.`lolSummonerName`, `Customer`.`Other`, `Customer`.`comment`, `Customer`.`seat_id`, `Customer`.`msg_notifications`, `Customer`.`mouseHand`, `Customer`.`deviceId`, `Customer`.`alternative_login`, `DefaultProvider`.`id`, `DefaultProvider`.`name`, `DefaultProvider`.`description`, `DefaultProvider`.`transactionFeeFixed`, `DefaultProvider`.`transactionFeeVariable` FROM `fom_site`.`orders` AS `Order` LEFT JOIN `fom_site`.`orderstates` AS `Orderstate` ON (`Order`.`orderStateId` = `Orderstate`.`id`) LEFT JOIN `fom_site`.`users` AS `Customer` ON (`Order`.`memberId` = `Customer`.`id`) LEFT JOIN `fom_site`.`payment_providers` AS `DefaultProvider` ON (`Order`.`defaultPaymentProviderId` = `DefaultProvider`.`id`) WHERE `memberId` IS NULL AND `orderStateId` = 1 LIMIT 1	0	0	0
SELECT Newspost.id, Newspost.title_en, Newspost.title_nl, Newspost.imageUrl, Newspost.spotlightImgUrl, Newspost.slug, Newspost.startDate, Newspost.spotlight, Maintag.bannerUrl FROM newsposts AS Newspost LEFT JOIN tags AS Maintag ON (Newspost.newsTagId = Maintag.id) INNER JOIN newsxgroup AS Newsxgroup ON (Newspost.id = Newsxgroup.newsId) INNER JOIN newsgroups As Newsgroup ON (Newsxgroup.newsgroupId = Newsgroup.Id) WHERE Newspost.startDate < '2025-08-05 14:55:45' AND Newspost.finished = 1 AND Newspost.spotlight = 1 AND Newsgroup.slug = 'frontpage' ORDER BY Newspost.startdate DESC LIMIT 4	4	4	4
SELECT Newspost.id, Newspost.title_en, Newspost.title_nl, Newspost.imageUrl, Newspost.spotlightImgUrl, Newspost.slug, Newspost.startDate, Newspost.spotlight, Maintag.bannerUrl, Maintag.tagName, Maintag.slug, Maintag.color FROM newsposts AS Newspost LEFT JOIN tags AS Maintag ON (Newspost.newsTagId = Maintag.id) INNER JOIN newsxgroup AS Newsxgroup ON (Newspost.id = Newsxgroup.newsId) INNER JOIN newsgroups As Newsgroup ON (Newsxgroup.newsgroupId = Newsgroup.Id) WHERE Newspost.startDate < '2025-08-05 14:55:45' AND Newspost.finished = 1 AND Newspost.spotlight = 1 AND Newsgroup.slug = 'tournaments' ORDER BY Newspost.startdate DESC LIMIT 4	4	4	1	maybe slow
SELECT `Team`.`id`, `Team`.`name`, `Team`.`leaderId`, `Team`.`compoId`, `Team`.`pouleId`, `Team`.`notes`, `Team`.`withdrew`, `Compo`.`id`, `Compo`.`name`, `Compo`.`steamGameId`, `Compo`.`nrPlayersTeam`, `Compo`.`maxTeams`, `Compo`.`compoTypeId`, `Compo`.`nrPoules`, `Compo`.`nrWinnersPoule`, `Compo`.`compoStateId`, `Compo`.`eventId`, `Compo`.`roundDE`, `Compo`.`addSecondaryFinal`, `Compo`.`adminId`, `Compo`.`adminId2`, `Compo`.`bannerUrl`, `Compo`.`description`, `Compo`.`tagId`, `Compo`.`allowDrawInPoule`, `Compo`.`nrLosersToBrackets`, `Compo`.`pauzed`, `Compo`.`rulebook`, `Compo`.`showsponsor`, `Compo`.`sponsorcontent`, `Compo`.`showfiles`, `Compo`.`filescontent`, `Compo`.`prizescontent`, `Compo`.`precompo`, `Compo`.`donations`, `Compo`.`donationAmount`, `Compo`.`schedule`, `Compo`.`faq`, `Compo`.`sponsorUrl`, `Compo`.`sponsorImg`, `Compo`.`sortTimeLabel`, `Leader`.`id`, `Leader`.`facebook_id`, `Leader`.`username`, `Leader`.`new_username`, `Leader`.`nickname`, `Leader`.`password`, `Leader`.`firstname`, `Leader`.`lastname`, `Leader`.`active`, `Leader`.`validationCode`, `Leader`.`mailValidationCode`, `Leader`.`group_id`, `Leader`.`created`, `Leader`.`modified`, `Leader`.`last_login`, `Leader`.`street`, `Leader`.`nr`, `Leader`.`bus`, `Leader`.`zip`, `Leader`.`city`, `Leader`.`country`, `Leader`.`phone`, `Leader`.`gsm`, `Leader`.`gender`, `Leader`.`birthdate`, `Leader`.`clanId`, `Leader`.`clantrust`, `Leader`.`clanjoinId`, `Leader`.`hwbudget`, `Leader`.`education`, `Leader`.`profession`, `Leader`.`hoursaweek`, `Leader`.`language`, `Leader`.`oldId`, `Leader`.`receive_newsletter`, `Leader`.`imageUrl`, `Leader`.`slug`, `Leader`.`fb_link`, `Leader`.`fb_location`, `Leader`.`CPU`, `Leader`.`MOBO`, `Leader`.`GFX`, `Leader`.`RAM`, `Leader`.`steamName`, `Leader`.`steamId`, `Leader`.`originName`, `Leader`.`lolSummonerName`, `Leader`.`Other`, `Leader`.`comment`, `Leader`.`seat_id`, `Leader`.`msg_notifications`, `Leader`.`mouseHand`, `Leader`.`deviceId`, `Leader`.`alternative_login`, `Poule`.`id`, `Poule`.`compoId`, `Poule`.`name` FROM `fom_site`.`teams` AS `Team` LEFT JOIN `fom_site`.`compos` AS `Compo` ON (`Team`.`compoId` = `Compo`.`id`) LEFT JOIN `fom_site`.`users` AS `Leader` ON (`Team`.`leaderId` = `Leader`.`id`) LEFT JOIN `fom_site`.`poules` AS `Poule` ON (`Team`.`pouleId` = `Poule`.`id`) WHERE `Team`.`id` = 10265 ORDER BY `Team`.`id` ASC LIMIT 1	1	1	1
SELECT `Members`.`id`, `Members`.`facebook_id`, `Members`.`username`, `Members`.`new_username`, `Members`.`nickname`, `Members`.`password`, `Members`.`firstname`, `Members`.`lastname`, `Members`.`active`, `Members`.`validationCode`, `Members`.`mailValidationCode`, `Members`.`group_id`, `Members`.`created`, `Members`.`modified`, `Members`.`last_login`, `Members`.`street`, `Members`.`nr`, `Members`.`bus`, `Members`.`zip`, `Members`.`city`, `Members`.`country`, `Members`.`phone`, `Members`.`gsm`, `Members`.`gender`, `Members`.`birthdate`, `Members`.`clanId`, `Members`.`clantrust`, `Members`.`clanjoinId`, `Members`.`hwbudget`, `Members`.`education`, `Members`.`profession`, `Members`.`hoursaweek`, `Members`.`language`, `Members`.`oldId`, `Members`.`receive_newsletter`, `Members`.`imageUrl`, `Members`.`slug`, `Members`.`fb_link`, `Members`.`fb_location`, `Members`.`CPU`, `Members`.`MOBO`, `Members`.`GFX`, `Members`.`RAM`, `Members`.`steamName`, `Members`.`steamId`, `Members`.`originName`, `Members`.`lolSummonerName`, `Members`.`Other`, `Members`.`comment`, `Members`.`seat_id`, `Members`.`msg_notifications`, `Members`.`mouseHand`, `Members`.`deviceId`, `Members`.`alternative_login`, `TeamUser`.`id`, `TeamUser`.`teamId`, `TeamUser`.`userId`, `TeamUser`.`date` FROM `fom_site`.`users` AS `Members` JOIN `fom_site`.`team_users` AS `TeamUser` ON (`TeamUser`.`teamId` = 10265 AND `TeamUser`.`userId` = `Members`.`id`)	6	6	0
SELECT `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq`, `TicketState`.`id`, `TicketState`.`name`, `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal`, `Buyer`.`id`, `Buyer`.`facebook_id`, `Buyer`.`username`, `Buyer`.`new_username`, `Buyer`.`nickname`, `Buyer`.`password`, `Buyer`.`firstname`, `Buyer`.`lastname`, `Buyer`.`active`, `Buyer`.`validationCode`, `Buyer`.`mailValidationCode`, `Buyer`.`group_id`, `Buyer`.`created`, `Buyer`.`modified`, `Buyer`.`last_login`, `Buyer`.`street`, `Buyer`.`nr`, `Buyer`.`bus`, `Buyer`.`zip`, `Buyer`.`city`, `Buyer`.`country`, `Buyer`.`phone`, `Buyer`.`gsm`, `Buyer`.`gender`, `Buyer`.`birthdate`, `Buyer`.`clanId`, `Buyer`.`clantrust`, `Buyer`.`clanjoinId`, `Buyer`.`hwbudget`, `Buyer`.`education`, `Buyer`.`profession`, `Buyer`.`hoursaweek`, `Buyer`.`language`, `Buyer`.`oldId`, `Buyer`.`receive_newsletter`, `Buyer`.`imageUrl`, `Buyer`.`slug`, `Buyer`.`fb_link`, `Buyer`.`fb_location`, `Buyer`.`CPU`, `Buyer`.`MOBO`, `Buyer`.`GFX`, `Buyer`.`RAM`, `Buyer`.`steamName`, `Buyer`.`steamId`, `Buyer`.`originName`, `Buyer`.`lolSummonerName`, `Buyer`.`Other`, `Buyer`.`comment`, `Buyer`.`seat_id`, `Buyer`.`msg_notifications`, `Buyer`.`mouseHand`, `Buyer`.`deviceId`, `Buyer`.`alternative_login`, `Owner`.`id`, `Owner`.`facebook_id`, `Owner`.`username`, `Owner`.`new_username`, `Owner`.`nickname`, `Owner`.`password`, `Owner`.`firstname`, `Owner`.`lastname`, `Owner`.`active`, `Owner`.`validationCode`, `Owner`.`mailValidationCode`, `Owner`.`group_id`, `Owner`.`created`, `Owner`.`modified`, `Owner`.`last_login`, `Owner`.`street`, `Owner`.`nr`, `Owner`.`bus`, `Owner`.`zip`, `Owner`.`city`, `Owner`.`country`, `Owner`.`phone`, `Owner`.`gsm`, `Owner`.`gender`, `Owner`.`birthdate`, `Owner`.`clanId`, `Owner`.`clantrust`, `Owner`.`clanjoinId`, `Owner`.`hwbudget`, `Owner`.`education`, `Owner`.`profession`, `Owner`.`hoursaweek`, `Owner`.`language`, `Owner`.`oldId`, `Owner`.`receive_newsletter`, `Owner`.`imageUrl`, `Owner`.`slug`, `Owner`.`fb_link`, `Owner`.`fb_location`, `Owner`.`CPU`, `Owner`.`MOBO`, `Owner`.`GFX`, `Owner`.`RAM`, `Owner`.`steamName`, `Owner`.`steamId`, `Owner`.`originName`, `Owner`.`lolSummonerName`, `Owner`.`Other`, `Owner`.`comment`, `Owner`.`seat_id`, `Owner`.`msg_notifications`, `Owner`.`mouseHand`, `Owner`.`deviceId`, `Owner`.`alternative_login`, `Operator`.`id`, `Operator`.`facebook_id`, `Operator`.`username`, `Operator`.`new_username`, `Operator`.`nickname`, `Operator`.`password`, `Operator`.`firstname`, `Operator`.`lastname`, `Operator`.`active`, `Operator`.`validationCode`, `Operator`.`mailValidationCode`, `Operator`.`group_id`, `Operator`.`created`, `Operator`.`modified`, `Operator`.`last_login`, `Operator`.`street`, `Operator`.`nr`, `Operator`.`bus`, `Operator`.`zip`, `Operator`.`city`, `Operator`.`country`, `Operator`.`phone`, `Operator`.`gsm`, `Operator`.`gender`, `Operator`.`birthdate`, `Operator`.`clanId`, `Operator`.`clantrust`, `Operator`.`clanjoinId`, `Operator`.`hwbudget`, `Operator`.`education`, `Operator`.`profession`, `Operator`.`hoursaweek`, `Operator`.`language`, `Operator`.`oldId`, `Operator`.`receive_newsletter`, `Operator`.`imageUrl`, `Operator`.`slug`, `Operator`.`fb_link`, `Operator`.`fb_location`, `Operator`.`CPU`, `Operator`.`MOBO`, `Operator`.`GFX`, `Operator`.`RAM`, `Operator`.`steamName`, `Operator`.`steamId`, `Operator`.`originName`, `Operator`.`lolSummonerName`, `Operator`.`Other`, `Operator`.`comment`, `Operator`.`seat_id`, `Operator`.`msg_notifications`, `Operator`.`mouseHand`, `Operator`.`deviceId`, `Operator`.`alternative_login`, `Product`.`id`, `Product`.`name`, `Product`.`slug`, `Product`.`description`, `Product`.`imageUrl`, `Product`.`priceExclVat`, `Product`.`priceInclVat`, `Product`.`vatId`, `Product`.`offeredFrom`, `Product`.`offeredUntil`, `Product`.`stock`, `Product`.`totalItems`, `Product`.`productTypeId`, `Product`.`productCategory`, `Product`.`eventId`, `Product`.`active`, `Order`.`id`, `Order`.`defaultPaymentProviderId`, `Order`.`orderStateId`, `Order`.`refundable`, `Order`.`memberId`, `Order`.`orderDate`, `Order`.`orderDueDate`, `Order`.`totalPriceIncVat`, `Order`.`orderNumber`, `Order`.`notes`, `Order`.`orderWarningSent`, `Order`.`orderWarningDate`, `Order`.`paypal_verification`, `Order`.`transactionFee`, `Type`.`id`, `Type`.`name` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`eventId` = 46 AND `Ticket`.`ownerId` = 5352 LIMIT 1	1	1	1
SELECT `Seat`.`id`, `Seat`.`seatmapId`, `Seat`.`ticketId`, `Seat`.`seatNumber`, `Seat`.`row`, `Seat`.`enabled`, `Seat`.`vip`, `Seat`.`date`, `Seat`.`reservedBy`, `Seatmap`.`id`, `Seatmap`.`eventId`, `Seatmap`.`enabled`, `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq` FROM `fom_site`.`seats` AS `Seat` LEFT JOIN `fom_site`.`seatmaps` AS `Seatmap` ON (`Seat`.`seatmapId` = `Seatmap`.`id`) LEFT JOIN `fom_site`.`tickets` AS `Ticket` ON (`Seat`.`ticketId` = `Ticket`.`id`) WHERE `Seat`.`ticketId` = 19741 LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`statusId` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`ownerId` = 5352 AND `Ticket`.`eventId` = 46 ORDER BY `id` DESC LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq`, `TicketState`.`id`, `TicketState`.`name`, `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal`, `Buyer`.`id`, `Buyer`.`facebook_id`, `Buyer`.`username`, `Buyer`.`new_username`, `Buyer`.`nickname`, `Buyer`.`password`, `Buyer`.`firstname`, `Buyer`.`lastname`, `Buyer`.`active`, `Buyer`.`validationCode`, `Buyer`.`mailValidationCode`, `Buyer`.`group_id`, `Buyer`.`created`, `Buyer`.`modified`, `Buyer`.`last_login`, `Buyer`.`street`, `Buyer`.`nr`, `Buyer`.`bus`, `Buyer`.`zip`, `Buyer`.`city`, `Buyer`.`country`, `Buyer`.`phone`, `Buyer`.`gsm`, `Buyer`.`gender`, `Buyer`.`birthdate`, `Buyer`.`clanId`, `Buyer`.`clantrust`, `Buyer`.`clanjoinId`, `Buyer`.`hwbudget`, `Buyer`.`education`, `Buyer`.`profession`, `Buyer`.`hoursaweek`, `Buyer`.`language`, `Buyer`.`oldId`, `Buyer`.`receive_newsletter`, `Buyer`.`imageUrl`, `Buyer`.`slug`, `Buyer`.`fb_link`, `Buyer`.`fb_location`, `Buyer`.`CPU`, `Buyer`.`MOBO`, `Buyer`.`GFX`, `Buyer`.`RAM`, `Buyer`.`steamName`, `Buyer`.`steamId`, `Buyer`.`originName`, `Buyer`.`lolSummonerName`, `Buyer`.`Other`, `Buyer`.`comment`, `Buyer`.`seat_id`, `Buyer`.`msg_notifications`, `Buyer`.`mouseHand`, `Buyer`.`deviceId`, `Buyer`.`alternative_login`, `Owner`.`id`, `Owner`.`facebook_id`, `Owner`.`username`, `Owner`.`new_username`, `Owner`.`nickname`, `Owner`.`password`, `Owner`.`firstname`, `Owner`.`lastname`, `Owner`.`active`, `Owner`.`validationCode`, `Owner`.`mailValidationCode`, `Owner`.`group_id`, `Owner`.`created`, `Owner`.`modified`, `Owner`.`last_login`, `Owner`.`street`, `Owner`.`nr`, `Owner`.`bus`, `Owner`.`zip`, `Owner`.`city`, `Owner`.`country`, `Owner`.`phone`, `Owner`.`gsm`, `Owner`.`gender`, `Owner`.`birthdate`, `Owner`.`clanId`, `Owner`.`clantrust`, `Owner`.`clanjoinId`, `Owner`.`hwbudget`, `Owner`.`education`, `Owner`.`profession`, `Owner`.`hoursaweek`, `Owner`.`language`, `Owner`.`oldId`, `Owner`.`receive_newsletter`, `Owner`.`imageUrl`, `Owner`.`slug`, `Owner`.`fb_link`, `Owner`.`fb_location`, `Owner`.`CPU`, `Owner`.`MOBO`, `Owner`.`GFX`, `Owner`.`RAM`, `Owner`.`steamName`, `Owner`.`steamId`, `Owner`.`originName`, `Owner`.`lolSummonerName`, `Owner`.`Other`, `Owner`.`comment`, `Owner`.`seat_id`, `Owner`.`msg_notifications`, `Owner`.`mouseHand`, `Owner`.`deviceId`, `Owner`.`alternative_login`, `Operator`.`id`, `Operator`.`facebook_id`, `Operator`.`username`, `Operator`.`new_username`, `Operator`.`nickname`, `Operator`.`password`, `Operator`.`firstname`, `Operator`.`lastname`, `Operator`.`active`, `Operator`.`validationCode`, `Operator`.`mailValidationCode`, `Operator`.`group_id`, `Operator`.`created`, `Operator`.`modified`, `Operator`.`last_login`, `Operator`.`street`, `Operator`.`nr`, `Operator`.`bus`, `Operator`.`zip`, `Operator`.`city`, `Operator`.`country`, `Operator`.`phone`, `Operator`.`gsm`, `Operator`.`gender`, `Operator`.`birthdate`, `Operator`.`clanId`, `Operator`.`clantrust`, `Operator`.`clanjoinId`, `Operator`.`hwbudget`, `Operator`.`education`, `Operator`.`profession`, `Operator`.`hoursaweek`, `Operator`.`language`, `Operator`.`oldId`, `Operator`.`receive_newsletter`, `Operator`.`imageUrl`, `Operator`.`slug`, `Operator`.`fb_link`, `Operator`.`fb_location`, `Operator`.`CPU`, `Operator`.`MOBO`, `Operator`.`GFX`, `Operator`.`RAM`, `Operator`.`steamName`, `Operator`.`steamId`, `Operator`.`originName`, `Operator`.`lolSummonerName`, `Operator`.`Other`, `Operator`.`comment`, `Operator`.`seat_id`, `Operator`.`msg_notifications`, `Operator`.`mouseHand`, `Operator`.`deviceId`, `Operator`.`alternative_login`, `Product`.`id`, `Product`.`name`, `Product`.`slug`, `Product`.`description`, `Product`.`imageUrl`, `Product`.`priceExclVat`, `Product`.`priceInclVat`, `Product`.`vatId`, `Product`.`offeredFrom`, `Product`.`offeredUntil`, `Product`.`stock`, `Product`.`totalItems`, `Product`.`productTypeId`, `Product`.`productCategory`, `Product`.`eventId`, `Product`.`active`, `Order`.`id`, `Order`.`defaultPaymentProviderId`, `Order`.`orderStateId`, `Order`.`refundable`, `Order`.`memberId`, `Order`.`orderDate`, `Order`.`orderDueDate`, `Order`.`totalPriceIncVat`, `Order`.`orderNumber`, `Order`.`notes`, `Order`.`orderWarningSent`, `Order`.`orderWarningDate`, `Order`.`paypal_verification`, `Order`.`transactionFee`, `Type`.`id`, `Type`.`name` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`eventId` = 46 AND `Ticket`.`ownerId` = 8720 LIMIT 1	1	1	1
SELECT `Seat`.`id`, `Seat`.`seatmapId`, `Seat`.`ticketId`, `Seat`.`seatNumber`, `Seat`.`row`, `Seat`.`enabled`, `Seat`.`vip`, `Seat`.`date`, `Seat`.`reservedBy`, `Seatmap`.`id`, `Seatmap`.`eventId`, `Seatmap`.`enabled`, `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq` FROM `fom_site`.`seats` AS `Seat` LEFT JOIN `fom_site`.`seatmaps` AS `Seatmap` ON (`Seat`.`seatmapId` = `Seatmap`.`id`) LEFT JOIN `fom_site`.`tickets` AS `Ticket` ON (`Seat`.`ticketId` = `Ticket`.`id`) WHERE `Seat`.`ticketId` = 19742 LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`statusId` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`ownerId` = 8720 AND `Ticket`.`eventId` = 46 ORDER BY `id` DESC LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq`, `TicketState`.`id`, `TicketState`.`name`, `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal`, `Buyer`.`id`, `Buyer`.`facebook_id`, `Buyer`.`username`, `Buyer`.`new_username`, `Buyer`.`nickname`, `Buyer`.`password`, `Buyer`.`firstname`, `Buyer`.`lastname`, `Buyer`.`active`, `Buyer`.`validationCode`, `Buyer`.`mailValidationCode`, `Buyer`.`group_id`, `Buyer`.`created`, `Buyer`.`modified`, `Buyer`.`last_login`, `Buyer`.`street`, `Buyer`.`nr`, `Buyer`.`bus`, `Buyer`.`zip`, `Buyer`.`city`, `Buyer`.`country`, `Buyer`.`phone`, `Buyer`.`gsm`, `Buyer`.`gender`, `Buyer`.`birthdate`, `Buyer`.`clanId`, `Buyer`.`clantrust`, `Buyer`.`clanjoinId`, `Buyer`.`hwbudget`, `Buyer`.`education`, `Buyer`.`profession`, `Buyer`.`hoursaweek`, `Buyer`.`language`, `Buyer`.`oldId`, `Buyer`.`receive_newsletter`, `Buyer`.`imageUrl`, `Buyer`.`slug`, `Buyer`.`fb_link`, `Buyer`.`fb_location`, `Buyer`.`CPU`, `Buyer`.`MOBO`, `Buyer`.`GFX`, `Buyer`.`RAM`, `Buyer`.`steamName`, `Buyer`.`steamId`, `Buyer`.`originName`, `Buyer`.`lolSummonerName`, `Buyer`.`Other`, `Buyer`.`comment`, `Buyer`.`seat_id`, `Buyer`.`msg_notifications`, `Buyer`.`mouseHand`, `Buyer`.`deviceId`, `Buyer`.`alternative_login`, `Owner`.`id`, `Owner`.`facebook_id`, `Owner`.`username`, `Owner`.`new_username`, `Owner`.`nickname`, `Owner`.`password`, `Owner`.`firstname`, `Owner`.`lastname`, `Owner`.`active`, `Owner`.`validationCode`, `Owner`.`mailValidationCode`, `Owner`.`group_id`, `Owner`.`created`, `Owner`.`modified`, `Owner`.`last_login`, `Owner`.`street`, `Owner`.`nr`, `Owner`.`bus`, `Owner`.`zip`, `Owner`.`city`, `Owner`.`country`, `Owner`.`phone`, `Owner`.`gsm`, `Owner`.`gender`, `Owner`.`birthdate`, `Owner`.`clanId`, `Owner`.`clantrust`, `Owner`.`clanjoinId`, `Owner`.`hwbudget`, `Owner`.`education`, `Owner`.`profession`, `Owner`.`hoursaweek`, `Owner`.`language`, `Owner`.`oldId`, `Owner`.`receive_newsletter`, `Owner`.`imageUrl`, `Owner`.`slug`, `Owner`.`fb_link`, `Owner`.`fb_location`, `Owner`.`CPU`, `Owner`.`MOBO`, `Owner`.`GFX`, `Owner`.`RAM`, `Owner`.`steamName`, `Owner`.`steamId`, `Owner`.`originName`, `Owner`.`lolSummonerName`, `Owner`.`Other`, `Owner`.`comment`, `Owner`.`seat_id`, `Owner`.`msg_notifications`, `Owner`.`mouseHand`, `Owner`.`deviceId`, `Owner`.`alternative_login`, `Operator`.`id`, `Operator`.`facebook_id`, `Operator`.`username`, `Operator`.`new_username`, `Operator`.`nickname`, `Operator`.`password`, `Operator`.`firstname`, `Operator`.`lastname`, `Operator`.`active`, `Operator`.`validationCode`, `Operator`.`mailValidationCode`, `Operator`.`group_id`, `Operator`.`created`, `Operator`.`modified`, `Operator`.`last_login`, `Operator`.`street`, `Operator`.`nr`, `Operator`.`bus`, `Operator`.`zip`, `Operator`.`city`, `Operator`.`country`, `Operator`.`phone`, `Operator`.`gsm`, `Operator`.`gender`, `Operator`.`birthdate`, `Operator`.`clanId`, `Operator`.`clantrust`, `Operator`.`clanjoinId`, `Operator`.`hwbudget`, `Operator`.`education`, `Operator`.`profession`, `Operator`.`hoursaweek`, `Operator`.`language`, `Operator`.`oldId`, `Operator`.`receive_newsletter`, `Operator`.`imageUrl`, `Operator`.`slug`, `Operator`.`fb_link`, `Operator`.`fb_location`, `Operator`.`CPU`, `Operator`.`MOBO`, `Operator`.`GFX`, `Operator`.`RAM`, `Operator`.`steamName`, `Operator`.`steamId`, `Operator`.`originName`, `Operator`.`lolSummonerName`, `Operator`.`Other`, `Operator`.`comment`, `Operator`.`seat_id`, `Operator`.`msg_notifications`, `Operator`.`mouseHand`, `Operator`.`deviceId`, `Operator`.`alternative_login`, `Product`.`id`, `Product`.`name`, `Product`.`slug`, `Product`.`description`, `Product`.`imageUrl`, `Product`.`priceExclVat`, `Product`.`priceInclVat`, `Product`.`vatId`, `Product`.`offeredFrom`, `Product`.`offeredUntil`, `Product`.`stock`, `Product`.`totalItems`, `Product`.`productTypeId`, `Product`.`productCategory`, `Product`.`eventId`, `Product`.`active`, `Order`.`id`, `Order`.`defaultPaymentProviderId`, `Order`.`orderStateId`, `Order`.`refundable`, `Order`.`memberId`, `Order`.`orderDate`, `Order`.`orderDueDate`, `Order`.`totalPriceIncVat`, `Order`.`orderNumber`, `Order`.`notes`, `Order`.`orderWarningSent`, `Order`.`orderWarningDate`, `Order`.`paypal_verification`, `Order`.`transactionFee`, `Type`.`id`, `Type`.`name` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`eventId` = 46 AND `Ticket`.`ownerId` = 5896 LIMIT 1	1	1	1
SELECT `Seat`.`id`, `Seat`.`seatmapId`, `Seat`.`ticketId`, `Seat`.`seatNumber`, `Seat`.`row`, `Seat`.`enabled`, `Seat`.`vip`, `Seat`.`date`, `Seat`.`reservedBy`, `Seatmap`.`id`, `Seatmap`.`eventId`, `Seatmap`.`enabled`, `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq` FROM `fom_site`.`seats` AS `Seat` LEFT JOIN `fom_site`.`seatmaps` AS `Seatmap` ON (`Seat`.`seatmapId` = `Seatmap`.`id`) LEFT JOIN `fom_site`.`tickets` AS `Ticket` ON (`Seat`.`ticketId` = `Ticket`.`id`) WHERE `Seat`.`ticketId` = 19865 LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`statusId` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`ownerId` = 5896 AND `Ticket`.`eventId` = 46 ORDER BY `id` DESC LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq`, `TicketState`.`id`, `TicketState`.`name`, `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal`, `Buyer`.`id`, `Buyer`.`facebook_id`, `Buyer`.`username`, `Buyer`.`new_username`, `Buyer`.`nickname`, `Buyer`.`password`, `Buyer`.`firstname`, `Buyer`.`lastname`, `Buyer`.`active`, `Buyer`.`validationCode`, `Buyer`.`mailValidationCode`, `Buyer`.`group_id`, `Buyer`.`created`, `Buyer`.`modified`, `Buyer`.`last_login`, `Buyer`.`street`, `Buyer`.`nr`, `Buyer`.`bus`, `Buyer`.`zip`, `Buyer`.`city`, `Buyer`.`country`, `Buyer`.`phone`, `Buyer`.`gsm`, `Buyer`.`gender`, `Buyer`.`birthdate`, `Buyer`.`clanId`, `Buyer`.`clantrust`, `Buyer`.`clanjoinId`, `Buyer`.`hwbudget`, `Buyer`.`education`, `Buyer`.`profession`, `Buyer`.`hoursaweek`, `Buyer`.`language`, `Buyer`.`oldId`, `Buyer`.`receive_newsletter`, `Buyer`.`imageUrl`, `Buyer`.`slug`, `Buyer`.`fb_link`, `Buyer`.`fb_location`, `Buyer`.`CPU`, `Buyer`.`MOBO`, `Buyer`.`GFX`, `Buyer`.`RAM`, `Buyer`.`steamName`, `Buyer`.`steamId`, `Buyer`.`originName`, `Buyer`.`lolSummonerName`, `Buyer`.`Other`, `Buyer`.`comment`, `Buyer`.`seat_id`, `Buyer`.`msg_notifications`, `Buyer`.`mouseHand`, `Buyer`.`deviceId`, `Buyer`.`alternative_login`, `Owner`.`id`, `Owner`.`facebook_id`, `Owner`.`username`, `Owner`.`new_username`, `Owner`.`nickname`, `Owner`.`password`, `Owner`.`firstname`, `Owner`.`lastname`, `Owner`.`active`, `Owner`.`validationCode`, `Owner`.`mailValidationCode`, `Owner`.`group_id`, `Owner`.`created`, `Owner`.`modified`, `Owner`.`last_login`, `Owner`.`street`, `Owner`.`nr`, `Owner`.`bus`, `Owner`.`zip`, `Owner`.`city`, `Owner`.`country`, `Owner`.`phone`, `Owner`.`gsm`, `Owner`.`gender`, `Owner`.`birthdate`, `Owner`.`clanId`, `Owner`.`clantrust`, `Owner`.`clanjoinId`, `Owner`.`hwbudget`, `Owner`.`education`, `Owner`.`profession`, `Owner`.`hoursaweek`, `Owner`.`language`, `Owner`.`oldId`, `Owner`.`receive_newsletter`, `Owner`.`imageUrl`, `Owner`.`slug`, `Owner`.`fb_link`, `Owner`.`fb_location`, `Owner`.`CPU`, `Owner`.`MOBO`, `Owner`.`GFX`, `Owner`.`RAM`, `Owner`.`steamName`, `Owner`.`steamId`, `Owner`.`originName`, `Owner`.`lolSummonerName`, `Owner`.`Other`, `Owner`.`comment`, `Owner`.`seat_id`, `Owner`.`msg_notifications`, `Owner`.`mouseHand`, `Owner`.`deviceId`, `Owner`.`alternative_login`, `Operator`.`id`, `Operator`.`facebook_id`, `Operator`.`username`, `Operator`.`new_username`, `Operator`.`nickname`, `Operator`.`password`, `Operator`.`firstname`, `Operator`.`lastname`, `Operator`.`active`, `Operator`.`validationCode`, `Operator`.`mailValidationCode`, `Operator`.`group_id`, `Operator`.`created`, `Operator`.`modified`, `Operator`.`last_login`, `Operator`.`street`, `Operator`.`nr`, `Operator`.`bus`, `Operator`.`zip`, `Operator`.`city`, `Operator`.`country`, `Operator`.`phone`, `Operator`.`gsm`, `Operator`.`gender`, `Operator`.`birthdate`, `Operator`.`clanId`, `Operator`.`clantrust`, `Operator`.`clanjoinId`, `Operator`.`hwbudget`, `Operator`.`education`, `Operator`.`profession`, `Operator`.`hoursaweek`, `Operator`.`language`, `Operator`.`oldId`, `Operator`.`receive_newsletter`, `Operator`.`imageUrl`, `Operator`.`slug`, `Operator`.`fb_link`, `Operator`.`fb_location`, `Operator`.`CPU`, `Operator`.`MOBO`, `Operator`.`GFX`, `Operator`.`RAM`, `Operator`.`steamName`, `Operator`.`steamId`, `Operator`.`originName`, `Operator`.`lolSummonerName`, `Operator`.`Other`, `Operator`.`comment`, `Operator`.`seat_id`, `Operator`.`msg_notifications`, `Operator`.`mouseHand`, `Operator`.`deviceId`, `Operator`.`alternative_login`, `Product`.`id`, `Product`.`name`, `Product`.`slug`, `Product`.`description`, `Product`.`imageUrl`, `Product`.`priceExclVat`, `Product`.`priceInclVat`, `Product`.`vatId`, `Product`.`offeredFrom`, `Product`.`offeredUntil`, `Product`.`stock`, `Product`.`totalItems`, `Product`.`productTypeId`, `Product`.`productCategory`, `Product`.`eventId`, `Product`.`active`, `Order`.`id`, `Order`.`defaultPaymentProviderId`, `Order`.`orderStateId`, `Order`.`refundable`, `Order`.`memberId`, `Order`.`orderDate`, `Order`.`orderDueDate`, `Order`.`totalPriceIncVat`, `Order`.`orderNumber`, `Order`.`notes`, `Order`.`orderWarningSent`, `Order`.`orderWarningDate`, `Order`.`paypal_verification`, `Order`.`transactionFee`, `Type`.`id`, `Type`.`name` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`eventId` = 46 AND `Ticket`.`ownerId` = 7769 LIMIT 1	1	1	1
SELECT `Seat`.`id`, `Seat`.`seatmapId`, `Seat`.`ticketId`, `Seat`.`seatNumber`, `Seat`.`row`, `Seat`.`enabled`, `Seat`.`vip`, `Seat`.`date`, `Seat`.`reservedBy`, `Seatmap`.`id`, `Seatmap`.`eventId`, `Seatmap`.`enabled`, `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq` FROM `fom_site`.`seats` AS `Seat` LEFT JOIN `fom_site`.`seatmaps` AS `Seatmap` ON (`Seat`.`seatmapId` = `Seatmap`.`id`) LEFT JOIN `fom_site`.`tickets` AS `Ticket` ON (`Seat`.`ticketId` = `Ticket`.`id`) WHERE `Seat`.`ticketId` = 19957 LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`statusId` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`ownerId` = 7769 AND `Ticket`.`eventId` = 46 ORDER BY `id` DESC LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq`, `TicketState`.`id`, `TicketState`.`name`, `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal`, `Buyer`.`id`, `Buyer`.`facebook_id`, `Buyer`.`username`, `Buyer`.`new_username`, `Buyer`.`nickname`, `Buyer`.`password`, `Buyer`.`firstname`, `Buyer`.`lastname`, `Buyer`.`active`, `Buyer`.`validationCode`, `Buyer`.`mailValidationCode`, `Buyer`.`group_id`, `Buyer`.`created`, `Buyer`.`modified`, `Buyer`.`last_login`, `Buyer`.`street`, `Buyer`.`nr`, `Buyer`.`bus`, `Buyer`.`zip`, `Buyer`.`city`, `Buyer`.`country`, `Buyer`.`phone`, `Buyer`.`gsm`, `Buyer`.`gender`, `Buyer`.`birthdate`, `Buyer`.`clanId`, `Buyer`.`clantrust`, `Buyer`.`clanjoinId`, `Buyer`.`hwbudget`, `Buyer`.`education`, `Buyer`.`profession`, `Buyer`.`hoursaweek`, `Buyer`.`language`, `Buyer`.`oldId`, `Buyer`.`receive_newsletter`, `Buyer`.`imageUrl`, `Buyer`.`slug`, `Buyer`.`fb_link`, `Buyer`.`fb_location`, `Buyer`.`CPU`, `Buyer`.`MOBO`, `Buyer`.`GFX`, `Buyer`.`RAM`, `Buyer`.`steamName`, `Buyer`.`steamId`, `Buyer`.`originName`, `Buyer`.`lolSummonerName`, `Buyer`.`Other`, `Buyer`.`comment`, `Buyer`.`seat_id`, `Buyer`.`msg_notifications`, `Buyer`.`mouseHand`, `Buyer`.`deviceId`, `Buyer`.`alternative_login`, `Owner`.`id`, `Owner`.`facebook_id`, `Owner`.`username`, `Owner`.`new_username`, `Owner`.`nickname`, `Owner`.`password`, `Owner`.`firstname`, `Owner`.`lastname`, `Owner`.`active`, `Owner`.`validationCode`, `Owner`.`mailValidationCode`, `Owner`.`group_id`, `Owner`.`created`, `Owner`.`modified`, `Owner`.`last_login`, `Owner`.`street`, `Owner`.`nr`, `Owner`.`bus`, `Owner`.`zip`, `Owner`.`city`, `Owner`.`country`, `Owner`.`phone`, `Owner`.`gsm`, `Owner`.`gender`, `Owner`.`birthdate`, `Owner`.`clanId`, `Owner`.`clantrust`, `Owner`.`clanjoinId`, `Owner`.`hwbudget`, `Owner`.`education`, `Owner`.`profession`, `Owner`.`hoursaweek`, `Owner`.`language`, `Owner`.`oldId`, `Owner`.`receive_newsletter`, `Owner`.`imageUrl`, `Owner`.`slug`, `Owner`.`fb_link`, `Owner`.`fb_location`, `Owner`.`CPU`, `Owner`.`MOBO`, `Owner`.`GFX`, `Owner`.`RAM`, `Owner`.`steamName`, `Owner`.`steamId`, `Owner`.`originName`, `Owner`.`lolSummonerName`, `Owner`.`Other`, `Owner`.`comment`, `Owner`.`seat_id`, `Owner`.`msg_notifications`, `Owner`.`mouseHand`, `Owner`.`deviceId`, `Owner`.`alternative_login`, `Operator`.`id`, `Operator`.`facebook_id`, `Operator`.`username`, `Operator`.`new_username`, `Operator`.`nickname`, `Operator`.`password`, `Operator`.`firstname`, `Operator`.`lastname`, `Operator`.`active`, `Operator`.`validationCode`, `Operator`.`mailValidationCode`, `Operator`.`group_id`, `Operator`.`created`, `Operator`.`modified`, `Operator`.`last_login`, `Operator`.`street`, `Operator`.`nr`, `Operator`.`bus`, `Operator`.`zip`, `Operator`.`city`, `Operator`.`country`, `Operator`.`phone`, `Operator`.`gsm`, `Operator`.`gender`, `Operator`.`birthdate`, `Operator`.`clanId`, `Operator`.`clantrust`, `Operator`.`clanjoinId`, `Operator`.`hwbudget`, `Operator`.`education`, `Operator`.`profession`, `Operator`.`hoursaweek`, `Operator`.`language`, `Operator`.`oldId`, `Operator`.`receive_newsletter`, `Operator`.`imageUrl`, `Operator`.`slug`, `Operator`.`fb_link`, `Operator`.`fb_location`, `Operator`.`CPU`, `Operator`.`MOBO`, `Operator`.`GFX`, `Operator`.`RAM`, `Operator`.`steamName`, `Operator`.`steamId`, `Operator`.`originName`, `Operator`.`lolSummonerName`, `Operator`.`Other`, `Operator`.`comment`, `Operator`.`seat_id`, `Operator`.`msg_notifications`, `Operator`.`mouseHand`, `Operator`.`deviceId`, `Operator`.`alternative_login`, `Product`.`id`, `Product`.`name`, `Product`.`slug`, `Product`.`description`, `Product`.`imageUrl`, `Product`.`priceExclVat`, `Product`.`priceInclVat`, `Product`.`vatId`, `Product`.`offeredFrom`, `Product`.`offeredUntil`, `Product`.`stock`, `Product`.`totalItems`, `Product`.`productTypeId`, `Product`.`productCategory`, `Product`.`eventId`, `Product`.`active`, `Order`.`id`, `Order`.`defaultPaymentProviderId`, `Order`.`orderStateId`, `Order`.`refundable`, `Order`.`memberId`, `Order`.`orderDate`, `Order`.`orderDueDate`, `Order`.`totalPriceIncVat`, `Order`.`orderNumber`, `Order`.`notes`, `Order`.`orderWarningSent`, `Order`.`orderWarningDate`, `Order`.`paypal_verification`, `Order`.`transactionFee`, `Type`.`id`, `Type`.`name` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`eventId` = 46 AND `Ticket`.`ownerId` = 5690 LIMIT 1	1	1	1
SELECT `Seat`.`id`, `Seat`.`seatmapId`, `Seat`.`ticketId`, `Seat`.`seatNumber`, `Seat`.`row`, `Seat`.`enabled`, `Seat`.`vip`, `Seat`.`date`, `Seat`.`reservedBy`, `Seatmap`.`id`, `Seatmap`.`eventId`, `Seatmap`.`enabled`, `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq` FROM `fom_site`.`seats` AS `Seat` LEFT JOIN `fom_site`.`seatmaps` AS `Seatmap` ON (`Seat`.`seatmapId` = `Seatmap`.`id`) LEFT JOIN `fom_site`.`tickets` AS `Ticket` ON (`Seat`.`ticketId` = `Ticket`.`id`) WHERE `Seat`.`ticketId` = 19745 LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`statusId` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`ownerId` = 5690 AND `Ticket`.`eventId` = 46 ORDER BY `id` DESC LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq`, `TicketState`.`id`, `TicketState`.`name`, `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal`, `Buyer`.`id`, `Buyer`.`facebook_id`, `Buyer`.`username`, `Buyer`.`new_username`, `Buyer`.`nickname`, `Buyer`.`password`, `Buyer`.`firstname`, `Buyer`.`lastname`, `Buyer`.`active`, `Buyer`.`validationCode`, `Buyer`.`mailValidationCode`, `Buyer`.`group_id`, `Buyer`.`created`, `Buyer`.`modified`, `Buyer`.`last_login`, `Buyer`.`street`, `Buyer`.`nr`, `Buyer`.`bus`, `Buyer`.`zip`, `Buyer`.`city`, `Buyer`.`country`, `Buyer`.`phone`, `Buyer`.`gsm`, `Buyer`.`gender`, `Buyer`.`birthdate`, `Buyer`.`clanId`, `Buyer`.`clantrust`, `Buyer`.`clanjoinId`, `Buyer`.`hwbudget`, `Buyer`.`education`, `Buyer`.`profession`, `Buyer`.`hoursaweek`, `Buyer`.`language`, `Buyer`.`oldId`, `Buyer`.`receive_newsletter`, `Buyer`.`imageUrl`, `Buyer`.`slug`, `Buyer`.`fb_link`, `Buyer`.`fb_location`, `Buyer`.`CPU`, `Buyer`.`MOBO`, `Buyer`.`GFX`, `Buyer`.`RAM`, `Buyer`.`steamName`, `Buyer`.`steamId`, `Buyer`.`originName`, `Buyer`.`lolSummonerName`, `Buyer`.`Other`, `Buyer`.`comment`, `Buyer`.`seat_id`, `Buyer`.`msg_notifications`, `Buyer`.`mouseHand`, `Buyer`.`deviceId`, `Buyer`.`alternative_login`, `Owner`.`id`, `Owner`.`facebook_id`, `Owner`.`username`, `Owner`.`new_username`, `Owner`.`nickname`, `Owner`.`password`, `Owner`.`firstname`, `Owner`.`lastname`, `Owner`.`active`, `Owner`.`validationCode`, `Owner`.`mailValidationCode`, `Owner`.`group_id`, `Owner`.`created`, `Owner`.`modified`, `Owner`.`last_login`, `Owner`.`street`, `Owner`.`nr`, `Owner`.`bus`, `Owner`.`zip`, `Owner`.`city`, `Owner`.`country`, `Owner`.`phone`, `Owner`.`gsm`, `Owner`.`gender`, `Owner`.`birthdate`, `Owner`.`clanId`, `Owner`.`clantrust`, `Owner`.`clanjoinId`, `Owner`.`hwbudget`, `Owner`.`education`, `Owner`.`profession`, `Owner`.`hoursaweek`, `Owner`.`language`, `Owner`.`oldId`, `Owner`.`receive_newsletter`, `Owner`.`imageUrl`, `Owner`.`slug`, `Owner`.`fb_link`, `Owner`.`fb_location`, `Owner`.`CPU`, `Owner`.`MOBO`, `Owner`.`GFX`, `Owner`.`RAM`, `Owner`.`steamName`, `Owner`.`steamId`, `Owner`.`originName`, `Owner`.`lolSummonerName`, `Owner`.`Other`, `Owner`.`comment`, `Owner`.`seat_id`, `Owner`.`msg_notifications`, `Owner`.`mouseHand`, `Owner`.`deviceId`, `Owner`.`alternative_login`, `Operator`.`id`, `Operator`.`facebook_id`, `Operator`.`username`, `Operator`.`new_username`, `Operator`.`nickname`, `Operator`.`password`, `Operator`.`firstname`, `Operator`.`lastname`, `Operator`.`active`, `Operator`.`validationCode`, `Operator`.`mailValidationCode`, `Operator`.`group_id`, `Operator`.`created`, `Operator`.`modified`, `Operator`.`last_login`, `Operator`.`street`, `Operator`.`nr`, `Operator`.`bus`, `Operator`.`zip`, `Operator`.`city`, `Operator`.`country`, `Operator`.`phone`, `Operator`.`gsm`, `Operator`.`gender`, `Operator`.`birthdate`, `Operator`.`clanId`, `Operator`.`clantrust`, `Operator`.`clanjoinId`, `Operator`.`hwbudget`, `Operator`.`education`, `Operator`.`profession`, `Operator`.`hoursaweek`, `Operator`.`language`, `Operator`.`oldId`, `Operator`.`receive_newsletter`, `Operator`.`imageUrl`, `Operator`.`slug`, `Operator`.`fb_link`, `Operator`.`fb_location`, `Operator`.`CPU`, `Operator`.`MOBO`, `Operator`.`GFX`, `Operator`.`RAM`, `Operator`.`steamName`, `Operator`.`steamId`, `Operator`.`originName`, `Operator`.`lolSummonerName`, `Operator`.`Other`, `Operator`.`comment`, `Operator`.`seat_id`, `Operator`.`msg_notifications`, `Operator`.`mouseHand`, `Operator`.`deviceId`, `Operator`.`alternative_login`, `Product`.`id`, `Product`.`name`, `Product`.`slug`, `Product`.`description`, `Product`.`imageUrl`, `Product`.`priceExclVat`, `Product`.`priceInclVat`, `Product`.`vatId`, `Product`.`offeredFrom`, `Product`.`offeredUntil`, `Product`.`stock`, `Product`.`totalItems`, `Product`.`productTypeId`, `Product`.`productCategory`, `Product`.`eventId`, `Product`.`active`, `Order`.`id`, `Order`.`defaultPaymentProviderId`, `Order`.`orderStateId`, `Order`.`refundable`, `Order`.`memberId`, `Order`.`orderDate`, `Order`.`orderDueDate`, `Order`.`totalPriceIncVat`, `Order`.`orderNumber`, `Order`.`notes`, `Order`.`orderWarningSent`, `Order`.`orderWarningDate`, `Order`.`paypal_verification`, `Order`.`transactionFee`, `Type`.`id`, `Type`.`name` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`eventId` = 46 AND `Ticket`.`ownerId` = 4547 LIMIT 1	1	1	22	maybe slow
SELECT `Seat`.`id`, `Seat`.`seatmapId`, `Seat`.`ticketId`, `Seat`.`seatNumber`, `Seat`.`row`, `Seat`.`enabled`, `Seat`.`vip`, `Seat`.`date`, `Seat`.`reservedBy`, `Seatmap`.`id`, `Seatmap`.`eventId`, `Seatmap`.`enabled`, `Ticket`.`id`, `Ticket`.`typeId`, `Ticket`.`refundable`, `Ticket`.`eventId`, `Ticket`.`buyerId`, `Ticket`.`ownerId`, `Ticket`.`productId`, `Ticket`.`orderId`, `Ticket`.`statusId`, `Ticket`.`ticketNumber`, `Ticket`.`checkindate`, `Ticket`.`createDate`, `Ticket`.`voucher`, `Ticket`.`checkInOperator`, `Ticket`.`wristbandCodeId`, `Ticket`.`voucherOperator`, `Ticket`.`voucherReason`, `Ticket`.`bbq` FROM `fom_site`.`seats` AS `Seat` LEFT JOIN `fom_site`.`seatmaps` AS `Seatmap` ON (`Seat`.`seatmapId` = `Seatmap`.`id`) LEFT JOIN `fom_site`.`tickets` AS `Ticket` ON (`Seat`.`ticketId` = `Ticket`.`id`) WHERE `Seat`.`ticketId` = 19760 LIMIT 1	1	1	0
SELECT `Ticket`.`id`, `Ticket`.`statusId` FROM `fom_site`.`tickets` AS `Ticket` LEFT JOIN `fom_site`.`ticket_states` AS `TicketState` ON (`Ticket`.`statusId` = `TicketState`.`id`) LEFT JOIN `fom_site`.`events` AS `Event` ON (`Ticket`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Buyer` ON (`Ticket`.`buyerId` = `Buyer`.`id`) LEFT JOIN `fom_site`.`users` AS `Owner` ON (`Ticket`.`ownerId` = `Owner`.`id`) LEFT JOIN `fom_site`.`users` AS `Operator` ON (`Ticket`.`voucherOperator` = `Operator`.`id`) LEFT JOIN `fom_site`.`products` AS `Product` ON (`Ticket`.`productId` = `Product`.`id`) LEFT JOIN `fom_site`.`orders` AS `Order` ON (`Ticket`.`orderId` = `Order`.`id`) LEFT JOIN `fom_site`.`ticket_types` AS `Type` ON (`Ticket`.`typeId` = `Type`.`id`) WHERE `Ticket`.`ownerId` = 4547 AND `Ticket`.`eventId` = 46 ORDER BY `id` DESC LIMIT 1	1	1	0
SELECT `War`.`id`, `War`.`screen1B`, `War`.`screen2B`, `War`.`screen3B`, `War`.`screen4B`, `War`.`bracketType`, `War`.`compoId`, `War`.`teamA`, `War`.`teamB`, `War`.`scoreAByA`, `War`.`scoreBByA`, `War`.`scoreAByB`, `War`.`scoreBByB`, `War`.`finalScoreA`, `War`.`finalScoreB`, `War`.`winnerWarId`, `War`.`loserWarId`, `War`.`pouleId`, `War`.`level`, `War`.`playable`, `War`.`mapname`, `War`.`time`, `War`.`screen1A`, `War`.`screen2A`, `War`.`screen3A`, `War`.`screen4A`, `War`.`prevTeamA`, `War`.`prevTeamB`, `War`.`screen1Admin`, `War`.`screen2Admin`, `War`.`adminEditID`, `War`.`adminEditDate`, `War`.`finalScoreDate`, `Compo`.`id`, `Compo`.`name`, `Compo`.`steamGameId`, `Compo`.`nrPlayersTeam`, `Compo`.`maxTeams`, `Compo`.`compoTypeId`, `Compo`.`nrPoules`, `Compo`.`nrWinnersPoule`, `Compo`.`compoStateId`, `Compo`.`eventId`, `Compo`.`roundDE`, `Compo`.`addSecondaryFinal`, `Compo`.`adminId`, `Compo`.`adminId2`, `Compo`.`bannerUrl`, `Compo`.`description`, `Compo`.`tagId`, `Compo`.`allowDrawInPoule`, `Compo`.`nrLosersToBrackets`, `Compo`.`pauzed`, `Compo`.`rulebook`, `Compo`.`showsponsor`, `Compo`.`sponsorcontent`, `Compo`.`showfiles`, `Compo`.`filescontent`, `Compo`.`prizescontent`, `Compo`.`precompo`, `Compo`.`donations`, `Compo`.`donationAmount`, `Compo`.`schedule`, `Compo`.`faq`, `Compo`.`sponsorUrl`, `Compo`.`sponsorImg`, `Compo`.`sortTimeLabel`, `TeamA`.`id`, `TeamA`.`name`, `TeamA`.`leaderId`, `TeamA`.`compoId`, `TeamA`.`pouleId`, `TeamA`.`notes`, `TeamA`.`withdrew`, `TeamB`.`id`, `TeamB`.`name`, `TeamB`.`leaderId`, `TeamB`.`compoId`, `TeamB`.`pouleId`, `TeamB`.`notes`, `TeamB`.`withdrew`, `AdminEdit`.`id`, `AdminEdit`.`facebook_id`, `AdminEdit`.`username`, `AdminEdit`.`new_username`, `AdminEdit`.`nickname`, `AdminEdit`.`password`, `AdminEdit`.`firstname`, `AdminEdit`.`lastname`, `AdminEdit`.`active`, `AdminEdit`.`validationCode`, `AdminEdit`.`mailValidationCode`, `AdminEdit`.`group_id`, `AdminEdit`.`created`, `AdminEdit`.`modified`, `AdminEdit`.`last_login`, `AdminEdit`.`street`, `AdminEdit`.`nr`, `AdminEdit`.`bus`, `AdminEdit`.`zip`, `AdminEdit`.`city`, `AdminEdit`.`country`, `AdminEdit`.`phone`, `AdminEdit`.`gsm`, `AdminEdit`.`gender`, `AdminEdit`.`birthdate`, `AdminEdit`.`clanId`, `AdminEdit`.`clantrust`, `AdminEdit`.`clanjoinId`, `AdminEdit`.`hwbudget`, `AdminEdit`.`education`, `AdminEdit`.`profession`, `AdminEdit`.`hoursaweek`, `AdminEdit`.`language`, `AdminEdit`.`oldId`, `AdminEdit`.`receive_newsletter`, `AdminEdit`.`imageUrl`, `AdminEdit`.`slug`, `AdminEdit`.`fb_link`, `AdminEdit`.`fb_location`, `AdminEdit`.`CPU`, `AdminEdit`.`MOBO`, `AdminEdit`.`GFX`, `AdminEdit`.`RAM`, `AdminEdit`.`steamName`, `AdminEdit`.`steamId`, `AdminEdit`.`originName`, `AdminEdit`.`lolSummonerName`, `AdminEdit`.`Other`, `AdminEdit`.`comment`, `AdminEdit`.`seat_id`, `AdminEdit`.`msg_notifications`, `AdminEdit`.`mouseHand`, `AdminEdit`.`deviceId`, `AdminEdit`.`alternative_login` FROM `fom_site`.`wars` AS `War` LEFT JOIN `fom_site`.`compos` AS `Compo` ON (`War`.`compoId` = `Compo`.`id`) LEFT JOIN `fom_site`.`teams` AS `TeamA` ON (`War`.`teamA` = `TeamA`.`id`) LEFT JOIN `fom_site`.`teams` AS `TeamB` ON (`War`.`teamB` = `TeamB`.`id`) LEFT JOIN `fom_site`.`users` AS `AdminEdit` ON (`War`.`adminEditID` = `AdminEdit`.`id`) WHERE NOT (`War`.`finalScoreA` IS NULL) AND ((`War`.`teamA` = 10265) OR (`War`.`teamB` = 10265)) ORDER BY `War`.`compoId` DESC	6	6	1	maybe slow
SELECT `Compo`.`id`, `Compo`.`name`, `Compo`.`steamGameId`, `Compo`.`nrPlayersTeam`, `Compo`.`maxTeams`, `Compo`.`compoTypeId`, `Compo`.`nrPoules`, `Compo`.`nrWinnersPoule`, `Compo`.`compoStateId`, `Compo`.`eventId`, `Compo`.`roundDE`, `Compo`.`addSecondaryFinal`, `Compo`.`adminId`, `Compo`.`adminId2`, `Compo`.`bannerUrl`, `Compo`.`description`, `Compo`.`tagId`, `Compo`.`allowDrawInPoule`, `Compo`.`nrLosersToBrackets`, `Compo`.`pauzed`, `Compo`.`rulebook`, `Compo`.`showsponsor`, `Compo`.`sponsorcontent`, `Compo`.`showfiles`, `Compo`.`filescontent`, `Compo`.`prizescontent`, `Compo`.`precompo`, `Compo`.`donations`, `Compo`.`donationAmount`, `Compo`.`schedule`, `Compo`.`faq`, `Compo`.`sponsorUrl`, `Compo`.`sponsorImg`, `Compo`.`sortTimeLabel`, `Event`.`id`, `Event`.`name`, `Event`.`description`, `Event`.`starttime`, `Event`.`endtime`, `Event`.`location`, `Event`.`street`, `Event`.`nr`, `Event`.`bus`, `Event`.`zip`, `Event`.`city`, `Event`.`country`, `Event`.`slug`, `Event`.`oldId`, `Event`.`nrParticipants`, `Event`.`bbq`, `Event`.`usedHal`, `Admin`.`id`, `Admin`.`facebook_id`, `Admin`.`username`, `Admin`.`new_username`, `Admin`.`nickname`, `Admin`.`password`, `Admin`.`firstname`, `Admin`.`lastname`, `Admin`.`active`, `Admin`.`validationCode`, `Admin`.`mailValidationCode`, `Admin`.`group_id`, `Admin`.`created`, `Admin`.`modified`, `Admin`.`last_login`, `Admin`.`street`, `Admin`.`nr`, `Admin`.`bus`, `Admin`.`zip`, `Admin`.`city`, `Admin`.`country`, `Admin`.`phone`, `Admin`.`gsm`, `Admin`.`gender`, `Admin`.`birthdate`, `Admin`.`clanId`, `Admin`.`clantrust`, `Admin`.`clanjoinId`, `Admin`.`hwbudget`, `Admin`.`education`, `Admin`.`profession`, `Admin`.`hoursaweek`, `Admin`.`language`, `Admin`.`oldId`, `Admin`.`receive_newsletter`, `Admin`.`imageUrl`, `Admin`.`slug`, `Admin`.`fb_link`, `Admin`.`fb_location`, `Admin`.`CPU`, `Admin`.`MOBO`, `Admin`.`GFX`, `Admin`.`RAM`, `Admin`.`steamName`, `Admin`.`steamId`, `Admin`.`originName`, `Admin`.`lolSummonerName`, `Admin`.`Other`, `Admin`.`comment`, `Admin`.`seat_id`, `Admin`.`msg_notifications`, `Admin`.`mouseHand`, `Admin`.`deviceId`, `Admin`.`alternative_login`, `Admin2`.`id`, `Admin2`.`facebook_id`, `Admin2`.`username`, `Admin2`.`new_username`, `Admin2`.`nickname`, `Admin2`.`password`, `Admin2`.`firstname`, `Admin2`.`lastname`, `Admin2`.`active`, `Admin2`.`validationCode`, `Admin2`.`mailValidationCode`, `Admin2`.`group_id`, `Admin2`.`created`, `Admin2`.`modified`, `Admin2`.`last_login`, `Admin2`.`street`, `Admin2`.`nr`, `Admin2`.`bus`, `Admin2`.`zip`, `Admin2`.`city`, `Admin2`.`country`, `Admin2`.`phone`, `Admin2`.`gsm`, `Admin2`.`gender`, `Admin2`.`birthdate`, `Admin2`.`clanId`, `Admin2`.`clantrust`, `Admin2`.`clanjoinId`, `Admin2`.`hwbudget`, `Admin2`.`education`, `Admin2`.`profession`, `Admin2`.`hoursaweek`, `Admin2`.`language`, `Admin2`.`oldId`, `Admin2`.`receive_newsletter`, `Admin2`.`imageUrl`, `Admin2`.`slug`, `Admin2`.`fb_link`, `Admin2`.`fb_location`, `Admin2`.`CPU`, `Admin2`.`MOBO`, `Admin2`.`GFX`, `Admin2`.`RAM`, `Admin2`.`steamName`, `Admin2`.`steamId`, `Admin2`.`originName`, `Admin2`.`lolSummonerName`, `Admin2`.`Other`, `Admin2`.`comment`, `Admin2`.`seat_id`, `Admin2`.`msg_notifications`, `Admin2`.`mouseHand`, `Admin2`.`deviceId`, `Admin2`.`alternative_login`, `CompoState`.`id`, `CompoState`.`name`, `Tag`.`id`, `Tag`.`tagName`, `Tag`.`bannerUrl`, `Tag`.`parentId`, `Tag`.`slug`, `Tag`.`color` FROM `fom_site`.`compos` AS `Compo` LEFT JOIN `fom_site`.`events` AS `Event` ON (`Compo`.`eventId` = `Event`.`id`) LEFT JOIN `fom_site`.`users` AS `Admin` ON (`Compo`.`adminId` = `Admin`.`id`) LEFT JOIN `fom_site`.`users` AS `Admin2` ON (`Compo`.`adminId2` = `Admin2`.`id`) LEFT JOIN `fom_site`.`compo_states` AS `CompoState` ON (`Compo`.`compoStateId` = `CompoState`.`id`) LEFT JOIN `fom_site`.`tags` AS `Tag` ON (`Compo`.`tagId` = `Tag`.`id`) WHERE `Compo`.`id` = 367 ORDER BY `Compo`.`id` ASC LIMIT 1	1	1	1
SELECT `Teams`.`id`, `Teams`.`name`, `Teams`.`leaderId`, `Teams`.`compoId`, `Teams`.`pouleId`, `Teams`.`notes`, `Teams`.`withdrew` FROM `fom_site`.`teams` AS `Teams` WHERE `Teams`.`compoId` = (367)	11	11	0
SELECT `Wars`.`id`, `Wars`.`screen1B`, `Wars`.`screen2B`, `Wars`.`screen3B`, `Wars`.`screen4B`, `Wars`.`bracketType`, `Wars`.`compoId`, `Wars`.`teamA`, `Wars`.`teamB`, `Wars`.`scoreAByA`, `Wars`.`scoreBByA`, `Wars`.`scoreAByB`, `Wars`.`scoreBByB`, `Wars`.`finalScoreA`, `Wars`.`finalScoreB`, `Wars`.`winnerWarId`, `Wars`.`loserWarId`, `Wars`.`pouleId`, `Wars`.`level`, `Wars`.`playable`, `Wars`.`mapname`, `Wars`.`time`, `Wars`.`screen1A`, `Wars`.`screen2A`, `Wars`.`screen3A`, `Wars`.`screen4A`, `Wars`.`prevTeamA`, `Wars`.`prevTeamB`, `Wars`.`screen1Admin`, `Wars`.`screen2Admin`, `Wars`.`adminEditID`, `Wars`.`adminEditDate`, `Wars`.`finalScoreDate` FROM `fom_site`.`wars` AS `Wars` WHERE `Wars`.`compoId` = (367)	46	46	0

Query Explain:

Click an "Explain" link above, to see the query explanation.

====

Timer

Memory

Peak Memory Use 9.26 MB

Message	Memory use
Component initialization	2.06 MB
Controller action start	4.32 MB
Controller render start	7.47 MB
View render complete	8.34 MB

Timers

Total Request Time: 239 (ms)

Message	Time in ms	Graph
Core Processing (Derived from $_SERVER["REQUEST_TIME"])	7.83
Event: Controller.initialize	39.17
Event: Controller.startup	0.47
Controller action	84.48
Event: Controller.beforeRender	2.17
» Processing toolbar data	2.06
Rendering View	76.05
» Event: View.beforeRender	0.05
» Rendering APP/View/Teams/view.ctp	72.82
» Event: View.afterRender	0.05
» Event: View.beforeLayout	0.03
» Rendering APP/View/Layouts/default.ctp	1.68
» » Rendering APP/View/Elements/frontend/mobile-menu.ctp	0.19
» » Rendering APP/View/Elements/frontend/top_navigation.ctp	0.54
» » » Rendering APP/View/Elements/frontend/top_navigation_menu.ctp	0.25
» » Rendering APP/View/Elements/frontend/footer.ctp	0.16
Event: View.afterLayout	0.00

====

Log
+

Logs

There were no log entries made this request

====
Variables
+
View Variables
- wars(array)
 0(array)
 War(array)
 id28182
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10324
 teamB10265
 scoreAByA0
 scoreBByA16
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA0
 finalScoreB16
 winnerWarId28189
 loserWarId28196
 pouleId(null)
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 13:17:36
 Compo(array)
 id367
 nameGRAND - CS:GO
 steamGameId(null)
 nrPlayersTeam5
 maxTeams64
 compoTypeId0
 nrPoules3
 nrWinnersPoule4
 compoStateId5
 eventId46
 roundDE2
 addSecondaryFinal(false)
 adminId8749
 adminId2(null)
 bannerUrl(null)
 description<h1>password to the servers: war</h1> 
 tagId31
 allowDrawInPoule1
 nrLosersToBrackets0
 pauzed0
 rulebookFrag-o-Matic 24.0 Rulebook Counter-Strike:Global Offensive (CS:GO) Introduction This is the official rulebook for the Frag-o-Matic 24.1 CS:GO competition, that will take place from the 1st until the 3rd of September 2023. These rules apply to the players throughout all stages of CS:GO competition. Failure to adhere to these rules may be penalized as outlined. It should be noted that the tournament administrators have the final word, and have the power to decide on any circumstances that are not outlined by this document, and in extreme cases may overrule the rulebook in order to preserve fair play and sportsmanship. Frag-o-Matic reserves the right to change these rules at any time. The CS:GO admin team wishes you good luck in the tournament and hopes that you have an enjoyable competition. We’ll do our utmost best to make it fair, fun and exciting for everyone involved. <a name="navigation"></a>Table of contents <ol> <li><a href="#admin">Admins and communication</a></li> <li><a href="#compo">Compo overview</a> <ol> <li><a href="#participants">Participants</a></li> <li><a href="#teamsheets">Team sheets</a></li> <li><a href="#teamnames">Team names</a></li> <li><a href="#teammanager">Team manager / coach</a></li> <li><a href="#teamcaptain">Team captain</a></li> <li><a href="#players">Players</a> <ol> <li><a href="#grstandard">Grooming standards</a></li> </ol> </li> <li><a href="#cheating">Cheating</a> <ol> <li><a href="#forbiditems">Forbidden items</a></li> </ol> </li> <li><a href="#match">Match protests and forfeit</a> <ol> <li><a href="#definitions">Definition</a></li> <li><a href="#matchprotest">Match protest rules</a></li> <li><a href="#forfeitrules">Forfeit rules</a></li> </ol> </li> <li><a href="#seeding">Seeding</a></li> </ol> </li> <li><a href="#general">General</a> <ol> <li><a href="#generalrules">General rules</a></li> <li><a href="#sanctions">Sanctions and disputes</a></li> <li><a href="#confidentiality">Confidentiality</a></li> <li><a href="#coc">Code of conduct</a></li> <li><a href="#drugsalcohol">Drugs and alcohol</a></li> <li><a href="#betting">Betting</a></li> <li><a href="#addagreement">Additional agreements</a></li> <li><a href="#streaming">Streaming, interviews and media</a> <ol> <li><a href="#broadcasting">Broadcasting</a></li> <li><a href="#matchmedia">Match media</a></li> <li><a href="#screenshots">Screenshots</a></li> </ol> </li> <li><a href="#playerchanges">Player changes</a></li> <li><a href="#prizemoney">Prize money</a></li> </ol> </li> <li><a href="#csgorules">Counter-Strike:Global Offensive rules</a> <ol> <li><a href="#tournament">Tournament structure and time schedule</a> <ol> <li><a href="#penalties">Penalties and forfeits during the time schedule</a></li> <li><a href="#compomaxteams">Compo sign-up and max teams</a></li> <li><a href="#structure">Structure</a></li> <li><a href="#gamesetup">Game setup</a></li> <li><a href="#vetosystem">Veto system</a></li> <li><a href="#compospecificrules">Compo specific rules</a></li> <li><a href="#usageofpause">Usage of pause</a></li> <li><a href="#demofiles">Demo files</a></li> </ol> </li> <li><a href="#matchprocedure">Match procedure</a> <ol> <li><a href="#maplist">Map list</a></li> <li><a href="#matchrules">Match rules</a></li> <li><a href="#clientrules">Client rules</a></li> <li><a href="#illegalscripts">Illegal scripts</a></li> <li><a href="#customfiles">Custom files</a></li> <li><a href="#colordepth">Color depth and external programs</a></li> <li><a href="#illegalprograms">Illegal programs</a></li> <li><a href="#ingameoverlay">In-game overlays</a></li> <li><a href="#techprobs">Technical problems and disconnects</a></li> </ol> </li> <li><a href="#csgoserver">CS:GO server</a> <ol> <li><a href="#serversettings">Server settings</a></li> <li><a href="#servercrash">Server crash</a></li> <li><a href="#serverlag">Server (var) lag</a></li> <li><a href="#serverplugins">Server plugins</a></li> <li><a href="#rconusage">RCON usage</a></li> <li><a href="#warmupservers">Warmup servers</a></li> </ol> </li> </ol> </li> <li><a href="#copyright">Copyright Notice</a></li> </ol> <a name="admin"></a>1. Admins and communication <hr /> Communication before the LAN: <ul> <li>General contact > <a href="mailto:csgo@fom.be">csgo@fom.be</a></li> </ul> Please email us any feedback before and after the LAN event. CS:GO admin team: <ul> <li>Dragon <ul> <li>Steam: https://steamcommunity.com/profiles/76561198244170010/</li> <li>Discord: dragon (main communication line)</li> </ul> </li> </ul> Communication during the LAN: The communication during the LAN will be through Steam, Discord or at the Compo Desk. We will be available as much as possible in the <a href="https://discord.gg/URX6v82Wmp" target="_blank">#csgo channel</a>. We will use this as a second channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #csgo channel. Discord will be our main communication channel. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compo"></a>2. Compo overview <hr /> <a name="participants"></a> 2.1 Participants Due to lack of time, we have a tight schedule. Therefore we can make the decision to force teams to only participate in 1 grand compo! We will contact the teams who are signed in for 2 grand compo’s at the moment and they will need to make a choice. When a team refuses, we will remove them from the competition to make room for other teams. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamsheets"></a> 2.2 Team sheets As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops. A rule violation by any player in a team may lead the tournament admins to sanction the entire team, even if the rest of the team was not aware of the violation. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamnames"></a> 2.3 Team names <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teammanager"></a> 2.4 Team manager / coach The team manager does not have any responsibilities. The team manager is eligible to play for his team in matches, providing he’s indicated as a “Player” on the team in the team sheet. The communication with the team will not go via the team manager, all communication will go via the team captain! Spectators are not allowed on our servers. Only tournament admins may be in spectator mode during a match. The only exception is: coaches are allowed to spectate a match using the coach's command, only if the tournament admin is notified, and thus to spectate their team only. They are obligated to use the “coach t” or “coach ct” command before the match start and aren’t allowed to join after a match has been started. If noticed that the coach is abusing this rule, the team will get punished for it (e.g. round loss, side loss or match loss). During a match, the coach may only communicate with the players during freeze-time, warm up, half-time, or during one of the 4 timeouts. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamcaptain"></a> 2.5 Team captain We consider the one who registered the team into the compo on the Frag-o-Matic website as captain! The clan leader or team captain is responsible for his team and all the players in that team. It is recommended that the team captain is fluent in English or Dutch, as he will be required to communicate with the tournament admins. The team captain must read and understand the rulebook. The team captain is responsible for ensuring his team and players adhere to the rules. Ignorance of the rules is not an excuse for rule violations. The team captain may choose at any time to nominate another player in or manager of his team as team captain for any reason. Such nominations must be reported by the team captain, either in person or in writing, to the admins before the game starts. All official communication between a competing team and the tournament admins must be conducted by the team captain. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="players"></a> 2.6 Players All players must read and understand the CSGO rulebook. Any player in violation of a rule, will be sanctioned as described in this rulebook. Each team must have five players on the match server at the match start time as indicated by the schedule, unless permission has been granted by the tournament admins to play with less than five players. Only players registered for a team in the tournament may play for that team unless otherwise discussed with the tournament admin. All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins. Players registered for a team in the tournament may not play for any other team in the same tournament. Each player has to use their nickname that is similar to the nickname he/she has entered on their fom.be account. All players for a team must be clearly identifiable in-game with a uniform tag for that team and a separate, noticeably different nickname for each player. Players may not significantly change their nickname during the tournament. Any nickname they use during the tournament must always obviously visibly correspond to their original nickname. You are not allowed to change your nickname in-game. If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning. 3 warnings are equal to a forfeit in 1 match. Player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate. Make sure your steam account is linked with your fom.be account corresponding to your nickname. Players are strictly prohibited from using any other person’s steam account for any reason whatsoever during the CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="grstandard"></a> 2.6.1 Grooming standards People participating in the CS:GO tournament are expected to normal grooming standards. You may be asked to take action if you or your clothing have a look or odor that’s offensive to other players. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="cheating"></a> 2.7 Cheating During Frag-o-Matic we won’t investigate cheaters from an external event. When we discover someone cheating during our LAN, that player and his team will be banned from the compo and the player will be also banned for the next Frag-o-Matic edition. Furthermore we will investigate reports of players cheating during other tournaments until 2 weeks before the LAN. When a player is discovered cheating during another tournament/platform 12 months before the event occurs, then that player will not be allowed to play on that edition of Frag-o-Matic within the CS:GO competition and the edition after that. If one of the following rules apply, then that player will not be allowed to compete in our tournament: Caught cheating within a tournament/platform 12 months before the start date of our event. There needs to be enough evidence for that player, that he/she was cheating and the tournament admins will judge if the evidence is valid OR if he/she was caught cheating on the following platforms: <ul> <li><a href="ts3server://ts.fom.lan">ts.fom.lan</a> - CS:GO admin channel</li> <li>Discord: <a href="https://discord.gg/MbPY2ge">https://discord.gg/MbPY2ge</a> <ul> <li>Teams are only allowed to use a uniform team name for their team.</li> <li>Teams may not change their team name during the tournament.</li> <li>Teams may not change their team in-game tag during the tournament, unless none was set.</li> <li>Duplicating team names of other teams is not allowed.</li> <li>Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.</li> <li>Team names are not allowed to be offensive.</li> <li>Please make sure your team name is filled in on your fom.be profile.</li> </ul> <ul> <li>Faceit</li> <li>Esl</li> <li>Valve (vac ban for any Counter strike: Global Offensive game)</li> <li>ESEA</li> <li>Cevo</li> </ul> </li> <li>When a player is caught selling or buying cheats. In any case the admin will have the final decision. This means that the admin will review the evidence and make the final call. If a player shows the intention of coming to our tournament to cheat and we’re provided evidence of this. Everyone from the community may send evidence to csgo@fom.be, when they suspect someone participating at Frag-o-Matic of cheating. All forms of cheating in matches are forbidden, and will result in an overall forfeit in the tournament. Possibilities for cheating in Counter-Strike:Global Offensive are, for example; all kinds of multi-hacks, wallhack, aimbot, colored models, no-recoil, no-smoke, no-flash and sound changes. All hardware or software that has an influence on the game in such a way that the essence of the game is affected are banned from this tournament. Any use of this kind of hardware will result in a disqualification of the tournament as it will be recognized as cheating. When proven that a player is not cooperating in his own ban research or is lying on purpose. He will get banned for 1 edition. You can find our banlist at http://www.fom.be/contents/view/cs-go-banlist The mentioned people in our ban list are not allowed in the CS:GO tournaments at Frag-O-Matic until the edition that’s stated there. When these people compete under a false name nonetheless or try to circumvent the rules then they will receive an extended or permanent ban. Here are some of the other examples of ways to gain advantages, this list may not be the full list but if players are unsure of certain things, they should seek to ask the tournament admins first: Flash Bang, Smoke Grenade, and Hand Grenade Bugs - it is illegal to use any flash bang, smoke grenade, or hand grenade bugs, regardless of intent. Silent Bomb Plants - ALL bomb plants must be done in a position where your opponents can hear you. There should be no rotation in players to gain money advantages throughout a match. The bomb must be planted on solid surfaces on the map, ie where an opponent can defuse from, so not up in the air or floating. Illegal Bomb Defuses - No player can defuse a bomb through any other solid object on the map, it has to be done in clear view. It is also forbidden to try to intentionally distort your hitboxes during a defuse situation to prevent an opponent from killing you in game. Walking/Boosting through walls - No player should walk, boost through walls or roofs. To do so will see your team penalized for that round. Map Exploits - Boosts that include the use of clipping are strictly forbidden. The term “Clipping” defines that when a player is boosted can see through certain parts of the map (ie over/under walls, or through solid objects on the map). If any player or team feels unsure on a new advantage they have found through their practice sessions, they are welcome to show this specific spot to the tournament team to review. Any player or team that does this will be treated to the strictest confidence as not to jeopardize your strategic advantage, however we can rule on whether it is a legal move. We strongly advise teams to give us plenty of time ahead of an event so we can review it in good time and make good judgement on it. The game admins may inspect your machine at any time throughout the event to inspect for cheats or hacks within your game files, steam cloud and anywhere on your PC or memory sticks. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="forbiditems"></a>2.7.1 Forbidden items During the lan, to prevent cheating by using external devices or items, the following items are forbidden: <ul> <li>Smartwatches; Having or carrying a smartwatch during the event, when competing in the CS:GO competition, that player will immediately be disqualified from the competition.</li> <li>Alienware Wireless Headset AW988; Visual representation of audio isn’t allowed.</li> <li>AR (augmented reality) glasses</li> <li>Hardware from the brand “Bloody” (these are mice that come with software that reduces recoil on weapons)</li> </ul> Any other electronic devices (like smartphones) that are used during a match will be considered suspicious and we’ll ask that they’re not used. If, during a match, the suspicious device is still in use; the team of the player using the device will receive a warning. After 3 warnings the team will receive a disqualification from the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="match"></a>2.8 Match protests and forfeit <a name="definitions"></a> 2.8.1 Definition A protest is a raised issue for problems that affect the match outcome; a protest may even be filed during a match for things like incorrect server settings and other related issues. A protest is the official communication between a team captain and a tournament admin. A forfeit is a lose or surrender. <a name="matchprotest"></a> 2.8.2 Match protest rules Participants are only allowed to issue a match protest before the beginning of their next match. The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “they are cheaters” will not be enough. Insults and flaming are strictly prohibited in a protest, and may result in the protest being ruled against the insulting party. <a name="forfeitrules"></a> 2.8.3 Forfeit rules A forfeit can be called for a single match or the entire competition from a competing team for their team. Only the team captain can raise a forfeit for their team. A forfeit can also be raised by an admin as a penalty for wrongdoing. For example, in most cases where a competing team doesn’t follow the time schedule. The tournament admins can always force a forfeit. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="seeding"></a>2.9 Seeding Seeding is done through an objective outlook towards data provided by all participants for every event. Every participant is required to provide us their main steam account, ESEA and/or CEVO profile, FACEit level and previous wins/achievements. The supplied data is only kept and used for one event to calculate an individual “score” based on reached rank, played time, csgo hours and historical performance/achievements from Frag-o-Matic or other tournaments. The team sum of 5 individual scores will show an objective score where the higher the score, the higher the team seeding. The tournament admins won’t seed teams higher based on any subjective opinions. If no statistical data was provided for all 5 team member, than that team will be seeded beyond top 16. <a name="general"></a>3. General <hr /> <a name="generalrules"></a> 3.1 General rules Frag-o-Matic Counter strike:Global Offensive (CS:GO) 5v5 tournament is a local area network (LAN) tournament. By competing in this tournament, teams and players accept these rules in full. Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation. In the beginning of the LAN the team captains can sit together with the admin to discuss the rules and to make adjustments if needed. The decisions are made by the admin. If you have any issues with the rules, you can explain this by sending an email to <a href="mailto:csgo@fom.be">csgo@fom.be</a> up to one week before the start of the event. Clarification of any point in the rules is available from the tournament admins at any time during the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="sanctions"></a>3.2 Sanctions and disputes Sanctions and disputes will be resolved by the main tournament admin. The admin’s decision on any sanction or dispute is final. Abusive behavior towards the Frag-o-Matic staff, tournament admins or opponents at any time during the tournament is unacceptable and will be punished with warnings. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="confidentiality"></a>3.3 Confidentiality The content of protests, support communication, discussions or any other correspondence with tournament officials and administrators are considered as strictly confidential. The publication of such material is prohibited. If the contents has been shared without consent then this could lead to a team’s disqualification. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="coc"></a>3.4 Code of conduct Any form of aggression<a href="#coc_aggression">*</a> (both verbally and physically) will not be tolerated. Any and all physical aggression will be sanctioned with an immediate disqualification by that person or team performing the physical act (both actioned and reactioned). Any verbal aggression will be sanctioned by a time-out for that person or team. A time-out is either set in time (hours/day) or in amount of matches when a player or team is not allowed to participate in the CS:GO competition. Any situation that is about to escalate should be dealt with in a calm and diplomatic manner. An audience with any Frag-o-Matic crew member (CS:GO admin or Frag-o-Matic team leaders) can always be called for at any time during the event. Keep in mind that this audience can not be used to waste time or get a time advantage. At any point, the CS:GO tournament admins can decide to continue with the competition with or without consent from either players or other Frag-o-Matic staff. In the event when a single player or more are accused of cheating, the event will continue nonetheless. Evidence will be presented to the tournament admins and a call will be made at a later stage of the event. This rule is set to not cause any delays and have the situation under control. Any player(s) or team(s) ignoring this rule will receive a forfeit. Any player or team ignoring a CS:GO admin will be sanctioned with a warning. 3 warnings are equal to a forfeit of 1 match. <a name="coc_aggression"></a>*A form of aggression is described as: <ul> <li>Instrumental aggression -- Aggression aimed at obtaining an object, privilege or space with no deliberate intent to harm another person. Typical of participants wanting to get ahead of the competition with lies, anger, bullying, criticizing other people behind their backs, leaving others out of a group or otherwise ostracizing them, turning people against each other, dismissing the opinions of others (passive aggression).</li> <li>Hostile aggression -- Aggression intended to harm another person, such as hitting/kicking/biting someone (active aggression). Threatening to beat up someone (nonverbal intimidation). Sending threatening messages through emails, phone calls, or social media, or making threats against someone's life, shouting, and swearing (verbal hostility). Breaking someone's computer, destroying someone's cell phone, or other forms of vandalism (destruction of property).</li> <li>Relational aggression -- A form of hostile aggression that does damage to another's peer relationships, as in social exclusion, gossiping or rumor spreading. Examples: Arguments within a team after a lose that lead to a verbal fight.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="drugsalcohol"></a>3.5 Drugs and alcohol To play a match under the influence of any drugs or performance enhancers is strictly prohibited, and may be punished with exclusion from the tournament. If an admin finds that a player is not capable of competing in the competition because of intoxication, the admin can exclude that person from the entire tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="betting"></a>3.6 Betting Betting on any match in the CS:GO tournament is strictly forbidden. <a name="addagreement"></a>3.7 Additional agreements Teams may be required to play any match on the stage. If so, teams will be notified at least 20 minutes prior to the start time of that match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="streaming"></a>3.8 Streaming, interviews and media <a name="broadcasting"></a>3.8.1 Broadcasting Frag-o-Matic reserves the right to broadcast any match or demo, teams may not refuse such broadcasts. All forms of client side game broadcasting are NOT allowed. Frag-o-Matic participants are not allowed to watch a local GOTV if a CS:GO server broadcasts a game. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchmedia"></a>3.8.2 Match media All match media (screenshots, demos, etc.) must be kept until the end of the event. Faking or manipulating match media is forbidden and will result in exclusion from the tournament. Match media should be named clearly based on what it is. It is not possible to file a protest to complain about bad match media naming. However if a tournament admin is hindered in their work because of bad match media naming, then a tournament admin will give a warning. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="screenshots"></a>3.8.3 Screenshots The admin can ask for screenshots of every game on any moment during the event. When he does this, the team leader has 15 minutes time to deliver the screenshot to the admin. A screenshot of the scoreboard at the end of each half must be taken. When this is not done by a team it can result in a lost match when one of the other teams complains about a score. An RCON status screenshot must be taken: <ul> <li>at the beginning of the match</li> <li>in case of a server/player change</li> <li>if a player reconnects</li> </ul> RCON status screenshots made with the help of programs like HLSW etc. are not sufficient. In order to take an RCON status you have to use the console command “rcon status” (don’t forget to enter your RCON password) and take a screenshot of that. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="playerchanges"></a>3.9 Player changes Teams are permitted to substitute players (only with another player not active in the CS:GO competition) during pauses and between rounds, if they have permission from the tournament admin. Consent for substitutions must be obtained from the tournament admins, and substitute players must be registered for that team in the tournament. You can make this clear to the admin by using the contact information in section ‘Admins and communication’. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="prizemoney"></a>3.10 Prize money When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="csgorules"></a> 4. Counter-Strike:Global Offensive rules <hr /> <a name="tournament"></a>4.1 Tournament structure and time schedule Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. On Saturday and Sunday, teams must be present at 10:00 (AM) and ready to start playing the rest of their scheduled matches. It can be the case that the tournament admins decide to start earlier or end later, but this will be communicated (to all team captains). An exact time schedule will be provided on our fom.be website for all teams to follow. Each match will have a start time on which the game needs to be started. The team(s) that are responsible where the start time has not been met will receive a forfeit for that match. Whether or not this rule will be applied, is the decision of a tournament admin. The schedule for the tournament may be subject to change at any time. Matches may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice. Games will not be rescheduled to an earlier time in the same day if either of the teams have not yet played a game on that day without the consent of both team captains. Where possible the tournament admins will notify any teams involved in a rescheduled game of the new match start time at least one hour before the new start time. In the event a match is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible. If there’s insufficient time to complete a match, the tournament admins may at any time declare one team as the winner, if that team holds a clear advantage in that match. It is the responsibility of the tournament admins to decide whether a team holds a clear advantage. This rule will only be used in the emergency when the remaining event time is a factor. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="penalties"></a>4.1.1 Penalties and forfeits during the time schedule If 1 or more teams are still playing a match in a previous stage or if 1 team is late and doesn’t start playing their match in the stage where they are; Teams are offered 30 minutes of grace time in both circumstances, after 30 minutes warnings are handed out: After 30 minutes that team, who’s still not playing their scheduled match, will receive a 1st warning from a tournament admin. A notice via our csgo channel on discord and if the team is present and found at their seat they’ll be warned in person as well. A second warning is given in the same manner 5 minutes after the first warning. A third and final warming is given in the same way 5 minutes after that. 5 minutes after the final warning the team who received 3 warnings will receive 1 game loss for their match in the next round. In case of a bo3 in the next round, a bo2 will be played with one win to the team that was on time. If after 15 minutes the team with 3 warnings and one loss in the next round is still not playing, they’ll receive a forfeit from an admin. In case of a bo1 (in the lower bracket for example) we won’t lose any more time and a forfeit will be forced. The forfeit is applied on our fom.be website and a notice is given on Discord in our csgo channel. The tournament admins will keep a record of the warnings and will communicate this to the compo desk. As mentioned in our general rulebook; Non-acceptable excuses for a delay: “We want to eat” isn’t a valid excuses for starting an argument at the compo desk. As a note, we ask that teams only take a maximum of 15 minute breaks in between games and matches to avoid any penalties. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compomaxteams"></a>4.1.2 Compo sign-up and max teams All compo sign-ups are done via our fom.be website. Some rules are already explained in our general rulebook. Any team that is not “full”, meaning the team doesn’t consist of minimum 5 players, will be removed from the compo sign-up one hour before the start of the competition. We allow a maximum 64 teams to register to our CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="structure"></a>4.1.3 Structure Our CS:GO tournament will use a poule system and 3 double elimination brackets (pro, semi-pro and fun). Each poule will consist out of 3-4 teams who will compete against each other to make it into the brackets. Each team within the poule needs to play against any other team within its poule. Following the poule stage, the 2 winners from each poule will advance to a pro bracket, the last 2 teams from each poule will advance to a semi-pro bracket and <s>other teams will proceed to the fun bracket</s>. Our compo structure will use the following setup for pro, semi-pro and fun: <ul> <li>Groupstage > BO1 (best of 1)</li> <li>Upper Bracket > BO3 (best of 3)</li> <li>Lower Bracket > BO1 (best of 1)</li> <li>Pro & semi-pro bracket: <ul> <li>Semi-final (Finals in lower bracket) > BO3 (best of 3)</li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> </li> <li><s>Fun bracket:</s> <ul> <li><s>Semi-final (Finals in lower bracket) > BO1 (best of 1)</s></li> </ul> </li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> When 2 teams have the same amount of points after the poules we will look at the following criteria in order: <ul> <li>The match between the 2 teams</li> <li>The won rounds total</li> <li>The lost rounds total</li> <li>Seeding</li> </ul> We can also look at other criteria if we feel that it's necessary (also cooperation). The admin is allowed to overrule these criteria. If there’s not enough data to validate a criteria the admin can chose to ignore it. A tournament admin can decide to change some matches from BO3 to BO1 or visa versa when needed. (For example: no time to play a BO3). <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="gamesetup"></a>4.1.4 Game setup Matches will be played 5on5. Playing with fewer than five players in any match is only allowed with permission from the tournament admins. Before a match starts, both teams must state that they are ready to start the match. The must do this by having one team member typing ‘ready’ in server chat. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated. Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug. You’ll need to use the following match setup to play every game: <ul> <li>2 teams join the server that is assigned to them on our fom website.</li> <li>The team captains can use the RCON password “godmode” to follow the next steps : <ul> <li>Don’t forget to do ‘cl_mute_enemy_team 0’</li> <li>Change the map to de_mirage (rcon changelevel de_mirage)</li> <li>Load the Frag-o-Matic config (rcon exec fom5on5.cfg)</li> <li>Start a knife round on de_mirage (optional). The winner of this knife round can decide who team A is. Start the map veto process (Veto is explained under ‘Veto system’’).</li> <li>After the Veto the team captain needs to change the map to the first map of Team A (in a BO3) or the single map that was chosen (in a BO1) (rcon changelevel ‘mapname’)</li> <li>Load the fom5on5.cfg again on this map. (rcon exec fom5on5.cfg)</li> <li>After this the teams do another knife round to decide which team will start on which side of the map. The winner of the knife round decides which side they want to start on and that team will also start the match. (rcon mp_restartgame 1)</li> </ul> </li> </ul> If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server can be paused at the end of the current round (see rule ‘Usage of pause’ function) by one of the teams. The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed. If a player/substitute doesn’t connect within that time, then the match is continued 4on5, or 4on4 if the opposing team agrees and the tournament admins are informed. There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="vetosystem"></a>4.1.5 Veto system Our veto process is the next step after playing a knife round, as described in ‘Game setup’. The map(s) chosen to be played in each BO1 and BO3 are done via elimination (i.e. veto). Where ‘team 1 = A’ and ‘team 2 = B’, with A being decided by the winner of the knife round. Teams can also decide who team A/B is without playing a knife round. The maps you don’t want to play as a team, should be the maps that you veto during this process. The veto process needs to be done in server chat. VETO rules best-of-1: ABABAB veto. The map pool exists out of 7 maps. 6 maps are vetoed during this process, 3 maps for each team. The remaining map is the map played in the best-of-1 match. VETO rules best-of-2: ABAB veto AB play. The map pool exists out of 7 maps. 4 maps are vetoed during this process, 2 maps for each team. Out of the 3 remaining maps, 1 team each gets to decide a map to play on. VETO rules best-of-3: A/B veto, A/B play and A/B veto. The map pool exists out of 7 maps. 4 maps are eliminated, and 3 maps are selected to play. Each team needs to veto a map, followed by each team choosing a map and again each team vetoing a map. The remaining map is the third map that needs to be played if both teams win a map. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compospecificrules"></a>4.1.6 Compo specific rules All matches in the group stage are played MR15. All matches in the brackets are played MR15 (meaning, 16 rounds won = game win). In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games are best of three (BO3) in the bracket, 3 maps are decided by veto. The grand final is a best of three (BO3) with map advantage! When in the brackets a game is tied an overtime needs to be played. The overtime will be played MR3 with 10.000$ start money. For the start of the overtime teams will stay on the side which they played the previous half on, during halftime sites will be swapped. Teams will continue to play overtimes until a winner has been found. We have our own special breed of bracket seeding. For more information please contact us in advance. This bracket seeding is law. Obey it. All CS:GO players can only use our ts.fom.lan (local) teamspeak for voice communication. Teams are only allowed to have 5 players + 1 coach in their teamspeak channel whilst in a competition match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="usageofpause"></a>4.1.7 Usage of pause Pauses may be taken for any reason. Teams are permitted 3 pauses per side in each match. Each pause having a maximum duration of 5 minutes, unless authorised by an admin to take a longer pause (in case of technical difficulties, for example). After a “pause”-event, an “unpause“-command needs to be done. Teams can’t unpause without the consent of the other team. Pauses may only be activated at the start of the next round during freeze time. So make sure you tell the other team before round end (in all-chat), that your team will take a pause in the next freeze time. Usage: Type the following commands in console, to activate and deactivate the pause event. Pause = rcon mp_pause_match Unpause = rcon mp_unpause_match Illegal usage: DON’T USE = sv_pause If a team does use sv_pause, they have to surrender 1 round. (by all team members typing “kill” in console) <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="demofiles"></a>4.1.8 Demo files GoTV demos must be active for each match to be recorded. It’s the responsibility of (both) team captains to ensure that GoTV is recording. If this isn’t the case, the tournament admins will be forced to make calls without a recording when a dispute occurs. It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A knife round is part of a match and should be recorded. At least one of the players must be able to upload the knife round on admin request. Protests regarding missing knife rounds are not valid. In general, defective or manipulated demos will be treated as missing demos. If the demo is incomplete, as decided by the admin, it also will be treated as missing demo. If a protest is opened for a match, all match media need to be kept until the end of the event. Demos can only be requested up to a maximum of 30 minutes after a match via the admin. A demo request must state which teams were playing, the name(s) of the map(s) the match(es) was/were played on, the time of the match(es) and the server IP address(es). If a player or a team illegally aborts the match, they lose their right to demand demos. Recording demos is recommended. Our servers will likely record demos for every match but these are only used when there is doubt about a decision the admin has to make. It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.2 Match procedure <a name="maplist"></a>4.2.1 Map list Only the following maps are allowed to be played on during the competition: <ul> <li>de_ancient</li> <li>de_anubis</li> <li>de_inferno</li> <li>de_mirage</li> <li>de_nuke</li> <li>de_overpass</li> <li>de_vertigo</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchrules"></a>4.2.2 Match rules <ul> <li>Diffusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.</li> <li>Throwing grenades/flash bangs/smokes across walls in maps is allowed.</li> <li>Boosting is not considered a bug.</li> <li>Buying and using multiple grenades is allowed but with a max of 2 flash bangs.</li> <li>Multiple grenades are allowed but max 2 flash bangs</li> <li>Bugs on the map must be checked before the match begins. Any protest after the match about map bugs will be ignored.</li> <li>If a player loses connection before the first kill, the match can be restarted. If this happens after the first kill, the server can be paused and have the disconnected player reconnect. Matches won’t be restarted due to disconnections.</li> <li>If you want a player change (sub) during the match, inform the opponent and the compo admins before the match begins!</li> <li>To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.</li> <li>Climbing with help of teammates is allowed in general.</li> <li>Throwing grenades inside walls is not allowed.</li> <li>Self-kills are strictly forbidden, unless an admin forces you to do this as a sanction for disobeying any rules.</li> <li>Bomb planting in a way it can’t be reached is forbidden.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="clientrules"></a>4.2.3 Client rules The admin is allowed to take over your computer before, during and after a game and have a look. Without the pc’s owner in question nearby, the person in question can appoint someone to stay with the admin to make sure no privacy issues are violated. Any trace evidence of cheats found on a player’s computer – even if such discovery took place outside of a game – can lead to exclusion from any competition. For NVIDIA graphics card users: The use of Ambient Occlusion is strictly forbidden. If you are caught using this setting, this will result in a direct loss of the match. Getting caught for a 2nd time will result in removal from the tournament. This setting can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings. The following commands are forbidden: <ul> <li>mat_hdr_enabled</li> </ul> The following startparameters are forbidden: <ul> <li>+mat_hdr_enabled 0/1</li> <li>+mat_hdr_leven 0/1/2</li> </ul> In your game client cfg-folder you’re only allowed to have config files. Pictures, demos, screenshots and zipped files are forbidden. All other configuration changes are allowed as long as they do not give an unfair edge or advantage comparable to cheating. The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary. Boosting through walls/ceilings/ground, sky walking, map swimming, floating and sharking are all forbidden. To throw grenades inside walls is not allowed. Above walls and roofs is allowed. To plant the bomb in a way that it cannot be reached is forbidden. Places that can be reached with help of a team mate are allowed as long as they are visible. Violating this rule will result in tournament administrators intervention. Changing graphic settings to irregular values can be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalscripts"></a>4.2.4 Illegal scripts In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts: <ul> <li>Stop Shoot scripts [Use or Awp scripts]</li> <li>Center view scripts</li> <li>Turn scripts [180° or similar]</li> <li>No Recoil scripts</li> <li>Burst fire scripts</li> <li>Rate changers (Lag scripts)</li> <li>FPS scripts</li> <li>Anti flash scripts or binding (snd_* bindings)</li> <li>Bunnyhop scripts</li> <li>Stop sound scripts</li> <li>Following Commands/CVars are forbidden</li> <li>+weapon_recoil_model 0 (Startparameter)</li> </ul> The following CVAR values must be used: <ul> <li>cl_bobcycle 0.98 (First Time->Warning)</li> </ul> If there are more than one player who used a wrong client setting, the match will be deleted. Exception: cl_bobcycle Using illegal scripts will be penalized if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized. The use of No-Flash and No-Recoil bindings/scripts in any and all forms will be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="customfiles"></a>4.2.5 Custom files The HUD can be changed as long as no information are deleted or falsified which are available in the standard HUD. If the HUD is changed it has to be readable. If an admin is hindered in his work due to an unreadable HUD, penalty points may be assigned. Protests or supports which adhere to this rule will not be admitted and are rejected directly. Apart from the HUD and the GUI no custom files are allowed. This also includes custom models, changed textures or sounds (volume, soundscapes) are forbidden. <a name="colordepth"></a>4.2.6 Color depth and external programs The usage of a color depth of 16bit is not allowed. The usage of external programs (ex. SweetFX, A3D,...) are not allowed to enhance vision. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalprograms"></a>4.2.7 Illegal programs Changing the game graphics or textures with the help of video card drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. NVidia SLI Display, Riva tuner Overlays) is illegal. Failure to comply with this rule will result in a punishment for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized. If you play with ambient occlusion, it will be punished as cheating!! Punishment will be given regardless of whether the script/binding is executed via external hardware or software. Also binding any snd_ command is forbidden. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="ingameoverlay"></a>4.2.8 In-game overlays All In-Game overlays – provided by the game itself – except the following are forbidden: <ul> <li>net_graph 0</li> <li>net_graph 1</li> <li>cl_showpos 1</li> <li>cl_showfps 1</li> <li>cl_showdemooverlay 1 / -1</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="techprobs"></a>4.2.9 Technical problems and disconnects If a disconnection occurs the game should automatically reconnect. When this doesn’t work, a tournament admin will decide what to do. The tournament admin will make a call in every possible scenario regarding the severity of the problem and how to deal with it. But, the following guidelines are in place in the event of a disconnect: <ul> <li>In the case where Frag-o-Matic is responsible for the disconnect, the round needs to be restored to the start of the round where the disconnection happened. I.e. follow the steps as described under “4.3.2 Server crash”.</li> <li>When a player is responsible for his own disconnect, the team with 4 players can decide to continue to play 4v5 or use a pause as described in “4.1.6 Usage of pause”.</li> <li>The disconnected player can then reconnect to the match. If that player fails to reconnect, then the match will continue 4v5.</li> <li>If another Frag-o-Matic participant is responsible for causing a problem, then the match needs to be paused and a tournament admin needs to be notified to make a call on what to do.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.3 CS:GO server <a name="serversettings"></a>4.3.1 Server settings Frag-o-Matic will supply hardware for all servers. All games related to the tournament must be played on these servers. All matches will be played using the latest version of CS:GO and the official Frag-o-Matic CS:GO server config. All matches have to be played on an official Frag-o-Matic CS:GO tournament server and on the provided server number (as listed on our fom.be website, in the csgo compo section). We’ll use a standard (ESL) 5v5 pro league tournament config on a 128 tickrate server: <ul> <li>Startmoney: 0</li> <li>Maxrounds: 30</li> <li>Roundtime: 1m 55s (1.92)</li> <li>Freezetime: 12 seconds</li> <li>C4timer: 40 seconds</li> <li>Pause: 1x 5minutes per half each map.</li> <li>Overtime: MR3 - .000 startmoney</li> <li>Time during half time: 13 seconds</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="servercrash"></a>4.3.2 Server crash In the event of a server crash, after notifying a tournament admin and having them restart the the server, both teams have to re-join the same server and use the following command: <ul> <li>rcon mp_backup_restore_list_files</li> </ul> This will show you the backup files before the server crashed. 1 team captain then executes the correct file by using the following command: <ul> <li>rcon mp_backup_restore_load_file</li> </ul> Example: rcon mp_backup_restore_load_file backup_round12.txt All previous settings (score, money, armor, weapons,...) are then reset to the round before the server crashed and the match is set to paused. To continue the match, use the unpause command: <ul> <li>rcon mp_unpause_match</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="serverlag"></a>4.3.3 Server (var) lag Teams are given the time to play a warm-up match on their server before every compo match if they wish to do so. It’s not allowed to switch to another server once the compo match has been started. Test the server before the match starts. Any server problems should be reported to a tournament admin by going to the compo desk after sending an email with the information below. In the event that you experience any lag during or before a match, please note the time(s) and contact us via Discord or the Compo Desk. We'll escalate this information and, if possible, provide a solution for upcoming matches. The statement or report of (possible) lag in a match is a not valid argument in a protest. However, sending us the data above will give your team the time necessary to avoid any possible forfeits when you notify us at the compo desk after sending your email. Failure in providing us this data will not allow your team to deviate from our time schedule. We strive to provide all our servers lag free. We would like to thank you in helping us improve our servers. <a name="serverplugins"></a>4.3.4 Server plugins No extra plugins will be installed on our CS:GO servers. <a name="rconusage"></a>4.3.5 RCON usage RCON is only allowed as described in “4.1.2 Game setup”. Usage of RCON outside the game setup is penalised by receiving an instant forfeit for the team using any other RCON commands. We monitor all servers and RCON logs and will use this as evidence to hand out a match forfeit to the team using RCON outside of the game setup rules. <a name="rconusage"></a>4.3.6 Warmup servers Subject to availability, we will provide warmup servers. The settings will mirror our war servers as close as possible, but won’t be managed by the csgo team. Participants in our competition are allowed to use our warmup servers as such, to warm up, practice nade throws, practice aim,etc… We will not guarantee availability of those servers, since they will depend on the overall capacity. If warmup servers are available, they cannot ever be used for playing matches. If a match has been played on one of those servers though, the end-scores will still count. It is the responsibility of both teams the correct (assigned) server is joined. At any time, we can convert one of those servers to an official war server (In cases of need). It will at that point no longer show up as a warmup server. <a name="copyright"></a>5. Copyright Notice Copyright © 2005-2022 by E-EVENTS VZW All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher, addressed at <a href="mailto:csgo@fom.be">csgo@fom.be</a> </li> </ul>
 showsponsor(false)
 sponsorcontent
 showfiles(false)
 filescontent
 prizescontent<h1> First Place </h1> <ul> <li> <h3>525 €</h3> </li> </ul> <h1>Second Place</h1> <ul> <li> <h3>315 €</h3> </li> </ul> <h1>Third Place</h1> <ul> <li> <h3>210 €</h3> </li> </ul>
 precompo(false)
 donations0
 donationAmount0
 scheduleregistration closes at 21! please make sure all games are played on time! poules will be made and will be playable. saturday 10am we will start with the brackets semi final will be at 10am on sunday with afterwards the grand final Have fun and Good luck!
 faq
 sponsorUrl
 sponsorImg(null)
 sortTimeLabel0
 TeamA(array)
 id10324
 nameSM1L3RS
 leaderId9989
 compoId367
 pouleId1454
 notes
 withdrew(false)
 TeamB(array)
 id10265
 nameBASTARDS.AF9K
 leaderId5352
 compoId367
 pouleId1452
 notes
 withdrew(false)
 AdminEdit(array)
 id(null)
 facebook_id(null)
 username(null)
 new_username(null)
 nickname(null)
 password(null)
 firstname(null)
 lastname(null)
 active(null)
 validationCode(null)
 mailValidationCode(null)
 group_id(null)
 created(null)
 modified(null)
 last_login(null)
 street(null)
 nr(null)
 bus(null)
 zip(null)
 city(null)
 country(null)
 phone(null)
 gsm(null)
 gender(null)
 birthdate(null)
 clanId(null)
 clantrust(null)
 clanjoinId(null)
 hwbudget(null)
 education(null)
 profession(null)
 hoursaweek(null)
 language(null)
 oldId(null)
 receive_newsletter(null)
 imageUrl(null)
 slug(null)
 fb_link(null)
 fb_location(null)
 CPU(null)
 MOBO(null)
 GFX(null)
 RAM(null)
 steamName(null)
 steamId(null)
 originName(null)
 lolSummonerName(null)
 Other(null)
 comment(null)
 seat_id(null)
 msg_notifications(null)
 mouseHand(null)
 deviceId(null)
 alternative_login(null)
 1(array)
 War(array)
 id28189
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10277
 teamB10265
 scoreAByA2
 scoreBByA0
 scoreAByB2
 scoreBByB0
 finalScoreA2
 finalScoreB0
 winnerWarId28193
 loserWarId28203
 pouleId(null)
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 14:27:23
 Compo(array)
 id367
 nameGRAND - CS:GO
 steamGameId(null)
 nrPlayersTeam5
 maxTeams64
 compoTypeId0
 nrPoules3
 nrWinnersPoule4
 compoStateId5
 eventId46
 roundDE2
 addSecondaryFinal(false)
 adminId8749
 adminId2(null)
 bannerUrl(null)
 description<h1>password to the servers: war</h1> 
 tagId31
 allowDrawInPoule1
 nrLosersToBrackets0
 pauzed0
 rulebookFrag-o-Matic 24.0 Rulebook Counter-Strike:Global Offensive (CS:GO) Introduction This is the official rulebook for the Frag-o-Matic 24.1 CS:GO competition, that will take place from the 1st until the 3rd of September 2023. These rules apply to the players throughout all stages of CS:GO competition. Failure to adhere to these rules may be penalized as outlined. It should be noted that the tournament administrators have the final word, and have the power to decide on any circumstances that are not outlined by this document, and in extreme cases may overrule the rulebook in order to preserve fair play and sportsmanship. Frag-o-Matic reserves the right to change these rules at any time. The CS:GO admin team wishes you good luck in the tournament and hopes that you have an enjoyable competition. We’ll do our utmost best to make it fair, fun and exciting for everyone involved. <a name="navigation"></a>Table of contents <ol> <li><a href="#admin">Admins and communication</a></li> <li><a href="#compo">Compo overview</a> <ol> <li><a href="#participants">Participants</a></li> <li><a href="#teamsheets">Team sheets</a></li> <li><a href="#teamnames">Team names</a></li> <li><a href="#teammanager">Team manager / coach</a></li> <li><a href="#teamcaptain">Team captain</a></li> <li><a href="#players">Players</a> <ol> <li><a href="#grstandard">Grooming standards</a></li> </ol> </li> <li><a href="#cheating">Cheating</a> <ol> <li><a href="#forbiditems">Forbidden items</a></li> </ol> </li> <li><a href="#match">Match protests and forfeit</a> <ol> <li><a href="#definitions">Definition</a></li> <li><a href="#matchprotest">Match protest rules</a></li> <li><a href="#forfeitrules">Forfeit rules</a></li> </ol> </li> <li><a href="#seeding">Seeding</a></li> </ol> </li> <li><a href="#general">General</a> <ol> <li><a href="#generalrules">General rules</a></li> <li><a href="#sanctions">Sanctions and disputes</a></li> <li><a href="#confidentiality">Confidentiality</a></li> <li><a href="#coc">Code of conduct</a></li> <li><a href="#drugsalcohol">Drugs and alcohol</a></li> <li><a href="#betting">Betting</a></li> <li><a href="#addagreement">Additional agreements</a></li> <li><a href="#streaming">Streaming, interviews and media</a> <ol> <li><a href="#broadcasting">Broadcasting</a></li> <li><a href="#matchmedia">Match media</a></li> <li><a href="#screenshots">Screenshots</a></li> </ol> </li> <li><a href="#playerchanges">Player changes</a></li> <li><a href="#prizemoney">Prize money</a></li> </ol> </li> <li><a href="#csgorules">Counter-Strike:Global Offensive rules</a> <ol> <li><a href="#tournament">Tournament structure and time schedule</a> <ol> <li><a href="#penalties">Penalties and forfeits during the time schedule</a></li> <li><a href="#compomaxteams">Compo sign-up and max teams</a></li> <li><a href="#structure">Structure</a></li> <li><a href="#gamesetup">Game setup</a></li> <li><a href="#vetosystem">Veto system</a></li> <li><a href="#compospecificrules">Compo specific rules</a></li> <li><a href="#usageofpause">Usage of pause</a></li> <li><a href="#demofiles">Demo files</a></li> </ol> </li> <li><a href="#matchprocedure">Match procedure</a> <ol> <li><a href="#maplist">Map list</a></li> <li><a href="#matchrules">Match rules</a></li> <li><a href="#clientrules">Client rules</a></li> <li><a href="#illegalscripts">Illegal scripts</a></li> <li><a href="#customfiles">Custom files</a></li> <li><a href="#colordepth">Color depth and external programs</a></li> <li><a href="#illegalprograms">Illegal programs</a></li> <li><a href="#ingameoverlay">In-game overlays</a></li> <li><a href="#techprobs">Technical problems and disconnects</a></li> </ol> </li> <li><a href="#csgoserver">CS:GO server</a> <ol> <li><a href="#serversettings">Server settings</a></li> <li><a href="#servercrash">Server crash</a></li> <li><a href="#serverlag">Server (var) lag</a></li> <li><a href="#serverplugins">Server plugins</a></li> <li><a href="#rconusage">RCON usage</a></li> <li><a href="#warmupservers">Warmup servers</a></li> </ol> </li> </ol> </li> <li><a href="#copyright">Copyright Notice</a></li> </ol> <a name="admin"></a>1. Admins and communication <hr /> Communication before the LAN: <ul> <li>General contact > <a href="mailto:csgo@fom.be">csgo@fom.be</a></li> </ul> Please email us any feedback before and after the LAN event. CS:GO admin team: <ul> <li>Dragon <ul> <li>Steam: https://steamcommunity.com/profiles/76561198244170010/</li> <li>Discord: dragon (main communication line)</li> </ul> </li> </ul> Communication during the LAN: The communication during the LAN will be through Steam, Discord or at the Compo Desk. We will be available as much as possible in the <a href="https://discord.gg/URX6v82Wmp" target="_blank">#csgo channel</a>. We will use this as a second channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #csgo channel. Discord will be our main communication channel. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compo"></a>2. Compo overview <hr /> <a name="participants"></a> 2.1 Participants Due to lack of time, we have a tight schedule. Therefore we can make the decision to force teams to only participate in 1 grand compo! We will contact the teams who are signed in for 2 grand compo’s at the moment and they will need to make a choice. When a team refuses, we will remove them from the competition to make room for other teams. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamsheets"></a> 2.2 Team sheets As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops. A rule violation by any player in a team may lead the tournament admins to sanction the entire team, even if the rest of the team was not aware of the violation. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamnames"></a> 2.3 Team names <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teammanager"></a> 2.4 Team manager / coach The team manager does not have any responsibilities. The team manager is eligible to play for his team in matches, providing he’s indicated as a “Player” on the team in the team sheet. The communication with the team will not go via the team manager, all communication will go via the team captain! Spectators are not allowed on our servers. Only tournament admins may be in spectator mode during a match. The only exception is: coaches are allowed to spectate a match using the coach's command, only if the tournament admin is notified, and thus to spectate their team only. They are obligated to use the “coach t” or “coach ct” command before the match start and aren’t allowed to join after a match has been started. If noticed that the coach is abusing this rule, the team will get punished for it (e.g. round loss, side loss or match loss). During a match, the coach may only communicate with the players during freeze-time, warm up, half-time, or during one of the 4 timeouts. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamcaptain"></a> 2.5 Team captain We consider the one who registered the team into the compo on the Frag-o-Matic website as captain! The clan leader or team captain is responsible for his team and all the players in that team. It is recommended that the team captain is fluent in English or Dutch, as he will be required to communicate with the tournament admins. The team captain must read and understand the rulebook. The team captain is responsible for ensuring his team and players adhere to the rules. Ignorance of the rules is not an excuse for rule violations. The team captain may choose at any time to nominate another player in or manager of his team as team captain for any reason. Such nominations must be reported by the team captain, either in person or in writing, to the admins before the game starts. All official communication between a competing team and the tournament admins must be conducted by the team captain. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="players"></a> 2.6 Players All players must read and understand the CSGO rulebook. Any player in violation of a rule, will be sanctioned as described in this rulebook. Each team must have five players on the match server at the match start time as indicated by the schedule, unless permission has been granted by the tournament admins to play with less than five players. Only players registered for a team in the tournament may play for that team unless otherwise discussed with the tournament admin. All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins. Players registered for a team in the tournament may not play for any other team in the same tournament. Each player has to use their nickname that is similar to the nickname he/she has entered on their fom.be account. All players for a team must be clearly identifiable in-game with a uniform tag for that team and a separate, noticeably different nickname for each player. Players may not significantly change their nickname during the tournament. Any nickname they use during the tournament must always obviously visibly correspond to their original nickname. You are not allowed to change your nickname in-game. If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning. 3 warnings are equal to a forfeit in 1 match. Player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate. Make sure your steam account is linked with your fom.be account corresponding to your nickname. Players are strictly prohibited from using any other person’s steam account for any reason whatsoever during the CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="grstandard"></a> 2.6.1 Grooming standards People participating in the CS:GO tournament are expected to normal grooming standards. You may be asked to take action if you or your clothing have a look or odor that’s offensive to other players. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="cheating"></a> 2.7 Cheating During Frag-o-Matic we won’t investigate cheaters from an external event. When we discover someone cheating during our LAN, that player and his team will be banned from the compo and the player will be also banned for the next Frag-o-Matic edition. Furthermore we will investigate reports of players cheating during other tournaments until 2 weeks before the LAN. When a player is discovered cheating during another tournament/platform 12 months before the event occurs, then that player will not be allowed to play on that edition of Frag-o-Matic within the CS:GO competition and the edition after that. If one of the following rules apply, then that player will not be allowed to compete in our tournament: Caught cheating within a tournament/platform 12 months before the start date of our event. There needs to be enough evidence for that player, that he/she was cheating and the tournament admins will judge if the evidence is valid OR if he/she was caught cheating on the following platforms: <ul> <li><a href="ts3server://ts.fom.lan">ts.fom.lan</a> - CS:GO admin channel</li> <li>Discord: <a href="https://discord.gg/MbPY2ge">https://discord.gg/MbPY2ge</a> <ul> <li>Teams are only allowed to use a uniform team name for their team.</li> <li>Teams may not change their team name during the tournament.</li> <li>Teams may not change their team in-game tag during the tournament, unless none was set.</li> <li>Duplicating team names of other teams is not allowed.</li> <li>Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.</li> <li>Team names are not allowed to be offensive.</li> <li>Please make sure your team name is filled in on your fom.be profile.</li> </ul> <ul> <li>Faceit</li> <li>Esl</li> <li>Valve (vac ban for any Counter strike: Global Offensive game)</li> <li>ESEA</li> <li>Cevo</li> </ul> </li> <li>When a player is caught selling or buying cheats. In any case the admin will have the final decision. This means that the admin will review the evidence and make the final call. If a player shows the intention of coming to our tournament to cheat and we’re provided evidence of this. Everyone from the community may send evidence to csgo@fom.be, when they suspect someone participating at Frag-o-Matic of cheating. All forms of cheating in matches are forbidden, and will result in an overall forfeit in the tournament. Possibilities for cheating in Counter-Strike:Global Offensive are, for example; all kinds of multi-hacks, wallhack, aimbot, colored models, no-recoil, no-smoke, no-flash and sound changes. All hardware or software that has an influence on the game in such a way that the essence of the game is affected are banned from this tournament. Any use of this kind of hardware will result in a disqualification of the tournament as it will be recognized as cheating. When proven that a player is not cooperating in his own ban research or is lying on purpose. He will get banned for 1 edition. You can find our banlist at http://www.fom.be/contents/view/cs-go-banlist The mentioned people in our ban list are not allowed in the CS:GO tournaments at Frag-O-Matic until the edition that’s stated there. When these people compete under a false name nonetheless or try to circumvent the rules then they will receive an extended or permanent ban. Here are some of the other examples of ways to gain advantages, this list may not be the full list but if players are unsure of certain things, they should seek to ask the tournament admins first: Flash Bang, Smoke Grenade, and Hand Grenade Bugs - it is illegal to use any flash bang, smoke grenade, or hand grenade bugs, regardless of intent. Silent Bomb Plants - ALL bomb plants must be done in a position where your opponents can hear you. There should be no rotation in players to gain money advantages throughout a match. The bomb must be planted on solid surfaces on the map, ie where an opponent can defuse from, so not up in the air or floating. Illegal Bomb Defuses - No player can defuse a bomb through any other solid object on the map, it has to be done in clear view. It is also forbidden to try to intentionally distort your hitboxes during a defuse situation to prevent an opponent from killing you in game. Walking/Boosting through walls - No player should walk, boost through walls or roofs. To do so will see your team penalized for that round. Map Exploits - Boosts that include the use of clipping are strictly forbidden. The term “Clipping” defines that when a player is boosted can see through certain parts of the map (ie over/under walls, or through solid objects on the map). If any player or team feels unsure on a new advantage they have found through their practice sessions, they are welcome to show this specific spot to the tournament team to review. Any player or team that does this will be treated to the strictest confidence as not to jeopardize your strategic advantage, however we can rule on whether it is a legal move. We strongly advise teams to give us plenty of time ahead of an event so we can review it in good time and make good judgement on it. The game admins may inspect your machine at any time throughout the event to inspect for cheats or hacks within your game files, steam cloud and anywhere on your PC or memory sticks. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="forbiditems"></a>2.7.1 Forbidden items During the lan, to prevent cheating by using external devices or items, the following items are forbidden: <ul> <li>Smartwatches; Having or carrying a smartwatch during the event, when competing in the CS:GO competition, that player will immediately be disqualified from the competition.</li> <li>Alienware Wireless Headset AW988; Visual representation of audio isn’t allowed.</li> <li>AR (augmented reality) glasses</li> <li>Hardware from the brand “Bloody” (these are mice that come with software that reduces recoil on weapons)</li> </ul> Any other electronic devices (like smartphones) that are used during a match will be considered suspicious and we’ll ask that they’re not used. If, during a match, the suspicious device is still in use; the team of the player using the device will receive a warning. After 3 warnings the team will receive a disqualification from the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="match"></a>2.8 Match protests and forfeit <a name="definitions"></a> 2.8.1 Definition A protest is a raised issue for problems that affect the match outcome; a protest may even be filed during a match for things like incorrect server settings and other related issues. A protest is the official communication between a team captain and a tournament admin. A forfeit is a lose or surrender. <a name="matchprotest"></a> 2.8.2 Match protest rules Participants are only allowed to issue a match protest before the beginning of their next match. The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “they are cheaters” will not be enough. Insults and flaming are strictly prohibited in a protest, and may result in the protest being ruled against the insulting party. <a name="forfeitrules"></a> 2.8.3 Forfeit rules A forfeit can be called for a single match or the entire competition from a competing team for their team. Only the team captain can raise a forfeit for their team. A forfeit can also be raised by an admin as a penalty for wrongdoing. For example, in most cases where a competing team doesn’t follow the time schedule. The tournament admins can always force a forfeit. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="seeding"></a>2.9 Seeding Seeding is done through an objective outlook towards data provided by all participants for every event. Every participant is required to provide us their main steam account, ESEA and/or CEVO profile, FACEit level and previous wins/achievements. The supplied data is only kept and used for one event to calculate an individual “score” based on reached rank, played time, csgo hours and historical performance/achievements from Frag-o-Matic or other tournaments. The team sum of 5 individual scores will show an objective score where the higher the score, the higher the team seeding. The tournament admins won’t seed teams higher based on any subjective opinions. If no statistical data was provided for all 5 team member, than that team will be seeded beyond top 16. <a name="general"></a>3. General <hr /> <a name="generalrules"></a> 3.1 General rules Frag-o-Matic Counter strike:Global Offensive (CS:GO) 5v5 tournament is a local area network (LAN) tournament. By competing in this tournament, teams and players accept these rules in full. Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation. In the beginning of the LAN the team captains can sit together with the admin to discuss the rules and to make adjustments if needed. The decisions are made by the admin. If you have any issues with the rules, you can explain this by sending an email to <a href="mailto:csgo@fom.be">csgo@fom.be</a> up to one week before the start of the event. Clarification of any point in the rules is available from the tournament admins at any time during the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="sanctions"></a>3.2 Sanctions and disputes Sanctions and disputes will be resolved by the main tournament admin. The admin’s decision on any sanction or dispute is final. Abusive behavior towards the Frag-o-Matic staff, tournament admins or opponents at any time during the tournament is unacceptable and will be punished with warnings. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="confidentiality"></a>3.3 Confidentiality The content of protests, support communication, discussions or any other correspondence with tournament officials and administrators are considered as strictly confidential. The publication of such material is prohibited. If the contents has been shared without consent then this could lead to a team’s disqualification. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="coc"></a>3.4 Code of conduct Any form of aggression<a href="#coc_aggression">*</a> (both verbally and physically) will not be tolerated. Any and all physical aggression will be sanctioned with an immediate disqualification by that person or team performing the physical act (both actioned and reactioned). Any verbal aggression will be sanctioned by a time-out for that person or team. A time-out is either set in time (hours/day) or in amount of matches when a player or team is not allowed to participate in the CS:GO competition. Any situation that is about to escalate should be dealt with in a calm and diplomatic manner. An audience with any Frag-o-Matic crew member (CS:GO admin or Frag-o-Matic team leaders) can always be called for at any time during the event. Keep in mind that this audience can not be used to waste time or get a time advantage. At any point, the CS:GO tournament admins can decide to continue with the competition with or without consent from either players or other Frag-o-Matic staff. In the event when a single player or more are accused of cheating, the event will continue nonetheless. Evidence will be presented to the tournament admins and a call will be made at a later stage of the event. This rule is set to not cause any delays and have the situation under control. Any player(s) or team(s) ignoring this rule will receive a forfeit. Any player or team ignoring a CS:GO admin will be sanctioned with a warning. 3 warnings are equal to a forfeit of 1 match. <a name="coc_aggression"></a>*A form of aggression is described as: <ul> <li>Instrumental aggression -- Aggression aimed at obtaining an object, privilege or space with no deliberate intent to harm another person. Typical of participants wanting to get ahead of the competition with lies, anger, bullying, criticizing other people behind their backs, leaving others out of a group or otherwise ostracizing them, turning people against each other, dismissing the opinions of others (passive aggression).</li> <li>Hostile aggression -- Aggression intended to harm another person, such as hitting/kicking/biting someone (active aggression). Threatening to beat up someone (nonverbal intimidation). Sending threatening messages through emails, phone calls, or social media, or making threats against someone's life, shouting, and swearing (verbal hostility). Breaking someone's computer, destroying someone's cell phone, or other forms of vandalism (destruction of property).</li> <li>Relational aggression -- A form of hostile aggression that does damage to another's peer relationships, as in social exclusion, gossiping or rumor spreading. Examples: Arguments within a team after a lose that lead to a verbal fight.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="drugsalcohol"></a>3.5 Drugs and alcohol To play a match under the influence of any drugs or performance enhancers is strictly prohibited, and may be punished with exclusion from the tournament. If an admin finds that a player is not capable of competing in the competition because of intoxication, the admin can exclude that person from the entire tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="betting"></a>3.6 Betting Betting on any match in the CS:GO tournament is strictly forbidden. <a name="addagreement"></a>3.7 Additional agreements Teams may be required to play any match on the stage. If so, teams will be notified at least 20 minutes prior to the start time of that match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="streaming"></a>3.8 Streaming, interviews and media <a name="broadcasting"></a>3.8.1 Broadcasting Frag-o-Matic reserves the right to broadcast any match or demo, teams may not refuse such broadcasts. All forms of client side game broadcasting are NOT allowed. Frag-o-Matic participants are not allowed to watch a local GOTV if a CS:GO server broadcasts a game. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchmedia"></a>3.8.2 Match media All match media (screenshots, demos, etc.) must be kept until the end of the event. Faking or manipulating match media is forbidden and will result in exclusion from the tournament. Match media should be named clearly based on what it is. It is not possible to file a protest to complain about bad match media naming. However if a tournament admin is hindered in their work because of bad match media naming, then a tournament admin will give a warning. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="screenshots"></a>3.8.3 Screenshots The admin can ask for screenshots of every game on any moment during the event. When he does this, the team leader has 15 minutes time to deliver the screenshot to the admin. A screenshot of the scoreboard at the end of each half must be taken. When this is not done by a team it can result in a lost match when one of the other teams complains about a score. An RCON status screenshot must be taken: <ul> <li>at the beginning of the match</li> <li>in case of a server/player change</li> <li>if a player reconnects</li> </ul> RCON status screenshots made with the help of programs like HLSW etc. are not sufficient. In order to take an RCON status you have to use the console command “rcon status” (don’t forget to enter your RCON password) and take a screenshot of that. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="playerchanges"></a>3.9 Player changes Teams are permitted to substitute players (only with another player not active in the CS:GO competition) during pauses and between rounds, if they have permission from the tournament admin. Consent for substitutions must be obtained from the tournament admins, and substitute players must be registered for that team in the tournament. You can make this clear to the admin by using the contact information in section ‘Admins and communication’. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="prizemoney"></a>3.10 Prize money When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="csgorules"></a> 4. Counter-Strike:Global Offensive rules <hr /> <a name="tournament"></a>4.1 Tournament structure and time schedule Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. On Saturday and Sunday, teams must be present at 10:00 (AM) and ready to start playing the rest of their scheduled matches. It can be the case that the tournament admins decide to start earlier or end later, but this will be communicated (to all team captains). An exact time schedule will be provided on our fom.be website for all teams to follow. Each match will have a start time on which the game needs to be started. The team(s) that are responsible where the start time has not been met will receive a forfeit for that match. Whether or not this rule will be applied, is the decision of a tournament admin. The schedule for the tournament may be subject to change at any time. Matches may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice. Games will not be rescheduled to an earlier time in the same day if either of the teams have not yet played a game on that day without the consent of both team captains. Where possible the tournament admins will notify any teams involved in a rescheduled game of the new match start time at least one hour before the new start time. In the event a match is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible. If there’s insufficient time to complete a match, the tournament admins may at any time declare one team as the winner, if that team holds a clear advantage in that match. It is the responsibility of the tournament admins to decide whether a team holds a clear advantage. This rule will only be used in the emergency when the remaining event time is a factor. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="penalties"></a>4.1.1 Penalties and forfeits during the time schedule If 1 or more teams are still playing a match in a previous stage or if 1 team is late and doesn’t start playing their match in the stage where they are; Teams are offered 30 minutes of grace time in both circumstances, after 30 minutes warnings are handed out: After 30 minutes that team, who’s still not playing their scheduled match, will receive a 1st warning from a tournament admin. A notice via our csgo channel on discord and if the team is present and found at their seat they’ll be warned in person as well. A second warning is given in the same manner 5 minutes after the first warning. A third and final warming is given in the same way 5 minutes after that. 5 minutes after the final warning the team who received 3 warnings will receive 1 game loss for their match in the next round. In case of a bo3 in the next round, a bo2 will be played with one win to the team that was on time. If after 15 minutes the team with 3 warnings and one loss in the next round is still not playing, they’ll receive a forfeit from an admin. In case of a bo1 (in the lower bracket for example) we won’t lose any more time and a forfeit will be forced. The forfeit is applied on our fom.be website and a notice is given on Discord in our csgo channel. The tournament admins will keep a record of the warnings and will communicate this to the compo desk. As mentioned in our general rulebook; Non-acceptable excuses for a delay: “We want to eat” isn’t a valid excuses for starting an argument at the compo desk. As a note, we ask that teams only take a maximum of 15 minute breaks in between games and matches to avoid any penalties. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compomaxteams"></a>4.1.2 Compo sign-up and max teams All compo sign-ups are done via our fom.be website. Some rules are already explained in our general rulebook. Any team that is not “full”, meaning the team doesn’t consist of minimum 5 players, will be removed from the compo sign-up one hour before the start of the competition. We allow a maximum 64 teams to register to our CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="structure"></a>4.1.3 Structure Our CS:GO tournament will use a poule system and 3 double elimination brackets (pro, semi-pro and fun). Each poule will consist out of 3-4 teams who will compete against each other to make it into the brackets. Each team within the poule needs to play against any other team within its poule. Following the poule stage, the 2 winners from each poule will advance to a pro bracket, the last 2 teams from each poule will advance to a semi-pro bracket and <s>other teams will proceed to the fun bracket</s>. Our compo structure will use the following setup for pro, semi-pro and fun: <ul> <li>Groupstage > BO1 (best of 1)</li> <li>Upper Bracket > BO3 (best of 3)</li> <li>Lower Bracket > BO1 (best of 1)</li> <li>Pro & semi-pro bracket: <ul> <li>Semi-final (Finals in lower bracket) > BO3 (best of 3)</li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> </li> <li><s>Fun bracket:</s> <ul> <li><s>Semi-final (Finals in lower bracket) > BO1 (best of 1)</s></li> </ul> </li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> When 2 teams have the same amount of points after the poules we will look at the following criteria in order: <ul> <li>The match between the 2 teams</li> <li>The won rounds total</li> <li>The lost rounds total</li> <li>Seeding</li> </ul> We can also look at other criteria if we feel that it's necessary (also cooperation). The admin is allowed to overrule these criteria. If there’s not enough data to validate a criteria the admin can chose to ignore it. A tournament admin can decide to change some matches from BO3 to BO1 or visa versa when needed. (For example: no time to play a BO3). <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="gamesetup"></a>4.1.4 Game setup Matches will be played 5on5. Playing with fewer than five players in any match is only allowed with permission from the tournament admins. Before a match starts, both teams must state that they are ready to start the match. The must do this by having one team member typing ‘ready’ in server chat. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated. Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug. You’ll need to use the following match setup to play every game: <ul> <li>2 teams join the server that is assigned to them on our fom website.</li> <li>The team captains can use the RCON password “godmode” to follow the next steps : <ul> <li>Don’t forget to do ‘cl_mute_enemy_team 0’</li> <li>Change the map to de_mirage (rcon changelevel de_mirage)</li> <li>Load the Frag-o-Matic config (rcon exec fom5on5.cfg)</li> <li>Start a knife round on de_mirage (optional). The winner of this knife round can decide who team A is. Start the map veto process (Veto is explained under ‘Veto system’’).</li> <li>After the Veto the team captain needs to change the map to the first map of Team A (in a BO3) or the single map that was chosen (in a BO1) (rcon changelevel ‘mapname’)</li> <li>Load the fom5on5.cfg again on this map. (rcon exec fom5on5.cfg)</li> <li>After this the teams do another knife round to decide which team will start on which side of the map. The winner of the knife round decides which side they want to start on and that team will also start the match. (rcon mp_restartgame 1)</li> </ul> </li> </ul> If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server can be paused at the end of the current round (see rule ‘Usage of pause’ function) by one of the teams. The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed. If a player/substitute doesn’t connect within that time, then the match is continued 4on5, or 4on4 if the opposing team agrees and the tournament admins are informed. There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="vetosystem"></a>4.1.5 Veto system Our veto process is the next step after playing a knife round, as described in ‘Game setup’. The map(s) chosen to be played in each BO1 and BO3 are done via elimination (i.e. veto). Where ‘team 1 = A’ and ‘team 2 = B’, with A being decided by the winner of the knife round. Teams can also decide who team A/B is without playing a knife round. The maps you don’t want to play as a team, should be the maps that you veto during this process. The veto process needs to be done in server chat. VETO rules best-of-1: ABABAB veto. The map pool exists out of 7 maps. 6 maps are vetoed during this process, 3 maps for each team. The remaining map is the map played in the best-of-1 match. VETO rules best-of-2: ABAB veto AB play. The map pool exists out of 7 maps. 4 maps are vetoed during this process, 2 maps for each team. Out of the 3 remaining maps, 1 team each gets to decide a map to play on. VETO rules best-of-3: A/B veto, A/B play and A/B veto. The map pool exists out of 7 maps. 4 maps are eliminated, and 3 maps are selected to play. Each team needs to veto a map, followed by each team choosing a map and again each team vetoing a map. The remaining map is the third map that needs to be played if both teams win a map. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compospecificrules"></a>4.1.6 Compo specific rules All matches in the group stage are played MR15. All matches in the brackets are played MR15 (meaning, 16 rounds won = game win). In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games are best of three (BO3) in the bracket, 3 maps are decided by veto. The grand final is a best of three (BO3) with map advantage! When in the brackets a game is tied an overtime needs to be played. The overtime will be played MR3 with 10.000$ start money. For the start of the overtime teams will stay on the side which they played the previous half on, during halftime sites will be swapped. Teams will continue to play overtimes until a winner has been found. We have our own special breed of bracket seeding. For more information please contact us in advance. This bracket seeding is law. Obey it. All CS:GO players can only use our ts.fom.lan (local) teamspeak for voice communication. Teams are only allowed to have 5 players + 1 coach in their teamspeak channel whilst in a competition match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="usageofpause"></a>4.1.7 Usage of pause Pauses may be taken for any reason. Teams are permitted 3 pauses per side in each match. Each pause having a maximum duration of 5 minutes, unless authorised by an admin to take a longer pause (in case of technical difficulties, for example). After a “pause”-event, an “unpause“-command needs to be done. Teams can’t unpause without the consent of the other team. Pauses may only be activated at the start of the next round during freeze time. So make sure you tell the other team before round end (in all-chat), that your team will take a pause in the next freeze time. Usage: Type the following commands in console, to activate and deactivate the pause event. Pause = rcon mp_pause_match Unpause = rcon mp_unpause_match Illegal usage: DON’T USE = sv_pause If a team does use sv_pause, they have to surrender 1 round. (by all team members typing “kill” in console) <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="demofiles"></a>4.1.8 Demo files GoTV demos must be active for each match to be recorded. It’s the responsibility of (both) team captains to ensure that GoTV is recording. If this isn’t the case, the tournament admins will be forced to make calls without a recording when a dispute occurs. It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A knife round is part of a match and should be recorded. At least one of the players must be able to upload the knife round on admin request. Protests regarding missing knife rounds are not valid. In general, defective or manipulated demos will be treated as missing demos. If the demo is incomplete, as decided by the admin, it also will be treated as missing demo. If a protest is opened for a match, all match media need to be kept until the end of the event. Demos can only be requested up to a maximum of 30 minutes after a match via the admin. A demo request must state which teams were playing, the name(s) of the map(s) the match(es) was/were played on, the time of the match(es) and the server IP address(es). If a player or a team illegally aborts the match, they lose their right to demand demos. Recording demos is recommended. Our servers will likely record demos for every match but these are only used when there is doubt about a decision the admin has to make. It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.2 Match procedure <a name="maplist"></a>4.2.1 Map list Only the following maps are allowed to be played on during the competition: <ul> <li>de_ancient</li> <li>de_anubis</li> <li>de_inferno</li> <li>de_mirage</li> <li>de_nuke</li> <li>de_overpass</li> <li>de_vertigo</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchrules"></a>4.2.2 Match rules <ul> <li>Diffusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.</li> <li>Throwing grenades/flash bangs/smokes across walls in maps is allowed.</li> <li>Boosting is not considered a bug.</li> <li>Buying and using multiple grenades is allowed but with a max of 2 flash bangs.</li> <li>Multiple grenades are allowed but max 2 flash bangs</li> <li>Bugs on the map must be checked before the match begins. Any protest after the match about map bugs will be ignored.</li> <li>If a player loses connection before the first kill, the match can be restarted. If this happens after the first kill, the server can be paused and have the disconnected player reconnect. Matches won’t be restarted due to disconnections.</li> <li>If you want a player change (sub) during the match, inform the opponent and the compo admins before the match begins!</li> <li>To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.</li> <li>Climbing with help of teammates is allowed in general.</li> <li>Throwing grenades inside walls is not allowed.</li> <li>Self-kills are strictly forbidden, unless an admin forces you to do this as a sanction for disobeying any rules.</li> <li>Bomb planting in a way it can’t be reached is forbidden.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="clientrules"></a>4.2.3 Client rules The admin is allowed to take over your computer before, during and after a game and have a look. Without the pc’s owner in question nearby, the person in question can appoint someone to stay with the admin to make sure no privacy issues are violated. Any trace evidence of cheats found on a player’s computer – even if such discovery took place outside of a game – can lead to exclusion from any competition. For NVIDIA graphics card users: The use of Ambient Occlusion is strictly forbidden. If you are caught using this setting, this will result in a direct loss of the match. Getting caught for a 2nd time will result in removal from the tournament. This setting can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings. The following commands are forbidden: <ul> <li>mat_hdr_enabled</li> </ul> The following startparameters are forbidden: <ul> <li>+mat_hdr_enabled 0/1</li> <li>+mat_hdr_leven 0/1/2</li> </ul> In your game client cfg-folder you’re only allowed to have config files. Pictures, demos, screenshots and zipped files are forbidden. All other configuration changes are allowed as long as they do not give an unfair edge or advantage comparable to cheating. The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary. Boosting through walls/ceilings/ground, sky walking, map swimming, floating and sharking are all forbidden. To throw grenades inside walls is not allowed. Above walls and roofs is allowed. To plant the bomb in a way that it cannot be reached is forbidden. Places that can be reached with help of a team mate are allowed as long as they are visible. Violating this rule will result in tournament administrators intervention. Changing graphic settings to irregular values can be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalscripts"></a>4.2.4 Illegal scripts In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts: <ul> <li>Stop Shoot scripts [Use or Awp scripts]</li> <li>Center view scripts</li> <li>Turn scripts [180° or similar]</li> <li>No Recoil scripts</li> <li>Burst fire scripts</li> <li>Rate changers (Lag scripts)</li> <li>FPS scripts</li> <li>Anti flash scripts or binding (snd_* bindings)</li> <li>Bunnyhop scripts</li> <li>Stop sound scripts</li> <li>Following Commands/CVars are forbidden</li> <li>+weapon_recoil_model 0 (Startparameter)</li> </ul> The following CVAR values must be used: <ul> <li>cl_bobcycle 0.98 (First Time->Warning)</li> </ul> If there are more than one player who used a wrong client setting, the match will be deleted. Exception: cl_bobcycle Using illegal scripts will be penalized if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized. The use of No-Flash and No-Recoil bindings/scripts in any and all forms will be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="customfiles"></a>4.2.5 Custom files The HUD can be changed as long as no information are deleted or falsified which are available in the standard HUD. If the HUD is changed it has to be readable. If an admin is hindered in his work due to an unreadable HUD, penalty points may be assigned. Protests or supports which adhere to this rule will not be admitted and are rejected directly. Apart from the HUD and the GUI no custom files are allowed. This also includes custom models, changed textures or sounds (volume, soundscapes) are forbidden. <a name="colordepth"></a>4.2.6 Color depth and external programs The usage of a color depth of 16bit is not allowed. The usage of external programs (ex. SweetFX, A3D,...) are not allowed to enhance vision. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalprograms"></a>4.2.7 Illegal programs Changing the game graphics or textures with the help of video card drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. NVidia SLI Display, Riva tuner Overlays) is illegal. Failure to comply with this rule will result in a punishment for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized. If you play with ambient occlusion, it will be punished as cheating!! Punishment will be given regardless of whether the script/binding is executed via external hardware or software. Also binding any snd_ command is forbidden. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="ingameoverlay"></a>4.2.8 In-game overlays All In-Game overlays – provided by the game itself – except the following are forbidden: <ul> <li>net_graph 0</li> <li>net_graph 1</li> <li>cl_showpos 1</li> <li>cl_showfps 1</li> <li>cl_showdemooverlay 1 / -1</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="techprobs"></a>4.2.9 Technical problems and disconnects If a disconnection occurs the game should automatically reconnect. When this doesn’t work, a tournament admin will decide what to do. The tournament admin will make a call in every possible scenario regarding the severity of the problem and how to deal with it. But, the following guidelines are in place in the event of a disconnect: <ul> <li>In the case where Frag-o-Matic is responsible for the disconnect, the round needs to be restored to the start of the round where the disconnection happened. I.e. follow the steps as described under “4.3.2 Server crash”.</li> <li>When a player is responsible for his own disconnect, the team with 4 players can decide to continue to play 4v5 or use a pause as described in “4.1.6 Usage of pause”.</li> <li>The disconnected player can then reconnect to the match. If that player fails to reconnect, then the match will continue 4v5.</li> <li>If another Frag-o-Matic participant is responsible for causing a problem, then the match needs to be paused and a tournament admin needs to be notified to make a call on what to do.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.3 CS:GO server <a name="serversettings"></a>4.3.1 Server settings Frag-o-Matic will supply hardware for all servers. All games related to the tournament must be played on these servers. All matches will be played using the latest version of CS:GO and the official Frag-o-Matic CS:GO server config. All matches have to be played on an official Frag-o-Matic CS:GO tournament server and on the provided server number (as listed on our fom.be website, in the csgo compo section). We’ll use a standard (ESL) 5v5 pro league tournament config on a 128 tickrate server: <ul> <li>Startmoney: 0</li> <li>Maxrounds: 30</li> <li>Roundtime: 1m 55s (1.92)</li> <li>Freezetime: 12 seconds</li> <li>C4timer: 40 seconds</li> <li>Pause: 1x 5minutes per half each map.</li> <li>Overtime: MR3 - .000 startmoney</li> <li>Time during half time: 13 seconds</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="servercrash"></a>4.3.2 Server crash In the event of a server crash, after notifying a tournament admin and having them restart the the server, both teams have to re-join the same server and use the following command: <ul> <li>rcon mp_backup_restore_list_files</li> </ul> This will show you the backup files before the server crashed. 1 team captain then executes the correct file by using the following command: <ul> <li>rcon mp_backup_restore_load_file</li> </ul> Example: rcon mp_backup_restore_load_file backup_round12.txt All previous settings (score, money, armor, weapons,...) are then reset to the round before the server crashed and the match is set to paused. To continue the match, use the unpause command: <ul> <li>rcon mp_unpause_match</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="serverlag"></a>4.3.3 Server (var) lag Teams are given the time to play a warm-up match on their server before every compo match if they wish to do so. It’s not allowed to switch to another server once the compo match has been started. Test the server before the match starts. Any server problems should be reported to a tournament admin by going to the compo desk after sending an email with the information below. In the event that you experience any lag during or before a match, please note the time(s) and contact us via Discord or the Compo Desk. We'll escalate this information and, if possible, provide a solution for upcoming matches. The statement or report of (possible) lag in a match is a not valid argument in a protest. However, sending us the data above will give your team the time necessary to avoid any possible forfeits when you notify us at the compo desk after sending your email. Failure in providing us this data will not allow your team to deviate from our time schedule. We strive to provide all our servers lag free. We would like to thank you in helping us improve our servers. <a name="serverplugins"></a>4.3.4 Server plugins No extra plugins will be installed on our CS:GO servers. <a name="rconusage"></a>4.3.5 RCON usage RCON is only allowed as described in “4.1.2 Game setup”. Usage of RCON outside the game setup is penalised by receiving an instant forfeit for the team using any other RCON commands. We monitor all servers and RCON logs and will use this as evidence to hand out a match forfeit to the team using RCON outside of the game setup rules. <a name="rconusage"></a>4.3.6 Warmup servers Subject to availability, we will provide warmup servers. The settings will mirror our war servers as close as possible, but won’t be managed by the csgo team. Participants in our competition are allowed to use our warmup servers as such, to warm up, practice nade throws, practice aim,etc… We will not guarantee availability of those servers, since they will depend on the overall capacity. If warmup servers are available, they cannot ever be used for playing matches. If a match has been played on one of those servers though, the end-scores will still count. It is the responsibility of both teams the correct (assigned) server is joined. At any time, we can convert one of those servers to an official war server (In cases of need). It will at that point no longer show up as a warmup server. <a name="copyright"></a>5. Copyright Notice Copyright © 2005-2022 by E-EVENTS VZW All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher, addressed at <a href="mailto:csgo@fom.be">csgo@fom.be</a> </li> </ul>
 showsponsor(false)
 sponsorcontent
 showfiles(false)
 filescontent
 prizescontent<h1> First Place </h1> <ul> <li> <h3>525 €</h3> </li> </ul> <h1>Second Place</h1> <ul> <li> <h3>315 €</h3> </li> </ul> <h1>Third Place</h1> <ul> <li> <h3>210 €</h3> </li> </ul>
 precompo(false)
 donations0
 donationAmount0
 scheduleregistration closes at 21! please make sure all games are played on time! poules will be made and will be playable. saturday 10am we will start with the brackets semi final will be at 10am on sunday with afterwards the grand final Have fun and Good luck!
 faq
 sponsorUrl
 sponsorImg(null)
 sortTimeLabel0
 TeamA(array)
 id10277
 nameSchizophrenic
 leaderId9704
 compoId367
 pouleId1453
 notes
 withdrew(false)
 TeamB(array)
 id10265
 nameBASTARDS.AF9K
 leaderId5352
 compoId367
 pouleId1452
 notes
 withdrew(false)
 AdminEdit(array)
 id(null)
 facebook_id(null)
 username(null)
 new_username(null)
 nickname(null)
 password(null)
 firstname(null)
 lastname(null)
 active(null)
 validationCode(null)
 mailValidationCode(null)
 group_id(null)
 created(null)
 modified(null)
 last_login(null)
 street(null)
 nr(null)
 bus(null)
 zip(null)
 city(null)
 country(null)
 phone(null)
 gsm(null)
 gender(null)
 birthdate(null)
 clanId(null)
 clantrust(null)
 clanjoinId(null)
 hwbudget(null)
 education(null)
 profession(null)
 hoursaweek(null)
 language(null)
 oldId(null)
 receive_newsletter(null)
 imageUrl(null)
 slug(null)
 fb_link(null)
 fb_location(null)
 CPU(null)
 MOBO(null)
 GFX(null)
 RAM(null)
 steamName(null)
 steamId(null)
 originName(null)
 lolSummonerName(null)
 Other(null)
 comment(null)
 seat_id(null)
 msg_notifications(null)
 mouseHand(null)
 deviceId(null)
 alternative_login(null)
 2(array)
 War(array)
 id28203
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10509
 teamB10265
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA1
 finalScoreB0
 winnerWarId28205
 loserWarId(null)
 pouleId(null)
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 19:30:26
 Compo(array)
 id367
 nameGRAND - CS:GO
 steamGameId(null)
 nrPlayersTeam5
 maxTeams64
 compoTypeId0
 nrPoules3
 nrWinnersPoule4
 compoStateId5
 eventId46
 roundDE2
 addSecondaryFinal(false)
 adminId8749
 adminId2(null)
 bannerUrl(null)
 description<h1>password to the servers: war</h1> 
 tagId31
 allowDrawInPoule1
 nrLosersToBrackets0
 pauzed0
 rulebookFrag-o-Matic 24.0 Rulebook Counter-Strike:Global Offensive (CS:GO) Introduction This is the official rulebook for the Frag-o-Matic 24.1 CS:GO competition, that will take place from the 1st until the 3rd of September 2023. These rules apply to the players throughout all stages of CS:GO competition. Failure to adhere to these rules may be penalized as outlined. It should be noted that the tournament administrators have the final word, and have the power to decide on any circumstances that are not outlined by this document, and in extreme cases may overrule the rulebook in order to preserve fair play and sportsmanship. Frag-o-Matic reserves the right to change these rules at any time. The CS:GO admin team wishes you good luck in the tournament and hopes that you have an enjoyable competition. We’ll do our utmost best to make it fair, fun and exciting for everyone involved. <a name="navigation"></a>Table of contents <ol> <li><a href="#admin">Admins and communication</a></li> <li><a href="#compo">Compo overview</a> <ol> <li><a href="#participants">Participants</a></li> <li><a href="#teamsheets">Team sheets</a></li> <li><a href="#teamnames">Team names</a></li> <li><a href="#teammanager">Team manager / coach</a></li> <li><a href="#teamcaptain">Team captain</a></li> <li><a href="#players">Players</a> <ol> <li><a href="#grstandard">Grooming standards</a></li> </ol> </li> <li><a href="#cheating">Cheating</a> <ol> <li><a href="#forbiditems">Forbidden items</a></li> </ol> </li> <li><a href="#match">Match protests and forfeit</a> <ol> <li><a href="#definitions">Definition</a></li> <li><a href="#matchprotest">Match protest rules</a></li> <li><a href="#forfeitrules">Forfeit rules</a></li> </ol> </li> <li><a href="#seeding">Seeding</a></li> </ol> </li> <li><a href="#general">General</a> <ol> <li><a href="#generalrules">General rules</a></li> <li><a href="#sanctions">Sanctions and disputes</a></li> <li><a href="#confidentiality">Confidentiality</a></li> <li><a href="#coc">Code of conduct</a></li> <li><a href="#drugsalcohol">Drugs and alcohol</a></li> <li><a href="#betting">Betting</a></li> <li><a href="#addagreement">Additional agreements</a></li> <li><a href="#streaming">Streaming, interviews and media</a> <ol> <li><a href="#broadcasting">Broadcasting</a></li> <li><a href="#matchmedia">Match media</a></li> <li><a href="#screenshots">Screenshots</a></li> </ol> </li> <li><a href="#playerchanges">Player changes</a></li> <li><a href="#prizemoney">Prize money</a></li> </ol> </li> <li><a href="#csgorules">Counter-Strike:Global Offensive rules</a> <ol> <li><a href="#tournament">Tournament structure and time schedule</a> <ol> <li><a href="#penalties">Penalties and forfeits during the time schedule</a></li> <li><a href="#compomaxteams">Compo sign-up and max teams</a></li> <li><a href="#structure">Structure</a></li> <li><a href="#gamesetup">Game setup</a></li> <li><a href="#vetosystem">Veto system</a></li> <li><a href="#compospecificrules">Compo specific rules</a></li> <li><a href="#usageofpause">Usage of pause</a></li> <li><a href="#demofiles">Demo files</a></li> </ol> </li> <li><a href="#matchprocedure">Match procedure</a> <ol> <li><a href="#maplist">Map list</a></li> <li><a href="#matchrules">Match rules</a></li> <li><a href="#clientrules">Client rules</a></li> <li><a href="#illegalscripts">Illegal scripts</a></li> <li><a href="#customfiles">Custom files</a></li> <li><a href="#colordepth">Color depth and external programs</a></li> <li><a href="#illegalprograms">Illegal programs</a></li> <li><a href="#ingameoverlay">In-game overlays</a></li> <li><a href="#techprobs">Technical problems and disconnects</a></li> </ol> </li> <li><a href="#csgoserver">CS:GO server</a> <ol> <li><a href="#serversettings">Server settings</a></li> <li><a href="#servercrash">Server crash</a></li> <li><a href="#serverlag">Server (var) lag</a></li> <li><a href="#serverplugins">Server plugins</a></li> <li><a href="#rconusage">RCON usage</a></li> <li><a href="#warmupservers">Warmup servers</a></li> </ol> </li> </ol> </li> <li><a href="#copyright">Copyright Notice</a></li> </ol> <a name="admin"></a>1. Admins and communication <hr /> Communication before the LAN: <ul> <li>General contact > <a href="mailto:csgo@fom.be">csgo@fom.be</a></li> </ul> Please email us any feedback before and after the LAN event. CS:GO admin team: <ul> <li>Dragon <ul> <li>Steam: https://steamcommunity.com/profiles/76561198244170010/</li> <li>Discord: dragon (main communication line)</li> </ul> </li> </ul> Communication during the LAN: The communication during the LAN will be through Steam, Discord or at the Compo Desk. We will be available as much as possible in the <a href="https://discord.gg/URX6v82Wmp" target="_blank">#csgo channel</a>. We will use this as a second channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #csgo channel. Discord will be our main communication channel. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compo"></a>2. Compo overview <hr /> <a name="participants"></a> 2.1 Participants Due to lack of time, we have a tight schedule. Therefore we can make the decision to force teams to only participate in 1 grand compo! We will contact the teams who are signed in for 2 grand compo’s at the moment and they will need to make a choice. When a team refuses, we will remove them from the competition to make room for other teams. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamsheets"></a> 2.2 Team sheets As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops. A rule violation by any player in a team may lead the tournament admins to sanction the entire team, even if the rest of the team was not aware of the violation. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamnames"></a> 2.3 Team names <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teammanager"></a> 2.4 Team manager / coach The team manager does not have any responsibilities. The team manager is eligible to play for his team in matches, providing he’s indicated as a “Player” on the team in the team sheet. The communication with the team will not go via the team manager, all communication will go via the team captain! Spectators are not allowed on our servers. Only tournament admins may be in spectator mode during a match. The only exception is: coaches are allowed to spectate a match using the coach's command, only if the tournament admin is notified, and thus to spectate their team only. They are obligated to use the “coach t” or “coach ct” command before the match start and aren’t allowed to join after a match has been started. If noticed that the coach is abusing this rule, the team will get punished for it (e.g. round loss, side loss or match loss). During a match, the coach may only communicate with the players during freeze-time, warm up, half-time, or during one of the 4 timeouts. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamcaptain"></a> 2.5 Team captain We consider the one who registered the team into the compo on the Frag-o-Matic website as captain! The clan leader or team captain is responsible for his team and all the players in that team. It is recommended that the team captain is fluent in English or Dutch, as he will be required to communicate with the tournament admins. The team captain must read and understand the rulebook. The team captain is responsible for ensuring his team and players adhere to the rules. Ignorance of the rules is not an excuse for rule violations. The team captain may choose at any time to nominate another player in or manager of his team as team captain for any reason. Such nominations must be reported by the team captain, either in person or in writing, to the admins before the game starts. All official communication between a competing team and the tournament admins must be conducted by the team captain. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="players"></a> 2.6 Players All players must read and understand the CSGO rulebook. Any player in violation of a rule, will be sanctioned as described in this rulebook. Each team must have five players on the match server at the match start time as indicated by the schedule, unless permission has been granted by the tournament admins to play with less than five players. Only players registered for a team in the tournament may play for that team unless otherwise discussed with the tournament admin. All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins. Players registered for a team in the tournament may not play for any other team in the same tournament. Each player has to use their nickname that is similar to the nickname he/she has entered on their fom.be account. All players for a team must be clearly identifiable in-game with a uniform tag for that team and a separate, noticeably different nickname for each player. Players may not significantly change their nickname during the tournament. Any nickname they use during the tournament must always obviously visibly correspond to their original nickname. You are not allowed to change your nickname in-game. If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning. 3 warnings are equal to a forfeit in 1 match. Player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate. Make sure your steam account is linked with your fom.be account corresponding to your nickname. Players are strictly prohibited from using any other person’s steam account for any reason whatsoever during the CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="grstandard"></a> 2.6.1 Grooming standards People participating in the CS:GO tournament are expected to normal grooming standards. You may be asked to take action if you or your clothing have a look or odor that’s offensive to other players. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="cheating"></a> 2.7 Cheating During Frag-o-Matic we won’t investigate cheaters from an external event. When we discover someone cheating during our LAN, that player and his team will be banned from the compo and the player will be also banned for the next Frag-o-Matic edition. Furthermore we will investigate reports of players cheating during other tournaments until 2 weeks before the LAN. When a player is discovered cheating during another tournament/platform 12 months before the event occurs, then that player will not be allowed to play on that edition of Frag-o-Matic within the CS:GO competition and the edition after that. If one of the following rules apply, then that player will not be allowed to compete in our tournament: Caught cheating within a tournament/platform 12 months before the start date of our event. There needs to be enough evidence for that player, that he/she was cheating and the tournament admins will judge if the evidence is valid OR if he/she was caught cheating on the following platforms: <ul> <li><a href="ts3server://ts.fom.lan">ts.fom.lan</a> - CS:GO admin channel</li> <li>Discord: <a href="https://discord.gg/MbPY2ge">https://discord.gg/MbPY2ge</a> <ul> <li>Teams are only allowed to use a uniform team name for their team.</li> <li>Teams may not change their team name during the tournament.</li> <li>Teams may not change their team in-game tag during the tournament, unless none was set.</li> <li>Duplicating team names of other teams is not allowed.</li> <li>Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.</li> <li>Team names are not allowed to be offensive.</li> <li>Please make sure your team name is filled in on your fom.be profile.</li> </ul> <ul> <li>Faceit</li> <li>Esl</li> <li>Valve (vac ban for any Counter strike: Global Offensive game)</li> <li>ESEA</li> <li>Cevo</li> </ul> </li> <li>When a player is caught selling or buying cheats. In any case the admin will have the final decision. This means that the admin will review the evidence and make the final call. If a player shows the intention of coming to our tournament to cheat and we’re provided evidence of this. Everyone from the community may send evidence to csgo@fom.be, when they suspect someone participating at Frag-o-Matic of cheating. All forms of cheating in matches are forbidden, and will result in an overall forfeit in the tournament. Possibilities for cheating in Counter-Strike:Global Offensive are, for example; all kinds of multi-hacks, wallhack, aimbot, colored models, no-recoil, no-smoke, no-flash and sound changes. All hardware or software that has an influence on the game in such a way that the essence of the game is affected are banned from this tournament. Any use of this kind of hardware will result in a disqualification of the tournament as it will be recognized as cheating. When proven that a player is not cooperating in his own ban research or is lying on purpose. He will get banned for 1 edition. You can find our banlist at http://www.fom.be/contents/view/cs-go-banlist The mentioned people in our ban list are not allowed in the CS:GO tournaments at Frag-O-Matic until the edition that’s stated there. When these people compete under a false name nonetheless or try to circumvent the rules then they will receive an extended or permanent ban. Here are some of the other examples of ways to gain advantages, this list may not be the full list but if players are unsure of certain things, they should seek to ask the tournament admins first: Flash Bang, Smoke Grenade, and Hand Grenade Bugs - it is illegal to use any flash bang, smoke grenade, or hand grenade bugs, regardless of intent. Silent Bomb Plants - ALL bomb plants must be done in a position where your opponents can hear you. There should be no rotation in players to gain money advantages throughout a match. The bomb must be planted on solid surfaces on the map, ie where an opponent can defuse from, so not up in the air or floating. Illegal Bomb Defuses - No player can defuse a bomb through any other solid object on the map, it has to be done in clear view. It is also forbidden to try to intentionally distort your hitboxes during a defuse situation to prevent an opponent from killing you in game. Walking/Boosting through walls - No player should walk, boost through walls or roofs. To do so will see your team penalized for that round. Map Exploits - Boosts that include the use of clipping are strictly forbidden. The term “Clipping” defines that when a player is boosted can see through certain parts of the map (ie over/under walls, or through solid objects on the map). If any player or team feels unsure on a new advantage they have found through their practice sessions, they are welcome to show this specific spot to the tournament team to review. Any player or team that does this will be treated to the strictest confidence as not to jeopardize your strategic advantage, however we can rule on whether it is a legal move. We strongly advise teams to give us plenty of time ahead of an event so we can review it in good time and make good judgement on it. The game admins may inspect your machine at any time throughout the event to inspect for cheats or hacks within your game files, steam cloud and anywhere on your PC or memory sticks. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="forbiditems"></a>2.7.1 Forbidden items During the lan, to prevent cheating by using external devices or items, the following items are forbidden: <ul> <li>Smartwatches; Having or carrying a smartwatch during the event, when competing in the CS:GO competition, that player will immediately be disqualified from the competition.</li> <li>Alienware Wireless Headset AW988; Visual representation of audio isn’t allowed.</li> <li>AR (augmented reality) glasses</li> <li>Hardware from the brand “Bloody” (these are mice that come with software that reduces recoil on weapons)</li> </ul> Any other electronic devices (like smartphones) that are used during a match will be considered suspicious and we’ll ask that they’re not used. If, during a match, the suspicious device is still in use; the team of the player using the device will receive a warning. After 3 warnings the team will receive a disqualification from the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="match"></a>2.8 Match protests and forfeit <a name="definitions"></a> 2.8.1 Definition A protest is a raised issue for problems that affect the match outcome; a protest may even be filed during a match for things like incorrect server settings and other related issues. A protest is the official communication between a team captain and a tournament admin. A forfeit is a lose or surrender. <a name="matchprotest"></a> 2.8.2 Match protest rules Participants are only allowed to issue a match protest before the beginning of their next match. The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “they are cheaters” will not be enough. Insults and flaming are strictly prohibited in a protest, and may result in the protest being ruled against the insulting party. <a name="forfeitrules"></a> 2.8.3 Forfeit rules A forfeit can be called for a single match or the entire competition from a competing team for their team. Only the team captain can raise a forfeit for their team. A forfeit can also be raised by an admin as a penalty for wrongdoing. For example, in most cases where a competing team doesn’t follow the time schedule. The tournament admins can always force a forfeit. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="seeding"></a>2.9 Seeding Seeding is done through an objective outlook towards data provided by all participants for every event. Every participant is required to provide us their main steam account, ESEA and/or CEVO profile, FACEit level and previous wins/achievements. The supplied data is only kept and used for one event to calculate an individual “score” based on reached rank, played time, csgo hours and historical performance/achievements from Frag-o-Matic or other tournaments. The team sum of 5 individual scores will show an objective score where the higher the score, the higher the team seeding. The tournament admins won’t seed teams higher based on any subjective opinions. If no statistical data was provided for all 5 team member, than that team will be seeded beyond top 16. <a name="general"></a>3. General <hr /> <a name="generalrules"></a> 3.1 General rules Frag-o-Matic Counter strike:Global Offensive (CS:GO) 5v5 tournament is a local area network (LAN) tournament. By competing in this tournament, teams and players accept these rules in full. Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation. In the beginning of the LAN the team captains can sit together with the admin to discuss the rules and to make adjustments if needed. The decisions are made by the admin. If you have any issues with the rules, you can explain this by sending an email to <a href="mailto:csgo@fom.be">csgo@fom.be</a> up to one week before the start of the event. Clarification of any point in the rules is available from the tournament admins at any time during the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="sanctions"></a>3.2 Sanctions and disputes Sanctions and disputes will be resolved by the main tournament admin. The admin’s decision on any sanction or dispute is final. Abusive behavior towards the Frag-o-Matic staff, tournament admins or opponents at any time during the tournament is unacceptable and will be punished with warnings. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="confidentiality"></a>3.3 Confidentiality The content of protests, support communication, discussions or any other correspondence with tournament officials and administrators are considered as strictly confidential. The publication of such material is prohibited. If the contents has been shared without consent then this could lead to a team’s disqualification. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="coc"></a>3.4 Code of conduct Any form of aggression<a href="#coc_aggression">*</a> (both verbally and physically) will not be tolerated. Any and all physical aggression will be sanctioned with an immediate disqualification by that person or team performing the physical act (both actioned and reactioned). Any verbal aggression will be sanctioned by a time-out for that person or team. A time-out is either set in time (hours/day) or in amount of matches when a player or team is not allowed to participate in the CS:GO competition. Any situation that is about to escalate should be dealt with in a calm and diplomatic manner. An audience with any Frag-o-Matic crew member (CS:GO admin or Frag-o-Matic team leaders) can always be called for at any time during the event. Keep in mind that this audience can not be used to waste time or get a time advantage. At any point, the CS:GO tournament admins can decide to continue with the competition with or without consent from either players or other Frag-o-Matic staff. In the event when a single player or more are accused of cheating, the event will continue nonetheless. Evidence will be presented to the tournament admins and a call will be made at a later stage of the event. This rule is set to not cause any delays and have the situation under control. Any player(s) or team(s) ignoring this rule will receive a forfeit. Any player or team ignoring a CS:GO admin will be sanctioned with a warning. 3 warnings are equal to a forfeit of 1 match. <a name="coc_aggression"></a>*A form of aggression is described as: <ul> <li>Instrumental aggression -- Aggression aimed at obtaining an object, privilege or space with no deliberate intent to harm another person. Typical of participants wanting to get ahead of the competition with lies, anger, bullying, criticizing other people behind their backs, leaving others out of a group or otherwise ostracizing them, turning people against each other, dismissing the opinions of others (passive aggression).</li> <li>Hostile aggression -- Aggression intended to harm another person, such as hitting/kicking/biting someone (active aggression). Threatening to beat up someone (nonverbal intimidation). Sending threatening messages through emails, phone calls, or social media, or making threats against someone's life, shouting, and swearing (verbal hostility). Breaking someone's computer, destroying someone's cell phone, or other forms of vandalism (destruction of property).</li> <li>Relational aggression -- A form of hostile aggression that does damage to another's peer relationships, as in social exclusion, gossiping or rumor spreading. Examples: Arguments within a team after a lose that lead to a verbal fight.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="drugsalcohol"></a>3.5 Drugs and alcohol To play a match under the influence of any drugs or performance enhancers is strictly prohibited, and may be punished with exclusion from the tournament. If an admin finds that a player is not capable of competing in the competition because of intoxication, the admin can exclude that person from the entire tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="betting"></a>3.6 Betting Betting on any match in the CS:GO tournament is strictly forbidden. <a name="addagreement"></a>3.7 Additional agreements Teams may be required to play any match on the stage. If so, teams will be notified at least 20 minutes prior to the start time of that match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="streaming"></a>3.8 Streaming, interviews and media <a name="broadcasting"></a>3.8.1 Broadcasting Frag-o-Matic reserves the right to broadcast any match or demo, teams may not refuse such broadcasts. All forms of client side game broadcasting are NOT allowed. Frag-o-Matic participants are not allowed to watch a local GOTV if a CS:GO server broadcasts a game. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchmedia"></a>3.8.2 Match media All match media (screenshots, demos, etc.) must be kept until the end of the event. Faking or manipulating match media is forbidden and will result in exclusion from the tournament. Match media should be named clearly based on what it is. It is not possible to file a protest to complain about bad match media naming. However if a tournament admin is hindered in their work because of bad match media naming, then a tournament admin will give a warning. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="screenshots"></a>3.8.3 Screenshots The admin can ask for screenshots of every game on any moment during the event. When he does this, the team leader has 15 minutes time to deliver the screenshot to the admin. A screenshot of the scoreboard at the end of each half must be taken. When this is not done by a team it can result in a lost match when one of the other teams complains about a score. An RCON status screenshot must be taken: <ul> <li>at the beginning of the match</li> <li>in case of a server/player change</li> <li>if a player reconnects</li> </ul> RCON status screenshots made with the help of programs like HLSW etc. are not sufficient. In order to take an RCON status you have to use the console command “rcon status” (don’t forget to enter your RCON password) and take a screenshot of that. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="playerchanges"></a>3.9 Player changes Teams are permitted to substitute players (only with another player not active in the CS:GO competition) during pauses and between rounds, if they have permission from the tournament admin. Consent for substitutions must be obtained from the tournament admins, and substitute players must be registered for that team in the tournament. You can make this clear to the admin by using the contact information in section ‘Admins and communication’. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="prizemoney"></a>3.10 Prize money When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="csgorules"></a> 4. Counter-Strike:Global Offensive rules <hr /> <a name="tournament"></a>4.1 Tournament structure and time schedule Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. On Saturday and Sunday, teams must be present at 10:00 (AM) and ready to start playing the rest of their scheduled matches. It can be the case that the tournament admins decide to start earlier or end later, but this will be communicated (to all team captains). An exact time schedule will be provided on our fom.be website for all teams to follow. Each match will have a start time on which the game needs to be started. The team(s) that are responsible where the start time has not been met will receive a forfeit for that match. Whether or not this rule will be applied, is the decision of a tournament admin. The schedule for the tournament may be subject to change at any time. Matches may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice. Games will not be rescheduled to an earlier time in the same day if either of the teams have not yet played a game on that day without the consent of both team captains. Where possible the tournament admins will notify any teams involved in a rescheduled game of the new match start time at least one hour before the new start time. In the event a match is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible. If there’s insufficient time to complete a match, the tournament admins may at any time declare one team as the winner, if that team holds a clear advantage in that match. It is the responsibility of the tournament admins to decide whether a team holds a clear advantage. This rule will only be used in the emergency when the remaining event time is a factor. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="penalties"></a>4.1.1 Penalties and forfeits during the time schedule If 1 or more teams are still playing a match in a previous stage or if 1 team is late and doesn’t start playing their match in the stage where they are; Teams are offered 30 minutes of grace time in both circumstances, after 30 minutes warnings are handed out: After 30 minutes that team, who’s still not playing their scheduled match, will receive a 1st warning from a tournament admin. A notice via our csgo channel on discord and if the team is present and found at their seat they’ll be warned in person as well. A second warning is given in the same manner 5 minutes after the first warning. A third and final warming is given in the same way 5 minutes after that. 5 minutes after the final warning the team who received 3 warnings will receive 1 game loss for their match in the next round. In case of a bo3 in the next round, a bo2 will be played with one win to the team that was on time. If after 15 minutes the team with 3 warnings and one loss in the next round is still not playing, they’ll receive a forfeit from an admin. In case of a bo1 (in the lower bracket for example) we won’t lose any more time and a forfeit will be forced. The forfeit is applied on our fom.be website and a notice is given on Discord in our csgo channel. The tournament admins will keep a record of the warnings and will communicate this to the compo desk. As mentioned in our general rulebook; Non-acceptable excuses for a delay: “We want to eat” isn’t a valid excuses for starting an argument at the compo desk. As a note, we ask that teams only take a maximum of 15 minute breaks in between games and matches to avoid any penalties. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compomaxteams"></a>4.1.2 Compo sign-up and max teams All compo sign-ups are done via our fom.be website. Some rules are already explained in our general rulebook. Any team that is not “full”, meaning the team doesn’t consist of minimum 5 players, will be removed from the compo sign-up one hour before the start of the competition. We allow a maximum 64 teams to register to our CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="structure"></a>4.1.3 Structure Our CS:GO tournament will use a poule system and 3 double elimination brackets (pro, semi-pro and fun). Each poule will consist out of 3-4 teams who will compete against each other to make it into the brackets. Each team within the poule needs to play against any other team within its poule. Following the poule stage, the 2 winners from each poule will advance to a pro bracket, the last 2 teams from each poule will advance to a semi-pro bracket and <s>other teams will proceed to the fun bracket</s>. Our compo structure will use the following setup for pro, semi-pro and fun: <ul> <li>Groupstage > BO1 (best of 1)</li> <li>Upper Bracket > BO3 (best of 3)</li> <li>Lower Bracket > BO1 (best of 1)</li> <li>Pro & semi-pro bracket: <ul> <li>Semi-final (Finals in lower bracket) > BO3 (best of 3)</li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> </li> <li><s>Fun bracket:</s> <ul> <li><s>Semi-final (Finals in lower bracket) > BO1 (best of 1)</s></li> </ul> </li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> When 2 teams have the same amount of points after the poules we will look at the following criteria in order: <ul> <li>The match between the 2 teams</li> <li>The won rounds total</li> <li>The lost rounds total</li> <li>Seeding</li> </ul> We can also look at other criteria if we feel that it's necessary (also cooperation). The admin is allowed to overrule these criteria. If there’s not enough data to validate a criteria the admin can chose to ignore it. A tournament admin can decide to change some matches from BO3 to BO1 or visa versa when needed. (For example: no time to play a BO3). <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="gamesetup"></a>4.1.4 Game setup Matches will be played 5on5. Playing with fewer than five players in any match is only allowed with permission from the tournament admins. Before a match starts, both teams must state that they are ready to start the match. The must do this by having one team member typing ‘ready’ in server chat. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated. Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug. You’ll need to use the following match setup to play every game: <ul> <li>2 teams join the server that is assigned to them on our fom website.</li> <li>The team captains can use the RCON password “godmode” to follow the next steps : <ul> <li>Don’t forget to do ‘cl_mute_enemy_team 0’</li> <li>Change the map to de_mirage (rcon changelevel de_mirage)</li> <li>Load the Frag-o-Matic config (rcon exec fom5on5.cfg)</li> <li>Start a knife round on de_mirage (optional). The winner of this knife round can decide who team A is. Start the map veto process (Veto is explained under ‘Veto system’’).</li> <li>After the Veto the team captain needs to change the map to the first map of Team A (in a BO3) or the single map that was chosen (in a BO1) (rcon changelevel ‘mapname’)</li> <li>Load the fom5on5.cfg again on this map. (rcon exec fom5on5.cfg)</li> <li>After this the teams do another knife round to decide which team will start on which side of the map. The winner of the knife round decides which side they want to start on and that team will also start the match. (rcon mp_restartgame 1)</li> </ul> </li> </ul> If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server can be paused at the end of the current round (see rule ‘Usage of pause’ function) by one of the teams. The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed. If a player/substitute doesn’t connect within that time, then the match is continued 4on5, or 4on4 if the opposing team agrees and the tournament admins are informed. There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="vetosystem"></a>4.1.5 Veto system Our veto process is the next step after playing a knife round, as described in ‘Game setup’. The map(s) chosen to be played in each BO1 and BO3 are done via elimination (i.e. veto). Where ‘team 1 = A’ and ‘team 2 = B’, with A being decided by the winner of the knife round. Teams can also decide who team A/B is without playing a knife round. The maps you don’t want to play as a team, should be the maps that you veto during this process. The veto process needs to be done in server chat. VETO rules best-of-1: ABABAB veto. The map pool exists out of 7 maps. 6 maps are vetoed during this process, 3 maps for each team. The remaining map is the map played in the best-of-1 match. VETO rules best-of-2: ABAB veto AB play. The map pool exists out of 7 maps. 4 maps are vetoed during this process, 2 maps for each team. Out of the 3 remaining maps, 1 team each gets to decide a map to play on. VETO rules best-of-3: A/B veto, A/B play and A/B veto. The map pool exists out of 7 maps. 4 maps are eliminated, and 3 maps are selected to play. Each team needs to veto a map, followed by each team choosing a map and again each team vetoing a map. The remaining map is the third map that needs to be played if both teams win a map. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compospecificrules"></a>4.1.6 Compo specific rules All matches in the group stage are played MR15. All matches in the brackets are played MR15 (meaning, 16 rounds won = game win). In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games are best of three (BO3) in the bracket, 3 maps are decided by veto. The grand final is a best of three (BO3) with map advantage! When in the brackets a game is tied an overtime needs to be played. The overtime will be played MR3 with 10.000$ start money. For the start of the overtime teams will stay on the side which they played the previous half on, during halftime sites will be swapped. Teams will continue to play overtimes until a winner has been found. We have our own special breed of bracket seeding. For more information please contact us in advance. This bracket seeding is law. Obey it. All CS:GO players can only use our ts.fom.lan (local) teamspeak for voice communication. Teams are only allowed to have 5 players + 1 coach in their teamspeak channel whilst in a competition match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="usageofpause"></a>4.1.7 Usage of pause Pauses may be taken for any reason. Teams are permitted 3 pauses per side in each match. Each pause having a maximum duration of 5 minutes, unless authorised by an admin to take a longer pause (in case of technical difficulties, for example). After a “pause”-event, an “unpause“-command needs to be done. Teams can’t unpause without the consent of the other team. Pauses may only be activated at the start of the next round during freeze time. So make sure you tell the other team before round end (in all-chat), that your team will take a pause in the next freeze time. Usage: Type the following commands in console, to activate and deactivate the pause event. Pause = rcon mp_pause_match Unpause = rcon mp_unpause_match Illegal usage: DON’T USE = sv_pause If a team does use sv_pause, they have to surrender 1 round. (by all team members typing “kill” in console) <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="demofiles"></a>4.1.8 Demo files GoTV demos must be active for each match to be recorded. It’s the responsibility of (both) team captains to ensure that GoTV is recording. If this isn’t the case, the tournament admins will be forced to make calls without a recording when a dispute occurs. It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A knife round is part of a match and should be recorded. At least one of the players must be able to upload the knife round on admin request. Protests regarding missing knife rounds are not valid. In general, defective or manipulated demos will be treated as missing demos. If the demo is incomplete, as decided by the admin, it also will be treated as missing demo. If a protest is opened for a match, all match media need to be kept until the end of the event. Demos can only be requested up to a maximum of 30 minutes after a match via the admin. A demo request must state which teams were playing, the name(s) of the map(s) the match(es) was/were played on, the time of the match(es) and the server IP address(es). If a player or a team illegally aborts the match, they lose their right to demand demos. Recording demos is recommended. Our servers will likely record demos for every match but these are only used when there is doubt about a decision the admin has to make. It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.2 Match procedure <a name="maplist"></a>4.2.1 Map list Only the following maps are allowed to be played on during the competition: <ul> <li>de_ancient</li> <li>de_anubis</li> <li>de_inferno</li> <li>de_mirage</li> <li>de_nuke</li> <li>de_overpass</li> <li>de_vertigo</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchrules"></a>4.2.2 Match rules <ul> <li>Diffusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.</li> <li>Throwing grenades/flash bangs/smokes across walls in maps is allowed.</li> <li>Boosting is not considered a bug.</li> <li>Buying and using multiple grenades is allowed but with a max of 2 flash bangs.</li> <li>Multiple grenades are allowed but max 2 flash bangs</li> <li>Bugs on the map must be checked before the match begins. Any protest after the match about map bugs will be ignored.</li> <li>If a player loses connection before the first kill, the match can be restarted. If this happens after the first kill, the server can be paused and have the disconnected player reconnect. Matches won’t be restarted due to disconnections.</li> <li>If you want a player change (sub) during the match, inform the opponent and the compo admins before the match begins!</li> <li>To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.</li> <li>Climbing with help of teammates is allowed in general.</li> <li>Throwing grenades inside walls is not allowed.</li> <li>Self-kills are strictly forbidden, unless an admin forces you to do this as a sanction for disobeying any rules.</li> <li>Bomb planting in a way it can’t be reached is forbidden.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="clientrules"></a>4.2.3 Client rules The admin is allowed to take over your computer before, during and after a game and have a look. Without the pc’s owner in question nearby, the person in question can appoint someone to stay with the admin to make sure no privacy issues are violated. Any trace evidence of cheats found on a player’s computer – even if such discovery took place outside of a game – can lead to exclusion from any competition. For NVIDIA graphics card users: The use of Ambient Occlusion is strictly forbidden. If you are caught using this setting, this will result in a direct loss of the match. Getting caught for a 2nd time will result in removal from the tournament. This setting can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings. The following commands are forbidden: <ul> <li>mat_hdr_enabled</li> </ul> The following startparameters are forbidden: <ul> <li>+mat_hdr_enabled 0/1</li> <li>+mat_hdr_leven 0/1/2</li> </ul> In your game client cfg-folder you’re only allowed to have config files. Pictures, demos, screenshots and zipped files are forbidden. All other configuration changes are allowed as long as they do not give an unfair edge or advantage comparable to cheating. The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary. Boosting through walls/ceilings/ground, sky walking, map swimming, floating and sharking are all forbidden. To throw grenades inside walls is not allowed. Above walls and roofs is allowed. To plant the bomb in a way that it cannot be reached is forbidden. Places that can be reached with help of a team mate are allowed as long as they are visible. Violating this rule will result in tournament administrators intervention. Changing graphic settings to irregular values can be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalscripts"></a>4.2.4 Illegal scripts In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts: <ul> <li>Stop Shoot scripts [Use or Awp scripts]</li> <li>Center view scripts</li> <li>Turn scripts [180° or similar]</li> <li>No Recoil scripts</li> <li>Burst fire scripts</li> <li>Rate changers (Lag scripts)</li> <li>FPS scripts</li> <li>Anti flash scripts or binding (snd_* bindings)</li> <li>Bunnyhop scripts</li> <li>Stop sound scripts</li> <li>Following Commands/CVars are forbidden</li> <li>+weapon_recoil_model 0 (Startparameter)</li> </ul> The following CVAR values must be used: <ul> <li>cl_bobcycle 0.98 (First Time->Warning)</li> </ul> If there are more than one player who used a wrong client setting, the match will be deleted. Exception: cl_bobcycle Using illegal scripts will be penalized if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized. The use of No-Flash and No-Recoil bindings/scripts in any and all forms will be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="customfiles"></a>4.2.5 Custom files The HUD can be changed as long as no information are deleted or falsified which are available in the standard HUD. If the HUD is changed it has to be readable. If an admin is hindered in his work due to an unreadable HUD, penalty points may be assigned. Protests or supports which adhere to this rule will not be admitted and are rejected directly. Apart from the HUD and the GUI no custom files are allowed. This also includes custom models, changed textures or sounds (volume, soundscapes) are forbidden. <a name="colordepth"></a>4.2.6 Color depth and external programs The usage of a color depth of 16bit is not allowed. The usage of external programs (ex. SweetFX, A3D,...) are not allowed to enhance vision. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalprograms"></a>4.2.7 Illegal programs Changing the game graphics or textures with the help of video card drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. NVidia SLI Display, Riva tuner Overlays) is illegal. Failure to comply with this rule will result in a punishment for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized. If you play with ambient occlusion, it will be punished as cheating!! Punishment will be given regardless of whether the script/binding is executed via external hardware or software. Also binding any snd_ command is forbidden. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="ingameoverlay"></a>4.2.8 In-game overlays All In-Game overlays – provided by the game itself – except the following are forbidden: <ul> <li>net_graph 0</li> <li>net_graph 1</li> <li>cl_showpos 1</li> <li>cl_showfps 1</li> <li>cl_showdemooverlay 1 / -1</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="techprobs"></a>4.2.9 Technical problems and disconnects If a disconnection occurs the game should automatically reconnect. When this doesn’t work, a tournament admin will decide what to do. The tournament admin will make a call in every possible scenario regarding the severity of the problem and how to deal with it. But, the following guidelines are in place in the event of a disconnect: <ul> <li>In the case where Frag-o-Matic is responsible for the disconnect, the round needs to be restored to the start of the round where the disconnection happened. I.e. follow the steps as described under “4.3.2 Server crash”.</li> <li>When a player is responsible for his own disconnect, the team with 4 players can decide to continue to play 4v5 or use a pause as described in “4.1.6 Usage of pause”.</li> <li>The disconnected player can then reconnect to the match. If that player fails to reconnect, then the match will continue 4v5.</li> <li>If another Frag-o-Matic participant is responsible for causing a problem, then the match needs to be paused and a tournament admin needs to be notified to make a call on what to do.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.3 CS:GO server <a name="serversettings"></a>4.3.1 Server settings Frag-o-Matic will supply hardware for all servers. All games related to the tournament must be played on these servers. All matches will be played using the latest version of CS:GO and the official Frag-o-Matic CS:GO server config. All matches have to be played on an official Frag-o-Matic CS:GO tournament server and on the provided server number (as listed on our fom.be website, in the csgo compo section). We’ll use a standard (ESL) 5v5 pro league tournament config on a 128 tickrate server: <ul> <li>Startmoney: 0</li> <li>Maxrounds: 30</li> <li>Roundtime: 1m 55s (1.92)</li> <li>Freezetime: 12 seconds</li> <li>C4timer: 40 seconds</li> <li>Pause: 1x 5minutes per half each map.</li> <li>Overtime: MR3 - .000 startmoney</li> <li>Time during half time: 13 seconds</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="servercrash"></a>4.3.2 Server crash In the event of a server crash, after notifying a tournament admin and having them restart the the server, both teams have to re-join the same server and use the following command: <ul> <li>rcon mp_backup_restore_list_files</li> </ul> This will show you the backup files before the server crashed. 1 team captain then executes the correct file by using the following command: <ul> <li>rcon mp_backup_restore_load_file</li> </ul> Example: rcon mp_backup_restore_load_file backup_round12.txt All previous settings (score, money, armor, weapons,...) are then reset to the round before the server crashed and the match is set to paused. To continue the match, use the unpause command: <ul> <li>rcon mp_unpause_match</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="serverlag"></a>4.3.3 Server (var) lag Teams are given the time to play a warm-up match on their server before every compo match if they wish to do so. It’s not allowed to switch to another server once the compo match has been started. Test the server before the match starts. Any server problems should be reported to a tournament admin by going to the compo desk after sending an email with the information below. In the event that you experience any lag during or before a match, please note the time(s) and contact us via Discord or the Compo Desk. We'll escalate this information and, if possible, provide a solution for upcoming matches. The statement or report of (possible) lag in a match is a not valid argument in a protest. However, sending us the data above will give your team the time necessary to avoid any possible forfeits when you notify us at the compo desk after sending your email. Failure in providing us this data will not allow your team to deviate from our time schedule. We strive to provide all our servers lag free. We would like to thank you in helping us improve our servers. <a name="serverplugins"></a>4.3.4 Server plugins No extra plugins will be installed on our CS:GO servers. <a name="rconusage"></a>4.3.5 RCON usage RCON is only allowed as described in “4.1.2 Game setup”. Usage of RCON outside the game setup is penalised by receiving an instant forfeit for the team using any other RCON commands. We monitor all servers and RCON logs and will use this as evidence to hand out a match forfeit to the team using RCON outside of the game setup rules. <a name="rconusage"></a>4.3.6 Warmup servers Subject to availability, we will provide warmup servers. The settings will mirror our war servers as close as possible, but won’t be managed by the csgo team. Participants in our competition are allowed to use our warmup servers as such, to warm up, practice nade throws, practice aim,etc… We will not guarantee availability of those servers, since they will depend on the overall capacity. If warmup servers are available, they cannot ever be used for playing matches. If a match has been played on one of those servers though, the end-scores will still count. It is the responsibility of both teams the correct (assigned) server is joined. At any time, we can convert one of those servers to an official war server (In cases of need). It will at that point no longer show up as a warmup server. <a name="copyright"></a>5. Copyright Notice Copyright © 2005-2022 by E-EVENTS VZW All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher, addressed at <a href="mailto:csgo@fom.be">csgo@fom.be</a> </li> </ul>
 showsponsor(false)
 sponsorcontent
 showfiles(false)
 filescontent
 prizescontent<h1> First Place </h1> <ul> <li> <h3>525 €</h3> </li> </ul> <h1>Second Place</h1> <ul> <li> <h3>315 €</h3> </li> </ul> <h1>Third Place</h1> <ul> <li> <h3>210 €</h3> </li> </ul>
 precompo(false)
 donations0
 donationAmount0
 scheduleregistration closes at 21! please make sure all games are played on time! poules will be made and will be playable. saturday 10am we will start with the brackets semi final will be at 10am on sunday with afterwards the grand final Have fun and Good luck!
 faq
 sponsorUrl
 sponsorImg(null)
 sortTimeLabel0
 TeamA(array)
 id10509
 nameiNTERMiXED
 leaderId1362
 compoId367
 pouleId1453
 notes
 withdrew(false)
 TeamB(array)
 id10265
 nameBASTARDS.AF9K
 leaderId5352
 compoId367
 pouleId1452
 notes
 withdrew(false)
 AdminEdit(array)
 id(null)
 facebook_id(null)
 username(null)
 new_username(null)
 nickname(null)
 password(null)
 firstname(null)
 lastname(null)
 active(null)
 validationCode(null)
 mailValidationCode(null)
 group_id(null)
 created(null)
 modified(null)
 last_login(null)
 street(null)
 nr(null)
 bus(null)
 zip(null)
 city(null)
 country(null)
 phone(null)
 gsm(null)
 gender(null)
 birthdate(null)
 clanId(null)
 clantrust(null)
 clanjoinId(null)
 hwbudget(null)
 education(null)
 profession(null)
 hoursaweek(null)
 language(null)
 oldId(null)
 receive_newsletter(null)
 imageUrl(null)
 slug(null)
 fb_link(null)
 fb_location(null)
 CPU(null)
 MOBO(null)
 GFX(null)
 RAM(null)
 steamName(null)
 steamId(null)
 originName(null)
 lolSummonerName(null)
 Other(null)
 comment(null)
 seat_id(null)
 msg_notifications(null)
 mouseHand(null)
 deviceId(null)
 alternative_login(null)
 3(array)
 War(array)
 id27959
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10265
 teamB10299
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB6
 scoreBByB16
 finalScoreA6
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1452
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 06:30:44
 Compo(array)
 id367
 nameGRAND - CS:GO
 steamGameId(null)
 nrPlayersTeam5
 maxTeams64
 compoTypeId0
 nrPoules3
 nrWinnersPoule4
 compoStateId5
 eventId46
 roundDE2
 addSecondaryFinal(false)
 adminId8749
 adminId2(null)
 bannerUrl(null)
 description<h1>password to the servers: war</h1> 
 tagId31
 allowDrawInPoule1
 nrLosersToBrackets0
 pauzed0
 rulebookFrag-o-Matic 24.0 Rulebook Counter-Strike:Global Offensive (CS:GO) Introduction This is the official rulebook for the Frag-o-Matic 24.1 CS:GO competition, that will take place from the 1st until the 3rd of September 2023. These rules apply to the players throughout all stages of CS:GO competition. Failure to adhere to these rules may be penalized as outlined. It should be noted that the tournament administrators have the final word, and have the power to decide on any circumstances that are not outlined by this document, and in extreme cases may overrule the rulebook in order to preserve fair play and sportsmanship. Frag-o-Matic reserves the right to change these rules at any time. The CS:GO admin team wishes you good luck in the tournament and hopes that you have an enjoyable competition. We’ll do our utmost best to make it fair, fun and exciting for everyone involved. <a name="navigation"></a>Table of contents <ol> <li><a href="#admin">Admins and communication</a></li> <li><a href="#compo">Compo overview</a> <ol> <li><a href="#participants">Participants</a></li> <li><a href="#teamsheets">Team sheets</a></li> <li><a href="#teamnames">Team names</a></li> <li><a href="#teammanager">Team manager / coach</a></li> <li><a href="#teamcaptain">Team captain</a></li> <li><a href="#players">Players</a> <ol> <li><a href="#grstandard">Grooming standards</a></li> </ol> </li> <li><a href="#cheating">Cheating</a> <ol> <li><a href="#forbiditems">Forbidden items</a></li> </ol> </li> <li><a href="#match">Match protests and forfeit</a> <ol> <li><a href="#definitions">Definition</a></li> <li><a href="#matchprotest">Match protest rules</a></li> <li><a href="#forfeitrules">Forfeit rules</a></li> </ol> </li> <li><a href="#seeding">Seeding</a></li> </ol> </li> <li><a href="#general">General</a> <ol> <li><a href="#generalrules">General rules</a></li> <li><a href="#sanctions">Sanctions and disputes</a></li> <li><a href="#confidentiality">Confidentiality</a></li> <li><a href="#coc">Code of conduct</a></li> <li><a href="#drugsalcohol">Drugs and alcohol</a></li> <li><a href="#betting">Betting</a></li> <li><a href="#addagreement">Additional agreements</a></li> <li><a href="#streaming">Streaming, interviews and media</a> <ol> <li><a href="#broadcasting">Broadcasting</a></li> <li><a href="#matchmedia">Match media</a></li> <li><a href="#screenshots">Screenshots</a></li> </ol> </li> <li><a href="#playerchanges">Player changes</a></li> <li><a href="#prizemoney">Prize money</a></li> </ol> </li> <li><a href="#csgorules">Counter-Strike:Global Offensive rules</a> <ol> <li><a href="#tournament">Tournament structure and time schedule</a> <ol> <li><a href="#penalties">Penalties and forfeits during the time schedule</a></li> <li><a href="#compomaxteams">Compo sign-up and max teams</a></li> <li><a href="#structure">Structure</a></li> <li><a href="#gamesetup">Game setup</a></li> <li><a href="#vetosystem">Veto system</a></li> <li><a href="#compospecificrules">Compo specific rules</a></li> <li><a href="#usageofpause">Usage of pause</a></li> <li><a href="#demofiles">Demo files</a></li> </ol> </li> <li><a href="#matchprocedure">Match procedure</a> <ol> <li><a href="#maplist">Map list</a></li> <li><a href="#matchrules">Match rules</a></li> <li><a href="#clientrules">Client rules</a></li> <li><a href="#illegalscripts">Illegal scripts</a></li> <li><a href="#customfiles">Custom files</a></li> <li><a href="#colordepth">Color depth and external programs</a></li> <li><a href="#illegalprograms">Illegal programs</a></li> <li><a href="#ingameoverlay">In-game overlays</a></li> <li><a href="#techprobs">Technical problems and disconnects</a></li> </ol> </li> <li><a href="#csgoserver">CS:GO server</a> <ol> <li><a href="#serversettings">Server settings</a></li> <li><a href="#servercrash">Server crash</a></li> <li><a href="#serverlag">Server (var) lag</a></li> <li><a href="#serverplugins">Server plugins</a></li> <li><a href="#rconusage">RCON usage</a></li> <li><a href="#warmupservers">Warmup servers</a></li> </ol> </li> </ol> </li> <li><a href="#copyright">Copyright Notice</a></li> </ol> <a name="admin"></a>1. Admins and communication <hr /> Communication before the LAN: <ul> <li>General contact > <a href="mailto:csgo@fom.be">csgo@fom.be</a></li> </ul> Please email us any feedback before and after the LAN event. CS:GO admin team: <ul> <li>Dragon <ul> <li>Steam: https://steamcommunity.com/profiles/76561198244170010/</li> <li>Discord: dragon (main communication line)</li> </ul> </li> </ul> Communication during the LAN: The communication during the LAN will be through Steam, Discord or at the Compo Desk. We will be available as much as possible in the <a href="https://discord.gg/URX6v82Wmp" target="_blank">#csgo channel</a>. We will use this as a second channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #csgo channel. Discord will be our main communication channel. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compo"></a>2. Compo overview <hr /> <a name="participants"></a> 2.1 Participants Due to lack of time, we have a tight schedule. Therefore we can make the decision to force teams to only participate in 1 grand compo! We will contact the teams who are signed in for 2 grand compo’s at the moment and they will need to make a choice. When a team refuses, we will remove them from the competition to make room for other teams. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamsheets"></a> 2.2 Team sheets As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops. A rule violation by any player in a team may lead the tournament admins to sanction the entire team, even if the rest of the team was not aware of the violation. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamnames"></a> 2.3 Team names <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teammanager"></a> 2.4 Team manager / coach The team manager does not have any responsibilities. The team manager is eligible to play for his team in matches, providing he’s indicated as a “Player” on the team in the team sheet. The communication with the team will not go via the team manager, all communication will go via the team captain! Spectators are not allowed on our servers. Only tournament admins may be in spectator mode during a match. The only exception is: coaches are allowed to spectate a match using the coach's command, only if the tournament admin is notified, and thus to spectate their team only. They are obligated to use the “coach t” or “coach ct” command before the match start and aren’t allowed to join after a match has been started. If noticed that the coach is abusing this rule, the team will get punished for it (e.g. round loss, side loss or match loss). During a match, the coach may only communicate with the players during freeze-time, warm up, half-time, or during one of the 4 timeouts. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamcaptain"></a> 2.5 Team captain We consider the one who registered the team into the compo on the Frag-o-Matic website as captain! The clan leader or team captain is responsible for his team and all the players in that team. It is recommended that the team captain is fluent in English or Dutch, as he will be required to communicate with the tournament admins. The team captain must read and understand the rulebook. The team captain is responsible for ensuring his team and players adhere to the rules. Ignorance of the rules is not an excuse for rule violations. The team captain may choose at any time to nominate another player in or manager of his team as team captain for any reason. Such nominations must be reported by the team captain, either in person or in writing, to the admins before the game starts. All official communication between a competing team and the tournament admins must be conducted by the team captain. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="players"></a> 2.6 Players All players must read and understand the CSGO rulebook. Any player in violation of a rule, will be sanctioned as described in this rulebook. Each team must have five players on the match server at the match start time as indicated by the schedule, unless permission has been granted by the tournament admins to play with less than five players. Only players registered for a team in the tournament may play for that team unless otherwise discussed with the tournament admin. All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins. Players registered for a team in the tournament may not play for any other team in the same tournament. Each player has to use their nickname that is similar to the nickname he/she has entered on their fom.be account. All players for a team must be clearly identifiable in-game with a uniform tag for that team and a separate, noticeably different nickname for each player. Players may not significantly change their nickname during the tournament. Any nickname they use during the tournament must always obviously visibly correspond to their original nickname. You are not allowed to change your nickname in-game. If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning. 3 warnings are equal to a forfeit in 1 match. Player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate. Make sure your steam account is linked with your fom.be account corresponding to your nickname. Players are strictly prohibited from using any other person’s steam account for any reason whatsoever during the CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="grstandard"></a> 2.6.1 Grooming standards People participating in the CS:GO tournament are expected to normal grooming standards. You may be asked to take action if you or your clothing have a look or odor that’s offensive to other players. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="cheating"></a> 2.7 Cheating During Frag-o-Matic we won’t investigate cheaters from an external event. When we discover someone cheating during our LAN, that player and his team will be banned from the compo and the player will be also banned for the next Frag-o-Matic edition. Furthermore we will investigate reports of players cheating during other tournaments until 2 weeks before the LAN. When a player is discovered cheating during another tournament/platform 12 months before the event occurs, then that player will not be allowed to play on that edition of Frag-o-Matic within the CS:GO competition and the edition after that. If one of the following rules apply, then that player will not be allowed to compete in our tournament: Caught cheating within a tournament/platform 12 months before the start date of our event. There needs to be enough evidence for that player, that he/she was cheating and the tournament admins will judge if the evidence is valid OR if he/she was caught cheating on the following platforms: <ul> <li><a href="ts3server://ts.fom.lan">ts.fom.lan</a> - CS:GO admin channel</li> <li>Discord: <a href="https://discord.gg/MbPY2ge">https://discord.gg/MbPY2ge</a> <ul> <li>Teams are only allowed to use a uniform team name for their team.</li> <li>Teams may not change their team name during the tournament.</li> <li>Teams may not change their team in-game tag during the tournament, unless none was set.</li> <li>Duplicating team names of other teams is not allowed.</li> <li>Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.</li> <li>Team names are not allowed to be offensive.</li> <li>Please make sure your team name is filled in on your fom.be profile.</li> </ul> <ul> <li>Faceit</li> <li>Esl</li> <li>Valve (vac ban for any Counter strike: Global Offensive game)</li> <li>ESEA</li> <li>Cevo</li> </ul> </li> <li>When a player is caught selling or buying cheats. In any case the admin will have the final decision. This means that the admin will review the evidence and make the final call. If a player shows the intention of coming to our tournament to cheat and we’re provided evidence of this. Everyone from the community may send evidence to csgo@fom.be, when they suspect someone participating at Frag-o-Matic of cheating. All forms of cheating in matches are forbidden, and will result in an overall forfeit in the tournament. Possibilities for cheating in Counter-Strike:Global Offensive are, for example; all kinds of multi-hacks, wallhack, aimbot, colored models, no-recoil, no-smoke, no-flash and sound changes. All hardware or software that has an influence on the game in such a way that the essence of the game is affected are banned from this tournament. Any use of this kind of hardware will result in a disqualification of the tournament as it will be recognized as cheating. When proven that a player is not cooperating in his own ban research or is lying on purpose. He will get banned for 1 edition. You can find our banlist at http://www.fom.be/contents/view/cs-go-banlist The mentioned people in our ban list are not allowed in the CS:GO tournaments at Frag-O-Matic until the edition that’s stated there. When these people compete under a false name nonetheless or try to circumvent the rules then they will receive an extended or permanent ban. Here are some of the other examples of ways to gain advantages, this list may not be the full list but if players are unsure of certain things, they should seek to ask the tournament admins first: Flash Bang, Smoke Grenade, and Hand Grenade Bugs - it is illegal to use any flash bang, smoke grenade, or hand grenade bugs, regardless of intent. Silent Bomb Plants - ALL bomb plants must be done in a position where your opponents can hear you. There should be no rotation in players to gain money advantages throughout a match. The bomb must be planted on solid surfaces on the map, ie where an opponent can defuse from, so not up in the air or floating. Illegal Bomb Defuses - No player can defuse a bomb through any other solid object on the map, it has to be done in clear view. It is also forbidden to try to intentionally distort your hitboxes during a defuse situation to prevent an opponent from killing you in game. Walking/Boosting through walls - No player should walk, boost through walls or roofs. To do so will see your team penalized for that round. Map Exploits - Boosts that include the use of clipping are strictly forbidden. The term “Clipping” defines that when a player is boosted can see through certain parts of the map (ie over/under walls, or through solid objects on the map). If any player or team feels unsure on a new advantage they have found through their practice sessions, they are welcome to show this specific spot to the tournament team to review. Any player or team that does this will be treated to the strictest confidence as not to jeopardize your strategic advantage, however we can rule on whether it is a legal move. We strongly advise teams to give us plenty of time ahead of an event so we can review it in good time and make good judgement on it. The game admins may inspect your machine at any time throughout the event to inspect for cheats or hacks within your game files, steam cloud and anywhere on your PC or memory sticks. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="forbiditems"></a>2.7.1 Forbidden items During the lan, to prevent cheating by using external devices or items, the following items are forbidden: <ul> <li>Smartwatches; Having or carrying a smartwatch during the event, when competing in the CS:GO competition, that player will immediately be disqualified from the competition.</li> <li>Alienware Wireless Headset AW988; Visual representation of audio isn’t allowed.</li> <li>AR (augmented reality) glasses</li> <li>Hardware from the brand “Bloody” (these are mice that come with software that reduces recoil on weapons)</li> </ul> Any other electronic devices (like smartphones) that are used during a match will be considered suspicious and we’ll ask that they’re not used. If, during a match, the suspicious device is still in use; the team of the player using the device will receive a warning. After 3 warnings the team will receive a disqualification from the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="match"></a>2.8 Match protests and forfeit <a name="definitions"></a> 2.8.1 Definition A protest is a raised issue for problems that affect the match outcome; a protest may even be filed during a match for things like incorrect server settings and other related issues. A protest is the official communication between a team captain and a tournament admin. A forfeit is a lose or surrender. <a name="matchprotest"></a> 2.8.2 Match protest rules Participants are only allowed to issue a match protest before the beginning of their next match. The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “they are cheaters” will not be enough. Insults and flaming are strictly prohibited in a protest, and may result in the protest being ruled against the insulting party. <a name="forfeitrules"></a> 2.8.3 Forfeit rules A forfeit can be called for a single match or the entire competition from a competing team for their team. Only the team captain can raise a forfeit for their team. A forfeit can also be raised by an admin as a penalty for wrongdoing. For example, in most cases where a competing team doesn’t follow the time schedule. The tournament admins can always force a forfeit. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="seeding"></a>2.9 Seeding Seeding is done through an objective outlook towards data provided by all participants for every event. Every participant is required to provide us their main steam account, ESEA and/or CEVO profile, FACEit level and previous wins/achievements. The supplied data is only kept and used for one event to calculate an individual “score” based on reached rank, played time, csgo hours and historical performance/achievements from Frag-o-Matic or other tournaments. The team sum of 5 individual scores will show an objective score where the higher the score, the higher the team seeding. The tournament admins won’t seed teams higher based on any subjective opinions. If no statistical data was provided for all 5 team member, than that team will be seeded beyond top 16. <a name="general"></a>3. General <hr /> <a name="generalrules"></a> 3.1 General rules Frag-o-Matic Counter strike:Global Offensive (CS:GO) 5v5 tournament is a local area network (LAN) tournament. By competing in this tournament, teams and players accept these rules in full. Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation. In the beginning of the LAN the team captains can sit together with the admin to discuss the rules and to make adjustments if needed. The decisions are made by the admin. If you have any issues with the rules, you can explain this by sending an email to <a href="mailto:csgo@fom.be">csgo@fom.be</a> up to one week before the start of the event. Clarification of any point in the rules is available from the tournament admins at any time during the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="sanctions"></a>3.2 Sanctions and disputes Sanctions and disputes will be resolved by the main tournament admin. The admin’s decision on any sanction or dispute is final. Abusive behavior towards the Frag-o-Matic staff, tournament admins or opponents at any time during the tournament is unacceptable and will be punished with warnings. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="confidentiality"></a>3.3 Confidentiality The content of protests, support communication, discussions or any other correspondence with tournament officials and administrators are considered as strictly confidential. The publication of such material is prohibited. If the contents has been shared without consent then this could lead to a team’s disqualification. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="coc"></a>3.4 Code of conduct Any form of aggression<a href="#coc_aggression">*</a> (both verbally and physically) will not be tolerated. Any and all physical aggression will be sanctioned with an immediate disqualification by that person or team performing the physical act (both actioned and reactioned). Any verbal aggression will be sanctioned by a time-out for that person or team. A time-out is either set in time (hours/day) or in amount of matches when a player or team is not allowed to participate in the CS:GO competition. Any situation that is about to escalate should be dealt with in a calm and diplomatic manner. An audience with any Frag-o-Matic crew member (CS:GO admin or Frag-o-Matic team leaders) can always be called for at any time during the event. Keep in mind that this audience can not be used to waste time or get a time advantage. At any point, the CS:GO tournament admins can decide to continue with the competition with or without consent from either players or other Frag-o-Matic staff. In the event when a single player or more are accused of cheating, the event will continue nonetheless. Evidence will be presented to the tournament admins and a call will be made at a later stage of the event. This rule is set to not cause any delays and have the situation under control. Any player(s) or team(s) ignoring this rule will receive a forfeit. Any player or team ignoring a CS:GO admin will be sanctioned with a warning. 3 warnings are equal to a forfeit of 1 match. <a name="coc_aggression"></a>*A form of aggression is described as: <ul> <li>Instrumental aggression -- Aggression aimed at obtaining an object, privilege or space with no deliberate intent to harm another person. Typical of participants wanting to get ahead of the competition with lies, anger, bullying, criticizing other people behind their backs, leaving others out of a group or otherwise ostracizing them, turning people against each other, dismissing the opinions of others (passive aggression).</li> <li>Hostile aggression -- Aggression intended to harm another person, such as hitting/kicking/biting someone (active aggression). Threatening to beat up someone (nonverbal intimidation). Sending threatening messages through emails, phone calls, or social media, or making threats against someone's life, shouting, and swearing (verbal hostility). Breaking someone's computer, destroying someone's cell phone, or other forms of vandalism (destruction of property).</li> <li>Relational aggression -- A form of hostile aggression that does damage to another's peer relationships, as in social exclusion, gossiping or rumor spreading. Examples: Arguments within a team after a lose that lead to a verbal fight.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="drugsalcohol"></a>3.5 Drugs and alcohol To play a match under the influence of any drugs or performance enhancers is strictly prohibited, and may be punished with exclusion from the tournament. If an admin finds that a player is not capable of competing in the competition because of intoxication, the admin can exclude that person from the entire tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="betting"></a>3.6 Betting Betting on any match in the CS:GO tournament is strictly forbidden. <a name="addagreement"></a>3.7 Additional agreements Teams may be required to play any match on the stage. If so, teams will be notified at least 20 minutes prior to the start time of that match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="streaming"></a>3.8 Streaming, interviews and media <a name="broadcasting"></a>3.8.1 Broadcasting Frag-o-Matic reserves the right to broadcast any match or demo, teams may not refuse such broadcasts. All forms of client side game broadcasting are NOT allowed. Frag-o-Matic participants are not allowed to watch a local GOTV if a CS:GO server broadcasts a game. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchmedia"></a>3.8.2 Match media All match media (screenshots, demos, etc.) must be kept until the end of the event. Faking or manipulating match media is forbidden and will result in exclusion from the tournament. Match media should be named clearly based on what it is. It is not possible to file a protest to complain about bad match media naming. However if a tournament admin is hindered in their work because of bad match media naming, then a tournament admin will give a warning. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="screenshots"></a>3.8.3 Screenshots The admin can ask for screenshots of every game on any moment during the event. When he does this, the team leader has 15 minutes time to deliver the screenshot to the admin. A screenshot of the scoreboard at the end of each half must be taken. When this is not done by a team it can result in a lost match when one of the other teams complains about a score. An RCON status screenshot must be taken: <ul> <li>at the beginning of the match</li> <li>in case of a server/player change</li> <li>if a player reconnects</li> </ul> RCON status screenshots made with the help of programs like HLSW etc. are not sufficient. In order to take an RCON status you have to use the console command “rcon status” (don’t forget to enter your RCON password) and take a screenshot of that. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="playerchanges"></a>3.9 Player changes Teams are permitted to substitute players (only with another player not active in the CS:GO competition) during pauses and between rounds, if they have permission from the tournament admin. Consent for substitutions must be obtained from the tournament admins, and substitute players must be registered for that team in the tournament. You can make this clear to the admin by using the contact information in section ‘Admins and communication’. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="prizemoney"></a>3.10 Prize money When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="csgorules"></a> 4. Counter-Strike:Global Offensive rules <hr /> <a name="tournament"></a>4.1 Tournament structure and time schedule Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. On Saturday and Sunday, teams must be present at 10:00 (AM) and ready to start playing the rest of their scheduled matches. It can be the case that the tournament admins decide to start earlier or end later, but this will be communicated (to all team captains). An exact time schedule will be provided on our fom.be website for all teams to follow. Each match will have a start time on which the game needs to be started. The team(s) that are responsible where the start time has not been met will receive a forfeit for that match. Whether or not this rule will be applied, is the decision of a tournament admin. The schedule for the tournament may be subject to change at any time. Matches may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice. Games will not be rescheduled to an earlier time in the same day if either of the teams have not yet played a game on that day without the consent of both team captains. Where possible the tournament admins will notify any teams involved in a rescheduled game of the new match start time at least one hour before the new start time. In the event a match is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible. If there’s insufficient time to complete a match, the tournament admins may at any time declare one team as the winner, if that team holds a clear advantage in that match. It is the responsibility of the tournament admins to decide whether a team holds a clear advantage. This rule will only be used in the emergency when the remaining event time is a factor. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="penalties"></a>4.1.1 Penalties and forfeits during the time schedule If 1 or more teams are still playing a match in a previous stage or if 1 team is late and doesn’t start playing their match in the stage where they are; Teams are offered 30 minutes of grace time in both circumstances, after 30 minutes warnings are handed out: After 30 minutes that team, who’s still not playing their scheduled match, will receive a 1st warning from a tournament admin. A notice via our csgo channel on discord and if the team is present and found at their seat they’ll be warned in person as well. A second warning is given in the same manner 5 minutes after the first warning. A third and final warming is given in the same way 5 minutes after that. 5 minutes after the final warning the team who received 3 warnings will receive 1 game loss for their match in the next round. In case of a bo3 in the next round, a bo2 will be played with one win to the team that was on time. If after 15 minutes the team with 3 warnings and one loss in the next round is still not playing, they’ll receive a forfeit from an admin. In case of a bo1 (in the lower bracket for example) we won’t lose any more time and a forfeit will be forced. The forfeit is applied on our fom.be website and a notice is given on Discord in our csgo channel. The tournament admins will keep a record of the warnings and will communicate this to the compo desk. As mentioned in our general rulebook; Non-acceptable excuses for a delay: “We want to eat” isn’t a valid excuses for starting an argument at the compo desk. As a note, we ask that teams only take a maximum of 15 minute breaks in between games and matches to avoid any penalties. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compomaxteams"></a>4.1.2 Compo sign-up and max teams All compo sign-ups are done via our fom.be website. Some rules are already explained in our general rulebook. Any team that is not “full”, meaning the team doesn’t consist of minimum 5 players, will be removed from the compo sign-up one hour before the start of the competition. We allow a maximum 64 teams to register to our CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="structure"></a>4.1.3 Structure Our CS:GO tournament will use a poule system and 3 double elimination brackets (pro, semi-pro and fun). Each poule will consist out of 3-4 teams who will compete against each other to make it into the brackets. Each team within the poule needs to play against any other team within its poule. Following the poule stage, the 2 winners from each poule will advance to a pro bracket, the last 2 teams from each poule will advance to a semi-pro bracket and <s>other teams will proceed to the fun bracket</s>. Our compo structure will use the following setup for pro, semi-pro and fun: <ul> <li>Groupstage > BO1 (best of 1)</li> <li>Upper Bracket > BO3 (best of 3)</li> <li>Lower Bracket > BO1 (best of 1)</li> <li>Pro & semi-pro bracket: <ul> <li>Semi-final (Finals in lower bracket) > BO3 (best of 3)</li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> </li> <li><s>Fun bracket:</s> <ul> <li><s>Semi-final (Finals in lower bracket) > BO1 (best of 1)</s></li> </ul> </li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> When 2 teams have the same amount of points after the poules we will look at the following criteria in order: <ul> <li>The match between the 2 teams</li> <li>The won rounds total</li> <li>The lost rounds total</li> <li>Seeding</li> </ul> We can also look at other criteria if we feel that it's necessary (also cooperation). The admin is allowed to overrule these criteria. If there’s not enough data to validate a criteria the admin can chose to ignore it. A tournament admin can decide to change some matches from BO3 to BO1 or visa versa when needed. (For example: no time to play a BO3). <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="gamesetup"></a>4.1.4 Game setup Matches will be played 5on5. Playing with fewer than five players in any match is only allowed with permission from the tournament admins. Before a match starts, both teams must state that they are ready to start the match. The must do this by having one team member typing ‘ready’ in server chat. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated. Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug. You’ll need to use the following match setup to play every game: <ul> <li>2 teams join the server that is assigned to them on our fom website.</li> <li>The team captains can use the RCON password “godmode” to follow the next steps : <ul> <li>Don’t forget to do ‘cl_mute_enemy_team 0’</li> <li>Change the map to de_mirage (rcon changelevel de_mirage)</li> <li>Load the Frag-o-Matic config (rcon exec fom5on5.cfg)</li> <li>Start a knife round on de_mirage (optional). The winner of this knife round can decide who team A is. Start the map veto process (Veto is explained under ‘Veto system’’).</li> <li>After the Veto the team captain needs to change the map to the first map of Team A (in a BO3) or the single map that was chosen (in a BO1) (rcon changelevel ‘mapname’)</li> <li>Load the fom5on5.cfg again on this map. (rcon exec fom5on5.cfg)</li> <li>After this the teams do another knife round to decide which team will start on which side of the map. The winner of the knife round decides which side they want to start on and that team will also start the match. (rcon mp_restartgame 1)</li> </ul> </li> </ul> If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server can be paused at the end of the current round (see rule ‘Usage of pause’ function) by one of the teams. The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed. If a player/substitute doesn’t connect within that time, then the match is continued 4on5, or 4on4 if the opposing team agrees and the tournament admins are informed. There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="vetosystem"></a>4.1.5 Veto system Our veto process is the next step after playing a knife round, as described in ‘Game setup’. The map(s) chosen to be played in each BO1 and BO3 are done via elimination (i.e. veto). Where ‘team 1 = A’ and ‘team 2 = B’, with A being decided by the winner of the knife round. Teams can also decide who team A/B is without playing a knife round. The maps you don’t want to play as a team, should be the maps that you veto during this process. The veto process needs to be done in server chat. VETO rules best-of-1: ABABAB veto. The map pool exists out of 7 maps. 6 maps are vetoed during this process, 3 maps for each team. The remaining map is the map played in the best-of-1 match. VETO rules best-of-2: ABAB veto AB play. The map pool exists out of 7 maps. 4 maps are vetoed during this process, 2 maps for each team. Out of the 3 remaining maps, 1 team each gets to decide a map to play on. VETO rules best-of-3: A/B veto, A/B play and A/B veto. The map pool exists out of 7 maps. 4 maps are eliminated, and 3 maps are selected to play. Each team needs to veto a map, followed by each team choosing a map and again each team vetoing a map. The remaining map is the third map that needs to be played if both teams win a map. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compospecificrules"></a>4.1.6 Compo specific rules All matches in the group stage are played MR15. All matches in the brackets are played MR15 (meaning, 16 rounds won = game win). In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games are best of three (BO3) in the bracket, 3 maps are decided by veto. The grand final is a best of three (BO3) with map advantage! When in the brackets a game is tied an overtime needs to be played. The overtime will be played MR3 with 10.000$ start money. For the start of the overtime teams will stay on the side which they played the previous half on, during halftime sites will be swapped. Teams will continue to play overtimes until a winner has been found. We have our own special breed of bracket seeding. For more information please contact us in advance. This bracket seeding is law. Obey it. All CS:GO players can only use our ts.fom.lan (local) teamspeak for voice communication. Teams are only allowed to have 5 players + 1 coach in their teamspeak channel whilst in a competition match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="usageofpause"></a>4.1.7 Usage of pause Pauses may be taken for any reason. Teams are permitted 3 pauses per side in each match. Each pause having a maximum duration of 5 minutes, unless authorised by an admin to take a longer pause (in case of technical difficulties, for example). After a “pause”-event, an “unpause“-command needs to be done. Teams can’t unpause without the consent of the other team. Pauses may only be activated at the start of the next round during freeze time. So make sure you tell the other team before round end (in all-chat), that your team will take a pause in the next freeze time. Usage: Type the following commands in console, to activate and deactivate the pause event. Pause = rcon mp_pause_match Unpause = rcon mp_unpause_match Illegal usage: DON’T USE = sv_pause If a team does use sv_pause, they have to surrender 1 round. (by all team members typing “kill” in console) <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="demofiles"></a>4.1.8 Demo files GoTV demos must be active for each match to be recorded. It’s the responsibility of (both) team captains to ensure that GoTV is recording. If this isn’t the case, the tournament admins will be forced to make calls without a recording when a dispute occurs. It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A knife round is part of a match and should be recorded. At least one of the players must be able to upload the knife round on admin request. Protests regarding missing knife rounds are not valid. In general, defective or manipulated demos will be treated as missing demos. If the demo is incomplete, as decided by the admin, it also will be treated as missing demo. If a protest is opened for a match, all match media need to be kept until the end of the event. Demos can only be requested up to a maximum of 30 minutes after a match via the admin. A demo request must state which teams were playing, the name(s) of the map(s) the match(es) was/were played on, the time of the match(es) and the server IP address(es). If a player or a team illegally aborts the match, they lose their right to demand demos. Recording demos is recommended. Our servers will likely record demos for every match but these are only used when there is doubt about a decision the admin has to make. It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.2 Match procedure <a name="maplist"></a>4.2.1 Map list Only the following maps are allowed to be played on during the competition: <ul> <li>de_ancient</li> <li>de_anubis</li> <li>de_inferno</li> <li>de_mirage</li> <li>de_nuke</li> <li>de_overpass</li> <li>de_vertigo</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchrules"></a>4.2.2 Match rules <ul> <li>Diffusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.</li> <li>Throwing grenades/flash bangs/smokes across walls in maps is allowed.</li> <li>Boosting is not considered a bug.</li> <li>Buying and using multiple grenades is allowed but with a max of 2 flash bangs.</li> <li>Multiple grenades are allowed but max 2 flash bangs</li> <li>Bugs on the map must be checked before the match begins. Any protest after the match about map bugs will be ignored.</li> <li>If a player loses connection before the first kill, the match can be restarted. If this happens after the first kill, the server can be paused and have the disconnected player reconnect. Matches won’t be restarted due to disconnections.</li> <li>If you want a player change (sub) during the match, inform the opponent and the compo admins before the match begins!</li> <li>To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.</li> <li>Climbing with help of teammates is allowed in general.</li> <li>Throwing grenades inside walls is not allowed.</li> <li>Self-kills are strictly forbidden, unless an admin forces you to do this as a sanction for disobeying any rules.</li> <li>Bomb planting in a way it can’t be reached is forbidden.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="clientrules"></a>4.2.3 Client rules The admin is allowed to take over your computer before, during and after a game and have a look. Without the pc’s owner in question nearby, the person in question can appoint someone to stay with the admin to make sure no privacy issues are violated. Any trace evidence of cheats found on a player’s computer – even if such discovery took place outside of a game – can lead to exclusion from any competition. For NVIDIA graphics card users: The use of Ambient Occlusion is strictly forbidden. If you are caught using this setting, this will result in a direct loss of the match. Getting caught for a 2nd time will result in removal from the tournament. This setting can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings. The following commands are forbidden: <ul> <li>mat_hdr_enabled</li> </ul> The following startparameters are forbidden: <ul> <li>+mat_hdr_enabled 0/1</li> <li>+mat_hdr_leven 0/1/2</li> </ul> In your game client cfg-folder you’re only allowed to have config files. Pictures, demos, screenshots and zipped files are forbidden. All other configuration changes are allowed as long as they do not give an unfair edge or advantage comparable to cheating. The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary. Boosting through walls/ceilings/ground, sky walking, map swimming, floating and sharking are all forbidden. To throw grenades inside walls is not allowed. Above walls and roofs is allowed. To plant the bomb in a way that it cannot be reached is forbidden. Places that can be reached with help of a team mate are allowed as long as they are visible. Violating this rule will result in tournament administrators intervention. Changing graphic settings to irregular values can be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalscripts"></a>4.2.4 Illegal scripts In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts: <ul> <li>Stop Shoot scripts [Use or Awp scripts]</li> <li>Center view scripts</li> <li>Turn scripts [180° or similar]</li> <li>No Recoil scripts</li> <li>Burst fire scripts</li> <li>Rate changers (Lag scripts)</li> <li>FPS scripts</li> <li>Anti flash scripts or binding (snd_* bindings)</li> <li>Bunnyhop scripts</li> <li>Stop sound scripts</li> <li>Following Commands/CVars are forbidden</li> <li>+weapon_recoil_model 0 (Startparameter)</li> </ul> The following CVAR values must be used: <ul> <li>cl_bobcycle 0.98 (First Time->Warning)</li> </ul> If there are more than one player who used a wrong client setting, the match will be deleted. Exception: cl_bobcycle Using illegal scripts will be penalized if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized. The use of No-Flash and No-Recoil bindings/scripts in any and all forms will be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="customfiles"></a>4.2.5 Custom files The HUD can be changed as long as no information are deleted or falsified which are available in the standard HUD. If the HUD is changed it has to be readable. If an admin is hindered in his work due to an unreadable HUD, penalty points may be assigned. Protests or supports which adhere to this rule will not be admitted and are rejected directly. Apart from the HUD and the GUI no custom files are allowed. This also includes custom models, changed textures or sounds (volume, soundscapes) are forbidden. <a name="colordepth"></a>4.2.6 Color depth and external programs The usage of a color depth of 16bit is not allowed. The usage of external programs (ex. SweetFX, A3D,...) are not allowed to enhance vision. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalprograms"></a>4.2.7 Illegal programs Changing the game graphics or textures with the help of video card drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. NVidia SLI Display, Riva tuner Overlays) is illegal. Failure to comply with this rule will result in a punishment for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized. If you play with ambient occlusion, it will be punished as cheating!! Punishment will be given regardless of whether the script/binding is executed via external hardware or software. Also binding any snd_ command is forbidden. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="ingameoverlay"></a>4.2.8 In-game overlays All In-Game overlays – provided by the game itself – except the following are forbidden: <ul> <li>net_graph 0</li> <li>net_graph 1</li> <li>cl_showpos 1</li> <li>cl_showfps 1</li> <li>cl_showdemooverlay 1 / -1</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="techprobs"></a>4.2.9 Technical problems and disconnects If a disconnection occurs the game should automatically reconnect. When this doesn’t work, a tournament admin will decide what to do. The tournament admin will make a call in every possible scenario regarding the severity of the problem and how to deal with it. But, the following guidelines are in place in the event of a disconnect: <ul> <li>In the case where Frag-o-Matic is responsible for the disconnect, the round needs to be restored to the start of the round where the disconnection happened. I.e. follow the steps as described under “4.3.2 Server crash”.</li> <li>When a player is responsible for his own disconnect, the team with 4 players can decide to continue to play 4v5 or use a pause as described in “4.1.6 Usage of pause”.</li> <li>The disconnected player can then reconnect to the match. If that player fails to reconnect, then the match will continue 4v5.</li> <li>If another Frag-o-Matic participant is responsible for causing a problem, then the match needs to be paused and a tournament admin needs to be notified to make a call on what to do.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.3 CS:GO server <a name="serversettings"></a>4.3.1 Server settings Frag-o-Matic will supply hardware for all servers. All games related to the tournament must be played on these servers. All matches will be played using the latest version of CS:GO and the official Frag-o-Matic CS:GO server config. All matches have to be played on an official Frag-o-Matic CS:GO tournament server and on the provided server number (as listed on our fom.be website, in the csgo compo section). We’ll use a standard (ESL) 5v5 pro league tournament config on a 128 tickrate server: <ul> <li>Startmoney: 0</li> <li>Maxrounds: 30</li> <li>Roundtime: 1m 55s (1.92)</li> <li>Freezetime: 12 seconds</li> <li>C4timer: 40 seconds</li> <li>Pause: 1x 5minutes per half each map.</li> <li>Overtime: MR3 - .000 startmoney</li> <li>Time during half time: 13 seconds</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="servercrash"></a>4.3.2 Server crash In the event of a server crash, after notifying a tournament admin and having them restart the the server, both teams have to re-join the same server and use the following command: <ul> <li>rcon mp_backup_restore_list_files</li> </ul> This will show you the backup files before the server crashed. 1 team captain then executes the correct file by using the following command: <ul> <li>rcon mp_backup_restore_load_file</li> </ul> Example: rcon mp_backup_restore_load_file backup_round12.txt All previous settings (score, money, armor, weapons,...) are then reset to the round before the server crashed and the match is set to paused. To continue the match, use the unpause command: <ul> <li>rcon mp_unpause_match</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="serverlag"></a>4.3.3 Server (var) lag Teams are given the time to play a warm-up match on their server before every compo match if they wish to do so. It’s not allowed to switch to another server once the compo match has been started. Test the server before the match starts. Any server problems should be reported to a tournament admin by going to the compo desk after sending an email with the information below. In the event that you experience any lag during or before a match, please note the time(s) and contact us via Discord or the Compo Desk. We'll escalate this information and, if possible, provide a solution for upcoming matches. The statement or report of (possible) lag in a match is a not valid argument in a protest. However, sending us the data above will give your team the time necessary to avoid any possible forfeits when you notify us at the compo desk after sending your email. Failure in providing us this data will not allow your team to deviate from our time schedule. We strive to provide all our servers lag free. We would like to thank you in helping us improve our servers. <a name="serverplugins"></a>4.3.4 Server plugins No extra plugins will be installed on our CS:GO servers. <a name="rconusage"></a>4.3.5 RCON usage RCON is only allowed as described in “4.1.2 Game setup”. Usage of RCON outside the game setup is penalised by receiving an instant forfeit for the team using any other RCON commands. We monitor all servers and RCON logs and will use this as evidence to hand out a match forfeit to the team using RCON outside of the game setup rules. <a name="rconusage"></a>4.3.6 Warmup servers Subject to availability, we will provide warmup servers. The settings will mirror our war servers as close as possible, but won’t be managed by the csgo team. Participants in our competition are allowed to use our warmup servers as such, to warm up, practice nade throws, practice aim,etc… We will not guarantee availability of those servers, since they will depend on the overall capacity. If warmup servers are available, they cannot ever be used for playing matches. If a match has been played on one of those servers though, the end-scores will still count. It is the responsibility of both teams the correct (assigned) server is joined. At any time, we can convert one of those servers to an official war server (In cases of need). It will at that point no longer show up as a warmup server. <a name="copyright"></a>5. Copyright Notice Copyright © 2005-2022 by E-EVENTS VZW All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher, addressed at <a href="mailto:csgo@fom.be">csgo@fom.be</a> </li> </ul>
 showsponsor(false)
 sponsorcontent
 showfiles(false)
 filescontent
 prizescontent<h1> First Place </h1> <ul> <li> <h3>525 €</h3> </li> </ul> <h1>Second Place</h1> <ul> <li> <h3>315 €</h3> </li> </ul> <h1>Third Place</h1> <ul> <li> <h3>210 €</h3> </li> </ul>
 precompo(false)
 donations0
 donationAmount0
 scheduleregistration closes at 21! please make sure all games are played on time! poules will be made and will be playable. saturday 10am we will start with the brackets semi final will be at 10am on sunday with afterwards the grand final Have fun and Good luck!
 faq
 sponsorUrl
 sponsorImg(null)
 sortTimeLabel0
 TeamA(array)
 id10265
 nameBASTARDS.AF9K
 leaderId5352
 compoId367
 pouleId1452
 notes
 withdrew(false)
 TeamB(array)
 id10299
 nameVlamski
 leaderId10144
 compoId367
 pouleId1452
 notes
 withdrew(false)
 AdminEdit(array)
 id(null)
 facebook_id(null)
 username(null)
 new_username(null)
 nickname(null)
 password(null)
 firstname(null)
 lastname(null)
 active(null)
 validationCode(null)
 mailValidationCode(null)
 group_id(null)
 created(null)
 modified(null)
 last_login(null)
 street(null)
 nr(null)
 bus(null)
 zip(null)
 city(null)
 country(null)
 phone(null)
 gsm(null)
 gender(null)
 birthdate(null)
 clanId(null)
 clantrust(null)
 clanjoinId(null)
 hwbudget(null)
 education(null)
 profession(null)
 hoursaweek(null)
 language(null)
 oldId(null)
 receive_newsletter(null)
 imageUrl(null)
 slug(null)
 fb_link(null)
 fb_location(null)
 CPU(null)
 MOBO(null)
 GFX(null)
 RAM(null)
 steamName(null)
 steamId(null)
 originName(null)
 lolSummonerName(null)
 Other(null)
 comment(null)
 seat_id(null)
 msg_notifications(null)
 mouseHand(null)
 deviceId(null)
 alternative_login(null)
 4(array)
 War(array)
 id27960
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10265
 teamB10336
 scoreAByA4
 scoreBByA16
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA4
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1452
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 06:30:42
 Compo(array)
 id367
 nameGRAND - CS:GO
 steamGameId(null)
 nrPlayersTeam5
 maxTeams64
 compoTypeId0
 nrPoules3
 nrWinnersPoule4
 compoStateId5
 eventId46
 roundDE2
 addSecondaryFinal(false)
 adminId8749
 adminId2(null)
 bannerUrl(null)
 description<h1>password to the servers: war</h1> 
 tagId31
 allowDrawInPoule1
 nrLosersToBrackets0
 pauzed0
 rulebookFrag-o-Matic 24.0 Rulebook Counter-Strike:Global Offensive (CS:GO) Introduction This is the official rulebook for the Frag-o-Matic 24.1 CS:GO competition, that will take place from the 1st until the 3rd of September 2023. These rules apply to the players throughout all stages of CS:GO competition. Failure to adhere to these rules may be penalized as outlined. It should be noted that the tournament administrators have the final word, and have the power to decide on any circumstances that are not outlined by this document, and in extreme cases may overrule the rulebook in order to preserve fair play and sportsmanship. Frag-o-Matic reserves the right to change these rules at any time. The CS:GO admin team wishes you good luck in the tournament and hopes that you have an enjoyable competition. We’ll do our utmost best to make it fair, fun and exciting for everyone involved. <a name="navigation"></a>Table of contents <ol> <li><a href="#admin">Admins and communication</a></li> <li><a href="#compo">Compo overview</a> <ol> <li><a href="#participants">Participants</a></li> <li><a href="#teamsheets">Team sheets</a></li> <li><a href="#teamnames">Team names</a></li> <li><a href="#teammanager">Team manager / coach</a></li> <li><a href="#teamcaptain">Team captain</a></li> <li><a href="#players">Players</a> <ol> <li><a href="#grstandard">Grooming standards</a></li> </ol> </li> <li><a href="#cheating">Cheating</a> <ol> <li><a href="#forbiditems">Forbidden items</a></li> </ol> </li> <li><a href="#match">Match protests and forfeit</a> <ol> <li><a href="#definitions">Definition</a></li> <li><a href="#matchprotest">Match protest rules</a></li> <li><a href="#forfeitrules">Forfeit rules</a></li> </ol> </li> <li><a href="#seeding">Seeding</a></li> </ol> </li> <li><a href="#general">General</a> <ol> <li><a href="#generalrules">General rules</a></li> <li><a href="#sanctions">Sanctions and disputes</a></li> <li><a href="#confidentiality">Confidentiality</a></li> <li><a href="#coc">Code of conduct</a></li> <li><a href="#drugsalcohol">Drugs and alcohol</a></li> <li><a href="#betting">Betting</a></li> <li><a href="#addagreement">Additional agreements</a></li> <li><a href="#streaming">Streaming, interviews and media</a> <ol> <li><a href="#broadcasting">Broadcasting</a></li> <li><a href="#matchmedia">Match media</a></li> <li><a href="#screenshots">Screenshots</a></li> </ol> </li> <li><a href="#playerchanges">Player changes</a></li> <li><a href="#prizemoney">Prize money</a></li> </ol> </li> <li><a href="#csgorules">Counter-Strike:Global Offensive rules</a> <ol> <li><a href="#tournament">Tournament structure and time schedule</a> <ol> <li><a href="#penalties">Penalties and forfeits during the time schedule</a></li> <li><a href="#compomaxteams">Compo sign-up and max teams</a></li> <li><a href="#structure">Structure</a></li> <li><a href="#gamesetup">Game setup</a></li> <li><a href="#vetosystem">Veto system</a></li> <li><a href="#compospecificrules">Compo specific rules</a></li> <li><a href="#usageofpause">Usage of pause</a></li> <li><a href="#demofiles">Demo files</a></li> </ol> </li> <li><a href="#matchprocedure">Match procedure</a> <ol> <li><a href="#maplist">Map list</a></li> <li><a href="#matchrules">Match rules</a></li> <li><a href="#clientrules">Client rules</a></li> <li><a href="#illegalscripts">Illegal scripts</a></li> <li><a href="#customfiles">Custom files</a></li> <li><a href="#colordepth">Color depth and external programs</a></li> <li><a href="#illegalprograms">Illegal programs</a></li> <li><a href="#ingameoverlay">In-game overlays</a></li> <li><a href="#techprobs">Technical problems and disconnects</a></li> </ol> </li> <li><a href="#csgoserver">CS:GO server</a> <ol> <li><a href="#serversettings">Server settings</a></li> <li><a href="#servercrash">Server crash</a></li> <li><a href="#serverlag">Server (var) lag</a></li> <li><a href="#serverplugins">Server plugins</a></li> <li><a href="#rconusage">RCON usage</a></li> <li><a href="#warmupservers">Warmup servers</a></li> </ol> </li> </ol> </li> <li><a href="#copyright">Copyright Notice</a></li> </ol> <a name="admin"></a>1. Admins and communication <hr /> Communication before the LAN: <ul> <li>General contact > <a href="mailto:csgo@fom.be">csgo@fom.be</a></li> </ul> Please email us any feedback before and after the LAN event. CS:GO admin team: <ul> <li>Dragon <ul> <li>Steam: https://steamcommunity.com/profiles/76561198244170010/</li> <li>Discord: dragon (main communication line)</li> </ul> </li> </ul> Communication during the LAN: The communication during the LAN will be through Steam, Discord or at the Compo Desk. We will be available as much as possible in the <a href="https://discord.gg/URX6v82Wmp" target="_blank">#csgo channel</a>. We will use this as a second channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #csgo channel. Discord will be our main communication channel. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compo"></a>2. Compo overview <hr /> <a name="participants"></a> 2.1 Participants Due to lack of time, we have a tight schedule. Therefore we can make the decision to force teams to only participate in 1 grand compo! We will contact the teams who are signed in for 2 grand compo’s at the moment and they will need to make a choice. When a team refuses, we will remove them from the competition to make room for other teams. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamsheets"></a> 2.2 Team sheets As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops. A rule violation by any player in a team may lead the tournament admins to sanction the entire team, even if the rest of the team was not aware of the violation. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamnames"></a> 2.3 Team names <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teammanager"></a> 2.4 Team manager / coach The team manager does not have any responsibilities. The team manager is eligible to play for his team in matches, providing he’s indicated as a “Player” on the team in the team sheet. The communication with the team will not go via the team manager, all communication will go via the team captain! Spectators are not allowed on our servers. Only tournament admins may be in spectator mode during a match. The only exception is: coaches are allowed to spectate a match using the coach's command, only if the tournament admin is notified, and thus to spectate their team only. They are obligated to use the “coach t” or “coach ct” command before the match start and aren’t allowed to join after a match has been started. If noticed that the coach is abusing this rule, the team will get punished for it (e.g. round loss, side loss or match loss). During a match, the coach may only communicate with the players during freeze-time, warm up, half-time, or during one of the 4 timeouts. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamcaptain"></a> 2.5 Team captain We consider the one who registered the team into the compo on the Frag-o-Matic website as captain! The clan leader or team captain is responsible for his team and all the players in that team. It is recommended that the team captain is fluent in English or Dutch, as he will be required to communicate with the tournament admins. The team captain must read and understand the rulebook. The team captain is responsible for ensuring his team and players adhere to the rules. Ignorance of the rules is not an excuse for rule violations. The team captain may choose at any time to nominate another player in or manager of his team as team captain for any reason. Such nominations must be reported by the team captain, either in person or in writing, to the admins before the game starts. All official communication between a competing team and the tournament admins must be conducted by the team captain. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="players"></a> 2.6 Players All players must read and understand the CSGO rulebook. Any player in violation of a rule, will be sanctioned as described in this rulebook. Each team must have five players on the match server at the match start time as indicated by the schedule, unless permission has been granted by the tournament admins to play with less than five players. Only players registered for a team in the tournament may play for that team unless otherwise discussed with the tournament admin. All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins. Players registered for a team in the tournament may not play for any other team in the same tournament. Each player has to use their nickname that is similar to the nickname he/she has entered on their fom.be account. All players for a team must be clearly identifiable in-game with a uniform tag for that team and a separate, noticeably different nickname for each player. Players may not significantly change their nickname during the tournament. Any nickname they use during the tournament must always obviously visibly correspond to their original nickname. You are not allowed to change your nickname in-game. If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning. 3 warnings are equal to a forfeit in 1 match. Player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate. Make sure your steam account is linked with your fom.be account corresponding to your nickname. Players are strictly prohibited from using any other person’s steam account for any reason whatsoever during the CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="grstandard"></a> 2.6.1 Grooming standards People participating in the CS:GO tournament are expected to normal grooming standards. You may be asked to take action if you or your clothing have a look or odor that’s offensive to other players. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="cheating"></a> 2.7 Cheating During Frag-o-Matic we won’t investigate cheaters from an external event. When we discover someone cheating during our LAN, that player and his team will be banned from the compo and the player will be also banned for the next Frag-o-Matic edition. Furthermore we will investigate reports of players cheating during other tournaments until 2 weeks before the LAN. When a player is discovered cheating during another tournament/platform 12 months before the event occurs, then that player will not be allowed to play on that edition of Frag-o-Matic within the CS:GO competition and the edition after that. If one of the following rules apply, then that player will not be allowed to compete in our tournament: Caught cheating within a tournament/platform 12 months before the start date of our event. There needs to be enough evidence for that player, that he/she was cheating and the tournament admins will judge if the evidence is valid OR if he/she was caught cheating on the following platforms: <ul> <li><a href="ts3server://ts.fom.lan">ts.fom.lan</a> - CS:GO admin channel</li> <li>Discord: <a href="https://discord.gg/MbPY2ge">https://discord.gg/MbPY2ge</a> <ul> <li>Teams are only allowed to use a uniform team name for their team.</li> <li>Teams may not change their team name during the tournament.</li> <li>Teams may not change their team in-game tag during the tournament, unless none was set.</li> <li>Duplicating team names of other teams is not allowed.</li> <li>Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.</li> <li>Team names are not allowed to be offensive.</li> <li>Please make sure your team name is filled in on your fom.be profile.</li> </ul> <ul> <li>Faceit</li> <li>Esl</li> <li>Valve (vac ban for any Counter strike: Global Offensive game)</li> <li>ESEA</li> <li>Cevo</li> </ul> </li> <li>When a player is caught selling or buying cheats. In any case the admin will have the final decision. This means that the admin will review the evidence and make the final call. If a player shows the intention of coming to our tournament to cheat and we’re provided evidence of this. Everyone from the community may send evidence to csgo@fom.be, when they suspect someone participating at Frag-o-Matic of cheating. All forms of cheating in matches are forbidden, and will result in an overall forfeit in the tournament. Possibilities for cheating in Counter-Strike:Global Offensive are, for example; all kinds of multi-hacks, wallhack, aimbot, colored models, no-recoil, no-smoke, no-flash and sound changes. All hardware or software that has an influence on the game in such a way that the essence of the game is affected are banned from this tournament. Any use of this kind of hardware will result in a disqualification of the tournament as it will be recognized as cheating. When proven that a player is not cooperating in his own ban research or is lying on purpose. He will get banned for 1 edition. You can find our banlist at http://www.fom.be/contents/view/cs-go-banlist The mentioned people in our ban list are not allowed in the CS:GO tournaments at Frag-O-Matic until the edition that’s stated there. When these people compete under a false name nonetheless or try to circumvent the rules then they will receive an extended or permanent ban. Here are some of the other examples of ways to gain advantages, this list may not be the full list but if players are unsure of certain things, they should seek to ask the tournament admins first: Flash Bang, Smoke Grenade, and Hand Grenade Bugs - it is illegal to use any flash bang, smoke grenade, or hand grenade bugs, regardless of intent. Silent Bomb Plants - ALL bomb plants must be done in a position where your opponents can hear you. There should be no rotation in players to gain money advantages throughout a match. The bomb must be planted on solid surfaces on the map, ie where an opponent can defuse from, so not up in the air or floating. Illegal Bomb Defuses - No player can defuse a bomb through any other solid object on the map, it has to be done in clear view. It is also forbidden to try to intentionally distort your hitboxes during a defuse situation to prevent an opponent from killing you in game. Walking/Boosting through walls - No player should walk, boost through walls or roofs. To do so will see your team penalized for that round. Map Exploits - Boosts that include the use of clipping are strictly forbidden. The term “Clipping” defines that when a player is boosted can see through certain parts of the map (ie over/under walls, or through solid objects on the map). If any player or team feels unsure on a new advantage they have found through their practice sessions, they are welcome to show this specific spot to the tournament team to review. Any player or team that does this will be treated to the strictest confidence as not to jeopardize your strategic advantage, however we can rule on whether it is a legal move. We strongly advise teams to give us plenty of time ahead of an event so we can review it in good time and make good judgement on it. The game admins may inspect your machine at any time throughout the event to inspect for cheats or hacks within your game files, steam cloud and anywhere on your PC or memory sticks. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="forbiditems"></a>2.7.1 Forbidden items During the lan, to prevent cheating by using external devices or items, the following items are forbidden: <ul> <li>Smartwatches; Having or carrying a smartwatch during the event, when competing in the CS:GO competition, that player will immediately be disqualified from the competition.</li> <li>Alienware Wireless Headset AW988; Visual representation of audio isn’t allowed.</li> <li>AR (augmented reality) glasses</li> <li>Hardware from the brand “Bloody” (these are mice that come with software that reduces recoil on weapons)</li> </ul> Any other electronic devices (like smartphones) that are used during a match will be considered suspicious and we’ll ask that they’re not used. If, during a match, the suspicious device is still in use; the team of the player using the device will receive a warning. After 3 warnings the team will receive a disqualification from the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="match"></a>2.8 Match protests and forfeit <a name="definitions"></a> 2.8.1 Definition A protest is a raised issue for problems that affect the match outcome; a protest may even be filed during a match for things like incorrect server settings and other related issues. A protest is the official communication between a team captain and a tournament admin. A forfeit is a lose or surrender. <a name="matchprotest"></a> 2.8.2 Match protest rules Participants are only allowed to issue a match protest before the beginning of their next match. The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “they are cheaters” will not be enough. Insults and flaming are strictly prohibited in a protest, and may result in the protest being ruled against the insulting party. <a name="forfeitrules"></a> 2.8.3 Forfeit rules A forfeit can be called for a single match or the entire competition from a competing team for their team. Only the team captain can raise a forfeit for their team. A forfeit can also be raised by an admin as a penalty for wrongdoing. For example, in most cases where a competing team doesn’t follow the time schedule. The tournament admins can always force a forfeit. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="seeding"></a>2.9 Seeding Seeding is done through an objective outlook towards data provided by all participants for every event. Every participant is required to provide us their main steam account, ESEA and/or CEVO profile, FACEit level and previous wins/achievements. The supplied data is only kept and used for one event to calculate an individual “score” based on reached rank, played time, csgo hours and historical performance/achievements from Frag-o-Matic or other tournaments. The team sum of 5 individual scores will show an objective score where the higher the score, the higher the team seeding. The tournament admins won’t seed teams higher based on any subjective opinions. If no statistical data was provided for all 5 team member, than that team will be seeded beyond top 16. <a name="general"></a>3. General <hr /> <a name="generalrules"></a> 3.1 General rules Frag-o-Matic Counter strike:Global Offensive (CS:GO) 5v5 tournament is a local area network (LAN) tournament. By competing in this tournament, teams and players accept these rules in full. Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation. In the beginning of the LAN the team captains can sit together with the admin to discuss the rules and to make adjustments if needed. The decisions are made by the admin. If you have any issues with the rules, you can explain this by sending an email to <a href="mailto:csgo@fom.be">csgo@fom.be</a> up to one week before the start of the event. Clarification of any point in the rules is available from the tournament admins at any time during the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="sanctions"></a>3.2 Sanctions and disputes Sanctions and disputes will be resolved by the main tournament admin. The admin’s decision on any sanction or dispute is final. Abusive behavior towards the Frag-o-Matic staff, tournament admins or opponents at any time during the tournament is unacceptable and will be punished with warnings. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="confidentiality"></a>3.3 Confidentiality The content of protests, support communication, discussions or any other correspondence with tournament officials and administrators are considered as strictly confidential. The publication of such material is prohibited. If the contents has been shared without consent then this could lead to a team’s disqualification. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="coc"></a>3.4 Code of conduct Any form of aggression<a href="#coc_aggression">*</a> (both verbally and physically) will not be tolerated. Any and all physical aggression will be sanctioned with an immediate disqualification by that person or team performing the physical act (both actioned and reactioned). Any verbal aggression will be sanctioned by a time-out for that person or team. A time-out is either set in time (hours/day) or in amount of matches when a player or team is not allowed to participate in the CS:GO competition. Any situation that is about to escalate should be dealt with in a calm and diplomatic manner. An audience with any Frag-o-Matic crew member (CS:GO admin or Frag-o-Matic team leaders) can always be called for at any time during the event. Keep in mind that this audience can not be used to waste time or get a time advantage. At any point, the CS:GO tournament admins can decide to continue with the competition with or without consent from either players or other Frag-o-Matic staff. In the event when a single player or more are accused of cheating, the event will continue nonetheless. Evidence will be presented to the tournament admins and a call will be made at a later stage of the event. This rule is set to not cause any delays and have the situation under control. Any player(s) or team(s) ignoring this rule will receive a forfeit. Any player or team ignoring a CS:GO admin will be sanctioned with a warning. 3 warnings are equal to a forfeit of 1 match. <a name="coc_aggression"></a>*A form of aggression is described as: <ul> <li>Instrumental aggression -- Aggression aimed at obtaining an object, privilege or space with no deliberate intent to harm another person. Typical of participants wanting to get ahead of the competition with lies, anger, bullying, criticizing other people behind their backs, leaving others out of a group or otherwise ostracizing them, turning people against each other, dismissing the opinions of others (passive aggression).</li> <li>Hostile aggression -- Aggression intended to harm another person, such as hitting/kicking/biting someone (active aggression). Threatening to beat up someone (nonverbal intimidation). Sending threatening messages through emails, phone calls, or social media, or making threats against someone's life, shouting, and swearing (verbal hostility). Breaking someone's computer, destroying someone's cell phone, or other forms of vandalism (destruction of property).</li> <li>Relational aggression -- A form of hostile aggression that does damage to another's peer relationships, as in social exclusion, gossiping or rumor spreading. Examples: Arguments within a team after a lose that lead to a verbal fight.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="drugsalcohol"></a>3.5 Drugs and alcohol To play a match under the influence of any drugs or performance enhancers is strictly prohibited, and may be punished with exclusion from the tournament. If an admin finds that a player is not capable of competing in the competition because of intoxication, the admin can exclude that person from the entire tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="betting"></a>3.6 Betting Betting on any match in the CS:GO tournament is strictly forbidden. <a name="addagreement"></a>3.7 Additional agreements Teams may be required to play any match on the stage. If so, teams will be notified at least 20 minutes prior to the start time of that match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="streaming"></a>3.8 Streaming, interviews and media <a name="broadcasting"></a>3.8.1 Broadcasting Frag-o-Matic reserves the right to broadcast any match or demo, teams may not refuse such broadcasts. All forms of client side game broadcasting are NOT allowed. Frag-o-Matic participants are not allowed to watch a local GOTV if a CS:GO server broadcasts a game. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchmedia"></a>3.8.2 Match media All match media (screenshots, demos, etc.) must be kept until the end of the event. Faking or manipulating match media is forbidden and will result in exclusion from the tournament. Match media should be named clearly based on what it is. It is not possible to file a protest to complain about bad match media naming. However if a tournament admin is hindered in their work because of bad match media naming, then a tournament admin will give a warning. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="screenshots"></a>3.8.3 Screenshots The admin can ask for screenshots of every game on any moment during the event. When he does this, the team leader has 15 minutes time to deliver the screenshot to the admin. A screenshot of the scoreboard at the end of each half must be taken. When this is not done by a team it can result in a lost match when one of the other teams complains about a score. An RCON status screenshot must be taken: <ul> <li>at the beginning of the match</li> <li>in case of a server/player change</li> <li>if a player reconnects</li> </ul> RCON status screenshots made with the help of programs like HLSW etc. are not sufficient. In order to take an RCON status you have to use the console command “rcon status” (don’t forget to enter your RCON password) and take a screenshot of that. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="playerchanges"></a>3.9 Player changes Teams are permitted to substitute players (only with another player not active in the CS:GO competition) during pauses and between rounds, if they have permission from the tournament admin. Consent for substitutions must be obtained from the tournament admins, and substitute players must be registered for that team in the tournament. You can make this clear to the admin by using the contact information in section ‘Admins and communication’. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="prizemoney"></a>3.10 Prize money When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="csgorules"></a> 4. Counter-Strike:Global Offensive rules <hr /> <a name="tournament"></a>4.1 Tournament structure and time schedule Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. On Saturday and Sunday, teams must be present at 10:00 (AM) and ready to start playing the rest of their scheduled matches. It can be the case that the tournament admins decide to start earlier or end later, but this will be communicated (to all team captains). An exact time schedule will be provided on our fom.be website for all teams to follow. Each match will have a start time on which the game needs to be started. The team(s) that are responsible where the start time has not been met will receive a forfeit for that match. Whether or not this rule will be applied, is the decision of a tournament admin. The schedule for the tournament may be subject to change at any time. Matches may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice. Games will not be rescheduled to an earlier time in the same day if either of the teams have not yet played a game on that day without the consent of both team captains. Where possible the tournament admins will notify any teams involved in a rescheduled game of the new match start time at least one hour before the new start time. In the event a match is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible. If there’s insufficient time to complete a match, the tournament admins may at any time declare one team as the winner, if that team holds a clear advantage in that match. It is the responsibility of the tournament admins to decide whether a team holds a clear advantage. This rule will only be used in the emergency when the remaining event time is a factor. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="penalties"></a>4.1.1 Penalties and forfeits during the time schedule If 1 or more teams are still playing a match in a previous stage or if 1 team is late and doesn’t start playing their match in the stage where they are; Teams are offered 30 minutes of grace time in both circumstances, after 30 minutes warnings are handed out: After 30 minutes that team, who’s still not playing their scheduled match, will receive a 1st warning from a tournament admin. A notice via our csgo channel on discord and if the team is present and found at their seat they’ll be warned in person as well. A second warning is given in the same manner 5 minutes after the first warning. A third and final warming is given in the same way 5 minutes after that. 5 minutes after the final warning the team who received 3 warnings will receive 1 game loss for their match in the next round. In case of a bo3 in the next round, a bo2 will be played with one win to the team that was on time. If after 15 minutes the team with 3 warnings and one loss in the next round is still not playing, they’ll receive a forfeit from an admin. In case of a bo1 (in the lower bracket for example) we won’t lose any more time and a forfeit will be forced. The forfeit is applied on our fom.be website and a notice is given on Discord in our csgo channel. The tournament admins will keep a record of the warnings and will communicate this to the compo desk. As mentioned in our general rulebook; Non-acceptable excuses for a delay: “We want to eat” isn’t a valid excuses for starting an argument at the compo desk. As a note, we ask that teams only take a maximum of 15 minute breaks in between games and matches to avoid any penalties. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compomaxteams"></a>4.1.2 Compo sign-up and max teams All compo sign-ups are done via our fom.be website. Some rules are already explained in our general rulebook. Any team that is not “full”, meaning the team doesn’t consist of minimum 5 players, will be removed from the compo sign-up one hour before the start of the competition. We allow a maximum 64 teams to register to our CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="structure"></a>4.1.3 Structure Our CS:GO tournament will use a poule system and 3 double elimination brackets (pro, semi-pro and fun). Each poule will consist out of 3-4 teams who will compete against each other to make it into the brackets. Each team within the poule needs to play against any other team within its poule. Following the poule stage, the 2 winners from each poule will advance to a pro bracket, the last 2 teams from each poule will advance to a semi-pro bracket and <s>other teams will proceed to the fun bracket</s>. Our compo structure will use the following setup for pro, semi-pro and fun: <ul> <li>Groupstage > BO1 (best of 1)</li> <li>Upper Bracket > BO3 (best of 3)</li> <li>Lower Bracket > BO1 (best of 1)</li> <li>Pro & semi-pro bracket: <ul> <li>Semi-final (Finals in lower bracket) > BO3 (best of 3)</li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> </li> <li><s>Fun bracket:</s> <ul> <li><s>Semi-final (Finals in lower bracket) > BO1 (best of 1)</s></li> </ul> </li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> When 2 teams have the same amount of points after the poules we will look at the following criteria in order: <ul> <li>The match between the 2 teams</li> <li>The won rounds total</li> <li>The lost rounds total</li> <li>Seeding</li> </ul> We can also look at other criteria if we feel that it's necessary (also cooperation). The admin is allowed to overrule these criteria. If there’s not enough data to validate a criteria the admin can chose to ignore it. A tournament admin can decide to change some matches from BO3 to BO1 or visa versa when needed. (For example: no time to play a BO3). <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="gamesetup"></a>4.1.4 Game setup Matches will be played 5on5. Playing with fewer than five players in any match is only allowed with permission from the tournament admins. Before a match starts, both teams must state that they are ready to start the match. The must do this by having one team member typing ‘ready’ in server chat. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated. Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug. You’ll need to use the following match setup to play every game: <ul> <li>2 teams join the server that is assigned to them on our fom website.</li> <li>The team captains can use the RCON password “godmode” to follow the next steps : <ul> <li>Don’t forget to do ‘cl_mute_enemy_team 0’</li> <li>Change the map to de_mirage (rcon changelevel de_mirage)</li> <li>Load the Frag-o-Matic config (rcon exec fom5on5.cfg)</li> <li>Start a knife round on de_mirage (optional). The winner of this knife round can decide who team A is. Start the map veto process (Veto is explained under ‘Veto system’’).</li> <li>After the Veto the team captain needs to change the map to the first map of Team A (in a BO3) or the single map that was chosen (in a BO1) (rcon changelevel ‘mapname’)</li> <li>Load the fom5on5.cfg again on this map. (rcon exec fom5on5.cfg)</li> <li>After this the teams do another knife round to decide which team will start on which side of the map. The winner of the knife round decides which side they want to start on and that team will also start the match. (rcon mp_restartgame 1)</li> </ul> </li> </ul> If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server can be paused at the end of the current round (see rule ‘Usage of pause’ function) by one of the teams. The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed. If a player/substitute doesn’t connect within that time, then the match is continued 4on5, or 4on4 if the opposing team agrees and the tournament admins are informed. There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="vetosystem"></a>4.1.5 Veto system Our veto process is the next step after playing a knife round, as described in ‘Game setup’. The map(s) chosen to be played in each BO1 and BO3 are done via elimination (i.e. veto). Where ‘team 1 = A’ and ‘team 2 = B’, with A being decided by the winner of the knife round. Teams can also decide who team A/B is without playing a knife round. The maps you don’t want to play as a team, should be the maps that you veto during this process. The veto process needs to be done in server chat. VETO rules best-of-1: ABABAB veto. The map pool exists out of 7 maps. 6 maps are vetoed during this process, 3 maps for each team. The remaining map is the map played in the best-of-1 match. VETO rules best-of-2: ABAB veto AB play. The map pool exists out of 7 maps. 4 maps are vetoed during this process, 2 maps for each team. Out of the 3 remaining maps, 1 team each gets to decide a map to play on. VETO rules best-of-3: A/B veto, A/B play and A/B veto. The map pool exists out of 7 maps. 4 maps are eliminated, and 3 maps are selected to play. Each team needs to veto a map, followed by each team choosing a map and again each team vetoing a map. The remaining map is the third map that needs to be played if both teams win a map. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compospecificrules"></a>4.1.6 Compo specific rules All matches in the group stage are played MR15. All matches in the brackets are played MR15 (meaning, 16 rounds won = game win). In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games are best of three (BO3) in the bracket, 3 maps are decided by veto. The grand final is a best of three (BO3) with map advantage! When in the brackets a game is tied an overtime needs to be played. The overtime will be played MR3 with 10.000$ start money. For the start of the overtime teams will stay on the side which they played the previous half on, during halftime sites will be swapped. Teams will continue to play overtimes until a winner has been found. We have our own special breed of bracket seeding. For more information please contact us in advance. This bracket seeding is law. Obey it. All CS:GO players can only use our ts.fom.lan (local) teamspeak for voice communication. Teams are only allowed to have 5 players + 1 coach in their teamspeak channel whilst in a competition match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="usageofpause"></a>4.1.7 Usage of pause Pauses may be taken for any reason. Teams are permitted 3 pauses per side in each match. Each pause having a maximum duration of 5 minutes, unless authorised by an admin to take a longer pause (in case of technical difficulties, for example). After a “pause”-event, an “unpause“-command needs to be done. Teams can’t unpause without the consent of the other team. Pauses may only be activated at the start of the next round during freeze time. So make sure you tell the other team before round end (in all-chat), that your team will take a pause in the next freeze time. Usage: Type the following commands in console, to activate and deactivate the pause event. Pause = rcon mp_pause_match Unpause = rcon mp_unpause_match Illegal usage: DON’T USE = sv_pause If a team does use sv_pause, they have to surrender 1 round. (by all team members typing “kill” in console) <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="demofiles"></a>4.1.8 Demo files GoTV demos must be active for each match to be recorded. It’s the responsibility of (both) team captains to ensure that GoTV is recording. If this isn’t the case, the tournament admins will be forced to make calls without a recording when a dispute occurs. It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A knife round is part of a match and should be recorded. At least one of the players must be able to upload the knife round on admin request. Protests regarding missing knife rounds are not valid. In general, defective or manipulated demos will be treated as missing demos. If the demo is incomplete, as decided by the admin, it also will be treated as missing demo. If a protest is opened for a match, all match media need to be kept until the end of the event. Demos can only be requested up to a maximum of 30 minutes after a match via the admin. A demo request must state which teams were playing, the name(s) of the map(s) the match(es) was/were played on, the time of the match(es) and the server IP address(es). If a player or a team illegally aborts the match, they lose their right to demand demos. Recording demos is recommended. Our servers will likely record demos for every match but these are only used when there is doubt about a decision the admin has to make. It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.2 Match procedure <a name="maplist"></a>4.2.1 Map list Only the following maps are allowed to be played on during the competition: <ul> <li>de_ancient</li> <li>de_anubis</li> <li>de_inferno</li> <li>de_mirage</li> <li>de_nuke</li> <li>de_overpass</li> <li>de_vertigo</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchrules"></a>4.2.2 Match rules <ul> <li>Diffusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.</li> <li>Throwing grenades/flash bangs/smokes across walls in maps is allowed.</li> <li>Boosting is not considered a bug.</li> <li>Buying and using multiple grenades is allowed but with a max of 2 flash bangs.</li> <li>Multiple grenades are allowed but max 2 flash bangs</li> <li>Bugs on the map must be checked before the match begins. Any protest after the match about map bugs will be ignored.</li> <li>If a player loses connection before the first kill, the match can be restarted. If this happens after the first kill, the server can be paused and have the disconnected player reconnect. Matches won’t be restarted due to disconnections.</li> <li>If you want a player change (sub) during the match, inform the opponent and the compo admins before the match begins!</li> <li>To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.</li> <li>Climbing with help of teammates is allowed in general.</li> <li>Throwing grenades inside walls is not allowed.</li> <li>Self-kills are strictly forbidden, unless an admin forces you to do this as a sanction for disobeying any rules.</li> <li>Bomb planting in a way it can’t be reached is forbidden.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="clientrules"></a>4.2.3 Client rules The admin is allowed to take over your computer before, during and after a game and have a look. Without the pc’s owner in question nearby, the person in question can appoint someone to stay with the admin to make sure no privacy issues are violated. Any trace evidence of cheats found on a player’s computer – even if such discovery took place outside of a game – can lead to exclusion from any competition. For NVIDIA graphics card users: The use of Ambient Occlusion is strictly forbidden. If you are caught using this setting, this will result in a direct loss of the match. Getting caught for a 2nd time will result in removal from the tournament. This setting can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings. The following commands are forbidden: <ul> <li>mat_hdr_enabled</li> </ul> The following startparameters are forbidden: <ul> <li>+mat_hdr_enabled 0/1</li> <li>+mat_hdr_leven 0/1/2</li> </ul> In your game client cfg-folder you’re only allowed to have config files. Pictures, demos, screenshots and zipped files are forbidden. All other configuration changes are allowed as long as they do not give an unfair edge or advantage comparable to cheating. The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary. Boosting through walls/ceilings/ground, sky walking, map swimming, floating and sharking are all forbidden. To throw grenades inside walls is not allowed. Above walls and roofs is allowed. To plant the bomb in a way that it cannot be reached is forbidden. Places that can be reached with help of a team mate are allowed as long as they are visible. Violating this rule will result in tournament administrators intervention. Changing graphic settings to irregular values can be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalscripts"></a>4.2.4 Illegal scripts In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts: <ul> <li>Stop Shoot scripts [Use or Awp scripts]</li> <li>Center view scripts</li> <li>Turn scripts [180° or similar]</li> <li>No Recoil scripts</li> <li>Burst fire scripts</li> <li>Rate changers (Lag scripts)</li> <li>FPS scripts</li> <li>Anti flash scripts or binding (snd_* bindings)</li> <li>Bunnyhop scripts</li> <li>Stop sound scripts</li> <li>Following Commands/CVars are forbidden</li> <li>+weapon_recoil_model 0 (Startparameter)</li> </ul> The following CVAR values must be used: <ul> <li>cl_bobcycle 0.98 (First Time->Warning)</li> </ul> If there are more than one player who used a wrong client setting, the match will be deleted. Exception: cl_bobcycle Using illegal scripts will be penalized if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized. The use of No-Flash and No-Recoil bindings/scripts in any and all forms will be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="customfiles"></a>4.2.5 Custom files The HUD can be changed as long as no information are deleted or falsified which are available in the standard HUD. If the HUD is changed it has to be readable. If an admin is hindered in his work due to an unreadable HUD, penalty points may be assigned. Protests or supports which adhere to this rule will not be admitted and are rejected directly. Apart from the HUD and the GUI no custom files are allowed. This also includes custom models, changed textures or sounds (volume, soundscapes) are forbidden. <a name="colordepth"></a>4.2.6 Color depth and external programs The usage of a color depth of 16bit is not allowed. The usage of external programs (ex. SweetFX, A3D,...) are not allowed to enhance vision. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalprograms"></a>4.2.7 Illegal programs Changing the game graphics or textures with the help of video card drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. NVidia SLI Display, Riva tuner Overlays) is illegal. Failure to comply with this rule will result in a punishment for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized. If you play with ambient occlusion, it will be punished as cheating!! Punishment will be given regardless of whether the script/binding is executed via external hardware or software. Also binding any snd_ command is forbidden. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="ingameoverlay"></a>4.2.8 In-game overlays All In-Game overlays – provided by the game itself – except the following are forbidden: <ul> <li>net_graph 0</li> <li>net_graph 1</li> <li>cl_showpos 1</li> <li>cl_showfps 1</li> <li>cl_showdemooverlay 1 / -1</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="techprobs"></a>4.2.9 Technical problems and disconnects If a disconnection occurs the game should automatically reconnect. When this doesn’t work, a tournament admin will decide what to do. The tournament admin will make a call in every possible scenario regarding the severity of the problem and how to deal with it. But, the following guidelines are in place in the event of a disconnect: <ul> <li>In the case where Frag-o-Matic is responsible for the disconnect, the round needs to be restored to the start of the round where the disconnection happened. I.e. follow the steps as described under “4.3.2 Server crash”.</li> <li>When a player is responsible for his own disconnect, the team with 4 players can decide to continue to play 4v5 or use a pause as described in “4.1.6 Usage of pause”.</li> <li>The disconnected player can then reconnect to the match. If that player fails to reconnect, then the match will continue 4v5.</li> <li>If another Frag-o-Matic participant is responsible for causing a problem, then the match needs to be paused and a tournament admin needs to be notified to make a call on what to do.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.3 CS:GO server <a name="serversettings"></a>4.3.1 Server settings Frag-o-Matic will supply hardware for all servers. All games related to the tournament must be played on these servers. All matches will be played using the latest version of CS:GO and the official Frag-o-Matic CS:GO server config. All matches have to be played on an official Frag-o-Matic CS:GO tournament server and on the provided server number (as listed on our fom.be website, in the csgo compo section). We’ll use a standard (ESL) 5v5 pro league tournament config on a 128 tickrate server: <ul> <li>Startmoney: 0</li> <li>Maxrounds: 30</li> <li>Roundtime: 1m 55s (1.92)</li> <li>Freezetime: 12 seconds</li> <li>C4timer: 40 seconds</li> <li>Pause: 1x 5minutes per half each map.</li> <li>Overtime: MR3 - .000 startmoney</li> <li>Time during half time: 13 seconds</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="servercrash"></a>4.3.2 Server crash In the event of a server crash, after notifying a tournament admin and having them restart the the server, both teams have to re-join the same server and use the following command: <ul> <li>rcon mp_backup_restore_list_files</li> </ul> This will show you the backup files before the server crashed. 1 team captain then executes the correct file by using the following command: <ul> <li>rcon mp_backup_restore_load_file</li> </ul> Example: rcon mp_backup_restore_load_file backup_round12.txt All previous settings (score, money, armor, weapons,...) are then reset to the round before the server crashed and the match is set to paused. To continue the match, use the unpause command: <ul> <li>rcon mp_unpause_match</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="serverlag"></a>4.3.3 Server (var) lag Teams are given the time to play a warm-up match on their server before every compo match if they wish to do so. It’s not allowed to switch to another server once the compo match has been started. Test the server before the match starts. Any server problems should be reported to a tournament admin by going to the compo desk after sending an email with the information below. In the event that you experience any lag during or before a match, please note the time(s) and contact us via Discord or the Compo Desk. We'll escalate this information and, if possible, provide a solution for upcoming matches. The statement or report of (possible) lag in a match is a not valid argument in a protest. However, sending us the data above will give your team the time necessary to avoid any possible forfeits when you notify us at the compo desk after sending your email. Failure in providing us this data will not allow your team to deviate from our time schedule. We strive to provide all our servers lag free. We would like to thank you in helping us improve our servers. <a name="serverplugins"></a>4.3.4 Server plugins No extra plugins will be installed on our CS:GO servers. <a name="rconusage"></a>4.3.5 RCON usage RCON is only allowed as described in “4.1.2 Game setup”. Usage of RCON outside the game setup is penalised by receiving an instant forfeit for the team using any other RCON commands. We monitor all servers and RCON logs and will use this as evidence to hand out a match forfeit to the team using RCON outside of the game setup rules. <a name="rconusage"></a>4.3.6 Warmup servers Subject to availability, we will provide warmup servers. The settings will mirror our war servers as close as possible, but won’t be managed by the csgo team. Participants in our competition are allowed to use our warmup servers as such, to warm up, practice nade throws, practice aim,etc… We will not guarantee availability of those servers, since they will depend on the overall capacity. If warmup servers are available, they cannot ever be used for playing matches. If a match has been played on one of those servers though, the end-scores will still count. It is the responsibility of both teams the correct (assigned) server is joined. At any time, we can convert one of those servers to an official war server (In cases of need). It will at that point no longer show up as a warmup server. <a name="copyright"></a>5. Copyright Notice Copyright © 2005-2022 by E-EVENTS VZW All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher, addressed at <a href="mailto:csgo@fom.be">csgo@fom.be</a> </li> </ul>
 showsponsor(false)
 sponsorcontent
 showfiles(false)
 filescontent
 prizescontent<h1> First Place </h1> <ul> <li> <h3>525 €</h3> </li> </ul> <h1>Second Place</h1> <ul> <li> <h3>315 €</h3> </li> </ul> <h1>Third Place</h1> <ul> <li> <h3>210 €</h3> </li> </ul>
 precompo(false)
 donations0
 donationAmount0
 scheduleregistration closes at 21! please make sure all games are played on time! poules will be made and will be playable. saturday 10am we will start with the brackets semi final will be at 10am on sunday with afterwards the grand final Have fun and Good luck!
 faq
 sponsorUrl
 sponsorImg(null)
 sortTimeLabel0
 TeamA(array)
 id10265
 nameBASTARDS.AF9K
 leaderId5352
 compoId367
 pouleId1452
 notes
 withdrew(false)
 TeamB(array)
 id10336
 nameBorn2Throw
 leaderId9602
 compoId367
 pouleId1452
 notes
 withdrew(false)
 AdminEdit(array)
 id(null)
 facebook_id(null)
 username(null)
 new_username(null)
 nickname(null)
 password(null)
 firstname(null)
 lastname(null)
 active(null)
 validationCode(null)
 mailValidationCode(null)
 group_id(null)
 created(null)
 modified(null)
 last_login(null)
 street(null)
 nr(null)
 bus(null)
 zip(null)
 city(null)
 country(null)
 phone(null)
 gsm(null)
 gender(null)
 birthdate(null)
 clanId(null)
 clantrust(null)
 clanjoinId(null)
 hwbudget(null)
 education(null)
 profession(null)
 hoursaweek(null)
 language(null)
 oldId(null)
 receive_newsletter(null)
 imageUrl(null)
 slug(null)
 fb_link(null)
 fb_location(null)
 CPU(null)
 MOBO(null)
 GFX(null)
 RAM(null)
 steamName(null)
 steamId(null)
 originName(null)
 lolSummonerName(null)
 Other(null)
 comment(null)
 seat_id(null)
 msg_notifications(null)
 mouseHand(null)
 deviceId(null)
 alternative_login(null)
 5(array)
 War(array)
 id27961
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10265
 teamB10375
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB1
 scoreBByB16
 finalScoreA1
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1452
 level2
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 06:30:38
 Compo(array)
 id367
 nameGRAND - CS:GO
 steamGameId(null)
 nrPlayersTeam5
 maxTeams64
 compoTypeId0
 nrPoules3
 nrWinnersPoule4
 compoStateId5
 eventId46
 roundDE2
 addSecondaryFinal(false)
 adminId8749
 adminId2(null)
 bannerUrl(null)
 description<h1>password to the servers: war</h1> 
 tagId31
 allowDrawInPoule1
 nrLosersToBrackets0
 pauzed0
 rulebookFrag-o-Matic 24.0 Rulebook Counter-Strike:Global Offensive (CS:GO) Introduction This is the official rulebook for the Frag-o-Matic 24.1 CS:GO competition, that will take place from the 1st until the 3rd of September 2023. These rules apply to the players throughout all stages of CS:GO competition. Failure to adhere to these rules may be penalized as outlined. It should be noted that the tournament administrators have the final word, and have the power to decide on any circumstances that are not outlined by this document, and in extreme cases may overrule the rulebook in order to preserve fair play and sportsmanship. Frag-o-Matic reserves the right to change these rules at any time. The CS:GO admin team wishes you good luck in the tournament and hopes that you have an enjoyable competition. We’ll do our utmost best to make it fair, fun and exciting for everyone involved. <a name="navigation"></a>Table of contents <ol> <li><a href="#admin">Admins and communication</a></li> <li><a href="#compo">Compo overview</a> <ol> <li><a href="#participants">Participants</a></li> <li><a href="#teamsheets">Team sheets</a></li> <li><a href="#teamnames">Team names</a></li> <li><a href="#teammanager">Team manager / coach</a></li> <li><a href="#teamcaptain">Team captain</a></li> <li><a href="#players">Players</a> <ol> <li><a href="#grstandard">Grooming standards</a></li> </ol> </li> <li><a href="#cheating">Cheating</a> <ol> <li><a href="#forbiditems">Forbidden items</a></li> </ol> </li> <li><a href="#match">Match protests and forfeit</a> <ol> <li><a href="#definitions">Definition</a></li> <li><a href="#matchprotest">Match protest rules</a></li> <li><a href="#forfeitrules">Forfeit rules</a></li> </ol> </li> <li><a href="#seeding">Seeding</a></li> </ol> </li> <li><a href="#general">General</a> <ol> <li><a href="#generalrules">General rules</a></li> <li><a href="#sanctions">Sanctions and disputes</a></li> <li><a href="#confidentiality">Confidentiality</a></li> <li><a href="#coc">Code of conduct</a></li> <li><a href="#drugsalcohol">Drugs and alcohol</a></li> <li><a href="#betting">Betting</a></li> <li><a href="#addagreement">Additional agreements</a></li> <li><a href="#streaming">Streaming, interviews and media</a> <ol> <li><a href="#broadcasting">Broadcasting</a></li> <li><a href="#matchmedia">Match media</a></li> <li><a href="#screenshots">Screenshots</a></li> </ol> </li> <li><a href="#playerchanges">Player changes</a></li> <li><a href="#prizemoney">Prize money</a></li> </ol> </li> <li><a href="#csgorules">Counter-Strike:Global Offensive rules</a> <ol> <li><a href="#tournament">Tournament structure and time schedule</a> <ol> <li><a href="#penalties">Penalties and forfeits during the time schedule</a></li> <li><a href="#compomaxteams">Compo sign-up and max teams</a></li> <li><a href="#structure">Structure</a></li> <li><a href="#gamesetup">Game setup</a></li> <li><a href="#vetosystem">Veto system</a></li> <li><a href="#compospecificrules">Compo specific rules</a></li> <li><a href="#usageofpause">Usage of pause</a></li> <li><a href="#demofiles">Demo files</a></li> </ol> </li> <li><a href="#matchprocedure">Match procedure</a> <ol> <li><a href="#maplist">Map list</a></li> <li><a href="#matchrules">Match rules</a></li> <li><a href="#clientrules">Client rules</a></li> <li><a href="#illegalscripts">Illegal scripts</a></li> <li><a href="#customfiles">Custom files</a></li> <li><a href="#colordepth">Color depth and external programs</a></li> <li><a href="#illegalprograms">Illegal programs</a></li> <li><a href="#ingameoverlay">In-game overlays</a></li> <li><a href="#techprobs">Technical problems and disconnects</a></li> </ol> </li> <li><a href="#csgoserver">CS:GO server</a> <ol> <li><a href="#serversettings">Server settings</a></li> <li><a href="#servercrash">Server crash</a></li> <li><a href="#serverlag">Server (var) lag</a></li> <li><a href="#serverplugins">Server plugins</a></li> <li><a href="#rconusage">RCON usage</a></li> <li><a href="#warmupservers">Warmup servers</a></li> </ol> </li> </ol> </li> <li><a href="#copyright">Copyright Notice</a></li> </ol> <a name="admin"></a>1. Admins and communication <hr /> Communication before the LAN: <ul> <li>General contact > <a href="mailto:csgo@fom.be">csgo@fom.be</a></li> </ul> Please email us any feedback before and after the LAN event. CS:GO admin team: <ul> <li>Dragon <ul> <li>Steam: https://steamcommunity.com/profiles/76561198244170010/</li> <li>Discord: dragon (main communication line)</li> </ul> </li> </ul> Communication during the LAN: The communication during the LAN will be through Steam, Discord or at the Compo Desk. We will be available as much as possible in the <a href="https://discord.gg/URX6v82Wmp" target="_blank">#csgo channel</a>. We will use this as a second channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #csgo channel. Discord will be our main communication channel. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compo"></a>2. Compo overview <hr /> <a name="participants"></a> 2.1 Participants Due to lack of time, we have a tight schedule. Therefore we can make the decision to force teams to only participate in 1 grand compo! We will contact the teams who are signed in for 2 grand compo’s at the moment and they will need to make a choice. When a team refuses, we will remove them from the competition to make room for other teams. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamsheets"></a> 2.2 Team sheets As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops. A rule violation by any player in a team may lead the tournament admins to sanction the entire team, even if the rest of the team was not aware of the violation. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamnames"></a> 2.3 Team names <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teammanager"></a> 2.4 Team manager / coach The team manager does not have any responsibilities. The team manager is eligible to play for his team in matches, providing he’s indicated as a “Player” on the team in the team sheet. The communication with the team will not go via the team manager, all communication will go via the team captain! Spectators are not allowed on our servers. Only tournament admins may be in spectator mode during a match. The only exception is: coaches are allowed to spectate a match using the coach's command, only if the tournament admin is notified, and thus to spectate their team only. They are obligated to use the “coach t” or “coach ct” command before the match start and aren’t allowed to join after a match has been started. If noticed that the coach is abusing this rule, the team will get punished for it (e.g. round loss, side loss or match loss). During a match, the coach may only communicate with the players during freeze-time, warm up, half-time, or during one of the 4 timeouts. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamcaptain"></a> 2.5 Team captain We consider the one who registered the team into the compo on the Frag-o-Matic website as captain! The clan leader or team captain is responsible for his team and all the players in that team. It is recommended that the team captain is fluent in English or Dutch, as he will be required to communicate with the tournament admins. The team captain must read and understand the rulebook. The team captain is responsible for ensuring his team and players adhere to the rules. Ignorance of the rules is not an excuse for rule violations. The team captain may choose at any time to nominate another player in or manager of his team as team captain for any reason. Such nominations must be reported by the team captain, either in person or in writing, to the admins before the game starts. All official communication between a competing team and the tournament admins must be conducted by the team captain. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="players"></a> 2.6 Players All players must read and understand the CSGO rulebook. Any player in violation of a rule, will be sanctioned as described in this rulebook. Each team must have five players on the match server at the match start time as indicated by the schedule, unless permission has been granted by the tournament admins to play with less than five players. Only players registered for a team in the tournament may play for that team unless otherwise discussed with the tournament admin. All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins. Players registered for a team in the tournament may not play for any other team in the same tournament. Each player has to use their nickname that is similar to the nickname he/she has entered on their fom.be account. All players for a team must be clearly identifiable in-game with a uniform tag for that team and a separate, noticeably different nickname for each player. Players may not significantly change their nickname during the tournament. Any nickname they use during the tournament must always obviously visibly correspond to their original nickname. You are not allowed to change your nickname in-game. If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning. 3 warnings are equal to a forfeit in 1 match. Player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate. Make sure your steam account is linked with your fom.be account corresponding to your nickname. Players are strictly prohibited from using any other person’s steam account for any reason whatsoever during the CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="grstandard"></a> 2.6.1 Grooming standards People participating in the CS:GO tournament are expected to normal grooming standards. You may be asked to take action if you or your clothing have a look or odor that’s offensive to other players. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="cheating"></a> 2.7 Cheating During Frag-o-Matic we won’t investigate cheaters from an external event. When we discover someone cheating during our LAN, that player and his team will be banned from the compo and the player will be also banned for the next Frag-o-Matic edition. Furthermore we will investigate reports of players cheating during other tournaments until 2 weeks before the LAN. When a player is discovered cheating during another tournament/platform 12 months before the event occurs, then that player will not be allowed to play on that edition of Frag-o-Matic within the CS:GO competition and the edition after that. If one of the following rules apply, then that player will not be allowed to compete in our tournament: Caught cheating within a tournament/platform 12 months before the start date of our event. There needs to be enough evidence for that player, that he/she was cheating and the tournament admins will judge if the evidence is valid OR if he/she was caught cheating on the following platforms: <ul> <li><a href="ts3server://ts.fom.lan">ts.fom.lan</a> - CS:GO admin channel</li> <li>Discord: <a href="https://discord.gg/MbPY2ge">https://discord.gg/MbPY2ge</a> <ul> <li>Teams are only allowed to use a uniform team name for their team.</li> <li>Teams may not change their team name during the tournament.</li> <li>Teams may not change their team in-game tag during the tournament, unless none was set.</li> <li>Duplicating team names of other teams is not allowed.</li> <li>Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.</li> <li>Team names are not allowed to be offensive.</li> <li>Please make sure your team name is filled in on your fom.be profile.</li> </ul> <ul> <li>Faceit</li> <li>Esl</li> <li>Valve (vac ban for any Counter strike: Global Offensive game)</li> <li>ESEA</li> <li>Cevo</li> </ul> </li> <li>When a player is caught selling or buying cheats. In any case the admin will have the final decision. This means that the admin will review the evidence and make the final call. If a player shows the intention of coming to our tournament to cheat and we’re provided evidence of this. Everyone from the community may send evidence to csgo@fom.be, when they suspect someone participating at Frag-o-Matic of cheating. All forms of cheating in matches are forbidden, and will result in an overall forfeit in the tournament. Possibilities for cheating in Counter-Strike:Global Offensive are, for example; all kinds of multi-hacks, wallhack, aimbot, colored models, no-recoil, no-smoke, no-flash and sound changes. All hardware or software that has an influence on the game in such a way that the essence of the game is affected are banned from this tournament. Any use of this kind of hardware will result in a disqualification of the tournament as it will be recognized as cheating. When proven that a player is not cooperating in his own ban research or is lying on purpose. He will get banned for 1 edition. You can find our banlist at http://www.fom.be/contents/view/cs-go-banlist The mentioned people in our ban list are not allowed in the CS:GO tournaments at Frag-O-Matic until the edition that’s stated there. When these people compete under a false name nonetheless or try to circumvent the rules then they will receive an extended or permanent ban. Here are some of the other examples of ways to gain advantages, this list may not be the full list but if players are unsure of certain things, they should seek to ask the tournament admins first: Flash Bang, Smoke Grenade, and Hand Grenade Bugs - it is illegal to use any flash bang, smoke grenade, or hand grenade bugs, regardless of intent. Silent Bomb Plants - ALL bomb plants must be done in a position where your opponents can hear you. There should be no rotation in players to gain money advantages throughout a match. The bomb must be planted on solid surfaces on the map, ie where an opponent can defuse from, so not up in the air or floating. Illegal Bomb Defuses - No player can defuse a bomb through any other solid object on the map, it has to be done in clear view. It is also forbidden to try to intentionally distort your hitboxes during a defuse situation to prevent an opponent from killing you in game. Walking/Boosting through walls - No player should walk, boost through walls or roofs. To do so will see your team penalized for that round. Map Exploits - Boosts that include the use of clipping are strictly forbidden. The term “Clipping” defines that when a player is boosted can see through certain parts of the map (ie over/under walls, or through solid objects on the map). If any player or team feels unsure on a new advantage they have found through their practice sessions, they are welcome to show this specific spot to the tournament team to review. Any player or team that does this will be treated to the strictest confidence as not to jeopardize your strategic advantage, however we can rule on whether it is a legal move. We strongly advise teams to give us plenty of time ahead of an event so we can review it in good time and make good judgement on it. The game admins may inspect your machine at any time throughout the event to inspect for cheats or hacks within your game files, steam cloud and anywhere on your PC or memory sticks. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="forbiditems"></a>2.7.1 Forbidden items During the lan, to prevent cheating by using external devices or items, the following items are forbidden: <ul> <li>Smartwatches; Having or carrying a smartwatch during the event, when competing in the CS:GO competition, that player will immediately be disqualified from the competition.</li> <li>Alienware Wireless Headset AW988; Visual representation of audio isn’t allowed.</li> <li>AR (augmented reality) glasses</li> <li>Hardware from the brand “Bloody” (these are mice that come with software that reduces recoil on weapons)</li> </ul> Any other electronic devices (like smartphones) that are used during a match will be considered suspicious and we’ll ask that they’re not used. If, during a match, the suspicious device is still in use; the team of the player using the device will receive a warning. After 3 warnings the team will receive a disqualification from the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="match"></a>2.8 Match protests and forfeit <a name="definitions"></a> 2.8.1 Definition A protest is a raised issue for problems that affect the match outcome; a protest may even be filed during a match for things like incorrect server settings and other related issues. A protest is the official communication between a team captain and a tournament admin. A forfeit is a lose or surrender. <a name="matchprotest"></a> 2.8.2 Match protest rules Participants are only allowed to issue a match protest before the beginning of their next match. The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “they are cheaters” will not be enough. Insults and flaming are strictly prohibited in a protest, and may result in the protest being ruled against the insulting party. <a name="forfeitrules"></a> 2.8.3 Forfeit rules A forfeit can be called for a single match or the entire competition from a competing team for their team. Only the team captain can raise a forfeit for their team. A forfeit can also be raised by an admin as a penalty for wrongdoing. For example, in most cases where a competing team doesn’t follow the time schedule. The tournament admins can always force a forfeit. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="seeding"></a>2.9 Seeding Seeding is done through an objective outlook towards data provided by all participants for every event. Every participant is required to provide us their main steam account, ESEA and/or CEVO profile, FACEit level and previous wins/achievements. The supplied data is only kept and used for one event to calculate an individual “score” based on reached rank, played time, csgo hours and historical performance/achievements from Frag-o-Matic or other tournaments. The team sum of 5 individual scores will show an objective score where the higher the score, the higher the team seeding. The tournament admins won’t seed teams higher based on any subjective opinions. If no statistical data was provided for all 5 team member, than that team will be seeded beyond top 16. <a name="general"></a>3. General <hr /> <a name="generalrules"></a> 3.1 General rules Frag-o-Matic Counter strike:Global Offensive (CS:GO) 5v5 tournament is a local area network (LAN) tournament. By competing in this tournament, teams and players accept these rules in full. Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation. In the beginning of the LAN the team captains can sit together with the admin to discuss the rules and to make adjustments if needed. The decisions are made by the admin. If you have any issues with the rules, you can explain this by sending an email to <a href="mailto:csgo@fom.be">csgo@fom.be</a> up to one week before the start of the event. Clarification of any point in the rules is available from the tournament admins at any time during the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="sanctions"></a>3.2 Sanctions and disputes Sanctions and disputes will be resolved by the main tournament admin. The admin’s decision on any sanction or dispute is final. Abusive behavior towards the Frag-o-Matic staff, tournament admins or opponents at any time during the tournament is unacceptable and will be punished with warnings. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="confidentiality"></a>3.3 Confidentiality The content of protests, support communication, discussions or any other correspondence with tournament officials and administrators are considered as strictly confidential. The publication of such material is prohibited. If the contents has been shared without consent then this could lead to a team’s disqualification. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="coc"></a>3.4 Code of conduct Any form of aggression<a href="#coc_aggression">*</a> (both verbally and physically) will not be tolerated. Any and all physical aggression will be sanctioned with an immediate disqualification by that person or team performing the physical act (both actioned and reactioned). Any verbal aggression will be sanctioned by a time-out for that person or team. A time-out is either set in time (hours/day) or in amount of matches when a player or team is not allowed to participate in the CS:GO competition. Any situation that is about to escalate should be dealt with in a calm and diplomatic manner. An audience with any Frag-o-Matic crew member (CS:GO admin or Frag-o-Matic team leaders) can always be called for at any time during the event. Keep in mind that this audience can not be used to waste time or get a time advantage. At any point, the CS:GO tournament admins can decide to continue with the competition with or without consent from either players or other Frag-o-Matic staff. In the event when a single player or more are accused of cheating, the event will continue nonetheless. Evidence will be presented to the tournament admins and a call will be made at a later stage of the event. This rule is set to not cause any delays and have the situation under control. Any player(s) or team(s) ignoring this rule will receive a forfeit. Any player or team ignoring a CS:GO admin will be sanctioned with a warning. 3 warnings are equal to a forfeit of 1 match. <a name="coc_aggression"></a>*A form of aggression is described as: <ul> <li>Instrumental aggression -- Aggression aimed at obtaining an object, privilege or space with no deliberate intent to harm another person. Typical of participants wanting to get ahead of the competition with lies, anger, bullying, criticizing other people behind their backs, leaving others out of a group or otherwise ostracizing them, turning people against each other, dismissing the opinions of others (passive aggression).</li> <li>Hostile aggression -- Aggression intended to harm another person, such as hitting/kicking/biting someone (active aggression). Threatening to beat up someone (nonverbal intimidation). Sending threatening messages through emails, phone calls, or social media, or making threats against someone's life, shouting, and swearing (verbal hostility). Breaking someone's computer, destroying someone's cell phone, or other forms of vandalism (destruction of property).</li> <li>Relational aggression -- A form of hostile aggression that does damage to another's peer relationships, as in social exclusion, gossiping or rumor spreading. Examples: Arguments within a team after a lose that lead to a verbal fight.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="drugsalcohol"></a>3.5 Drugs and alcohol To play a match under the influence of any drugs or performance enhancers is strictly prohibited, and may be punished with exclusion from the tournament. If an admin finds that a player is not capable of competing in the competition because of intoxication, the admin can exclude that person from the entire tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="betting"></a>3.6 Betting Betting on any match in the CS:GO tournament is strictly forbidden. <a name="addagreement"></a>3.7 Additional agreements Teams may be required to play any match on the stage. If so, teams will be notified at least 20 minutes prior to the start time of that match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="streaming"></a>3.8 Streaming, interviews and media <a name="broadcasting"></a>3.8.1 Broadcasting Frag-o-Matic reserves the right to broadcast any match or demo, teams may not refuse such broadcasts. All forms of client side game broadcasting are NOT allowed. Frag-o-Matic participants are not allowed to watch a local GOTV if a CS:GO server broadcasts a game. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchmedia"></a>3.8.2 Match media All match media (screenshots, demos, etc.) must be kept until the end of the event. Faking or manipulating match media is forbidden and will result in exclusion from the tournament. Match media should be named clearly based on what it is. It is not possible to file a protest to complain about bad match media naming. However if a tournament admin is hindered in their work because of bad match media naming, then a tournament admin will give a warning. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="screenshots"></a>3.8.3 Screenshots The admin can ask for screenshots of every game on any moment during the event. When he does this, the team leader has 15 minutes time to deliver the screenshot to the admin. A screenshot of the scoreboard at the end of each half must be taken. When this is not done by a team it can result in a lost match when one of the other teams complains about a score. An RCON status screenshot must be taken: <ul> <li>at the beginning of the match</li> <li>in case of a server/player change</li> <li>if a player reconnects</li> </ul> RCON status screenshots made with the help of programs like HLSW etc. are not sufficient. In order to take an RCON status you have to use the console command “rcon status” (don’t forget to enter your RCON password) and take a screenshot of that. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="playerchanges"></a>3.9 Player changes Teams are permitted to substitute players (only with another player not active in the CS:GO competition) during pauses and between rounds, if they have permission from the tournament admin. Consent for substitutions must be obtained from the tournament admins, and substitute players must be registered for that team in the tournament. You can make this clear to the admin by using the contact information in section ‘Admins and communication’. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="prizemoney"></a>3.10 Prize money When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="csgorules"></a> 4. Counter-Strike:Global Offensive rules <hr /> <a name="tournament"></a>4.1 Tournament structure and time schedule Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. On Saturday and Sunday, teams must be present at 10:00 (AM) and ready to start playing the rest of their scheduled matches. It can be the case that the tournament admins decide to start earlier or end later, but this will be communicated (to all team captains). An exact time schedule will be provided on our fom.be website for all teams to follow. Each match will have a start time on which the game needs to be started. The team(s) that are responsible where the start time has not been met will receive a forfeit for that match. Whether or not this rule will be applied, is the decision of a tournament admin. The schedule for the tournament may be subject to change at any time. Matches may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice. Games will not be rescheduled to an earlier time in the same day if either of the teams have not yet played a game on that day without the consent of both team captains. Where possible the tournament admins will notify any teams involved in a rescheduled game of the new match start time at least one hour before the new start time. In the event a match is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible. If there’s insufficient time to complete a match, the tournament admins may at any time declare one team as the winner, if that team holds a clear advantage in that match. It is the responsibility of the tournament admins to decide whether a team holds a clear advantage. This rule will only be used in the emergency when the remaining event time is a factor. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="penalties"></a>4.1.1 Penalties and forfeits during the time schedule If 1 or more teams are still playing a match in a previous stage or if 1 team is late and doesn’t start playing their match in the stage where they are; Teams are offered 30 minutes of grace time in both circumstances, after 30 minutes warnings are handed out: After 30 minutes that team, who’s still not playing their scheduled match, will receive a 1st warning from a tournament admin. A notice via our csgo channel on discord and if the team is present and found at their seat they’ll be warned in person as well. A second warning is given in the same manner 5 minutes after the first warning. A third and final warming is given in the same way 5 minutes after that. 5 minutes after the final warning the team who received 3 warnings will receive 1 game loss for their match in the next round. In case of a bo3 in the next round, a bo2 will be played with one win to the team that was on time. If after 15 minutes the team with 3 warnings and one loss in the next round is still not playing, they’ll receive a forfeit from an admin. In case of a bo1 (in the lower bracket for example) we won’t lose any more time and a forfeit will be forced. The forfeit is applied on our fom.be website and a notice is given on Discord in our csgo channel. The tournament admins will keep a record of the warnings and will communicate this to the compo desk. As mentioned in our general rulebook; Non-acceptable excuses for a delay: “We want to eat” isn’t a valid excuses for starting an argument at the compo desk. As a note, we ask that teams only take a maximum of 15 minute breaks in between games and matches to avoid any penalties. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compomaxteams"></a>4.1.2 Compo sign-up and max teams All compo sign-ups are done via our fom.be website. Some rules are already explained in our general rulebook. Any team that is not “full”, meaning the team doesn’t consist of minimum 5 players, will be removed from the compo sign-up one hour before the start of the competition. We allow a maximum 64 teams to register to our CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="structure"></a>4.1.3 Structure Our CS:GO tournament will use a poule system and 3 double elimination brackets (pro, semi-pro and fun). Each poule will consist out of 3-4 teams who will compete against each other to make it into the brackets. Each team within the poule needs to play against any other team within its poule. Following the poule stage, the 2 winners from each poule will advance to a pro bracket, the last 2 teams from each poule will advance to a semi-pro bracket and <s>other teams will proceed to the fun bracket</s>. Our compo structure will use the following setup for pro, semi-pro and fun: <ul> <li>Groupstage > BO1 (best of 1)</li> <li>Upper Bracket > BO3 (best of 3)</li> <li>Lower Bracket > BO1 (best of 1)</li> <li>Pro & semi-pro bracket: <ul> <li>Semi-final (Finals in lower bracket) > BO3 (best of 3)</li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> </li> <li><s>Fun bracket:</s> <ul> <li><s>Semi-final (Finals in lower bracket) > BO1 (best of 1)</s></li> </ul> </li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> When 2 teams have the same amount of points after the poules we will look at the following criteria in order: <ul> <li>The match between the 2 teams</li> <li>The won rounds total</li> <li>The lost rounds total</li> <li>Seeding</li> </ul> We can also look at other criteria if we feel that it's necessary (also cooperation). The admin is allowed to overrule these criteria. If there’s not enough data to validate a criteria the admin can chose to ignore it. A tournament admin can decide to change some matches from BO3 to BO1 or visa versa when needed. (For example: no time to play a BO3). <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="gamesetup"></a>4.1.4 Game setup Matches will be played 5on5. Playing with fewer than five players in any match is only allowed with permission from the tournament admins. Before a match starts, both teams must state that they are ready to start the match. The must do this by having one team member typing ‘ready’ in server chat. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated. Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug. You’ll need to use the following match setup to play every game: <ul> <li>2 teams join the server that is assigned to them on our fom website.</li> <li>The team captains can use the RCON password “godmode” to follow the next steps : <ul> <li>Don’t forget to do ‘cl_mute_enemy_team 0’</li> <li>Change the map to de_mirage (rcon changelevel de_mirage)</li> <li>Load the Frag-o-Matic config (rcon exec fom5on5.cfg)</li> <li>Start a knife round on de_mirage (optional). The winner of this knife round can decide who team A is. Start the map veto process (Veto is explained under ‘Veto system’’).</li> <li>After the Veto the team captain needs to change the map to the first map of Team A (in a BO3) or the single map that was chosen (in a BO1) (rcon changelevel ‘mapname’)</li> <li>Load the fom5on5.cfg again on this map. (rcon exec fom5on5.cfg)</li> <li>After this the teams do another knife round to decide which team will start on which side of the map. The winner of the knife round decides which side they want to start on and that team will also start the match. (rcon mp_restartgame 1)</li> </ul> </li> </ul> If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server can be paused at the end of the current round (see rule ‘Usage of pause’ function) by one of the teams. The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed. If a player/substitute doesn’t connect within that time, then the match is continued 4on5, or 4on4 if the opposing team agrees and the tournament admins are informed. There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="vetosystem"></a>4.1.5 Veto system Our veto process is the next step after playing a knife round, as described in ‘Game setup’. The map(s) chosen to be played in each BO1 and BO3 are done via elimination (i.e. veto). Where ‘team 1 = A’ and ‘team 2 = B’, with A being decided by the winner of the knife round. Teams can also decide who team A/B is without playing a knife round. The maps you don’t want to play as a team, should be the maps that you veto during this process. The veto process needs to be done in server chat. VETO rules best-of-1: ABABAB veto. The map pool exists out of 7 maps. 6 maps are vetoed during this process, 3 maps for each team. The remaining map is the map played in the best-of-1 match. VETO rules best-of-2: ABAB veto AB play. The map pool exists out of 7 maps. 4 maps are vetoed during this process, 2 maps for each team. Out of the 3 remaining maps, 1 team each gets to decide a map to play on. VETO rules best-of-3: A/B veto, A/B play and A/B veto. The map pool exists out of 7 maps. 4 maps are eliminated, and 3 maps are selected to play. Each team needs to veto a map, followed by each team choosing a map and again each team vetoing a map. The remaining map is the third map that needs to be played if both teams win a map. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compospecificrules"></a>4.1.6 Compo specific rules All matches in the group stage are played MR15. All matches in the brackets are played MR15 (meaning, 16 rounds won = game win). In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games are best of three (BO3) in the bracket, 3 maps are decided by veto. The grand final is a best of three (BO3) with map advantage! When in the brackets a game is tied an overtime needs to be played. The overtime will be played MR3 with 10.000$ start money. For the start of the overtime teams will stay on the side which they played the previous half on, during halftime sites will be swapped. Teams will continue to play overtimes until a winner has been found. We have our own special breed of bracket seeding. For more information please contact us in advance. This bracket seeding is law. Obey it. All CS:GO players can only use our ts.fom.lan (local) teamspeak for voice communication. Teams are only allowed to have 5 players + 1 coach in their teamspeak channel whilst in a competition match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="usageofpause"></a>4.1.7 Usage of pause Pauses may be taken for any reason. Teams are permitted 3 pauses per side in each match. Each pause having a maximum duration of 5 minutes, unless authorised by an admin to take a longer pause (in case of technical difficulties, for example). After a “pause”-event, an “unpause“-command needs to be done. Teams can’t unpause without the consent of the other team. Pauses may only be activated at the start of the next round during freeze time. So make sure you tell the other team before round end (in all-chat), that your team will take a pause in the next freeze time. Usage: Type the following commands in console, to activate and deactivate the pause event. Pause = rcon mp_pause_match Unpause = rcon mp_unpause_match Illegal usage: DON’T USE = sv_pause If a team does use sv_pause, they have to surrender 1 round. (by all team members typing “kill” in console) <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="demofiles"></a>4.1.8 Demo files GoTV demos must be active for each match to be recorded. It’s the responsibility of (both) team captains to ensure that GoTV is recording. If this isn’t the case, the tournament admins will be forced to make calls without a recording when a dispute occurs. It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A knife round is part of a match and should be recorded. At least one of the players must be able to upload the knife round on admin request. Protests regarding missing knife rounds are not valid. In general, defective or manipulated demos will be treated as missing demos. If the demo is incomplete, as decided by the admin, it also will be treated as missing demo. If a protest is opened for a match, all match media need to be kept until the end of the event. Demos can only be requested up to a maximum of 30 minutes after a match via the admin. A demo request must state which teams were playing, the name(s) of the map(s) the match(es) was/were played on, the time of the match(es) and the server IP address(es). If a player or a team illegally aborts the match, they lose their right to demand demos. Recording demos is recommended. Our servers will likely record demos for every match but these are only used when there is doubt about a decision the admin has to make. It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.2 Match procedure <a name="maplist"></a>4.2.1 Map list Only the following maps are allowed to be played on during the competition: <ul> <li>de_ancient</li> <li>de_anubis</li> <li>de_inferno</li> <li>de_mirage</li> <li>de_nuke</li> <li>de_overpass</li> <li>de_vertigo</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchrules"></a>4.2.2 Match rules <ul> <li>Diffusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.</li> <li>Throwing grenades/flash bangs/smokes across walls in maps is allowed.</li> <li>Boosting is not considered a bug.</li> <li>Buying and using multiple grenades is allowed but with a max of 2 flash bangs.</li> <li>Multiple grenades are allowed but max 2 flash bangs</li> <li>Bugs on the map must be checked before the match begins. Any protest after the match about map bugs will be ignored.</li> <li>If a player loses connection before the first kill, the match can be restarted. If this happens after the first kill, the server can be paused and have the disconnected player reconnect. Matches won’t be restarted due to disconnections.</li> <li>If you want a player change (sub) during the match, inform the opponent and the compo admins before the match begins!</li> <li>To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.</li> <li>Climbing with help of teammates is allowed in general.</li> <li>Throwing grenades inside walls is not allowed.</li> <li>Self-kills are strictly forbidden, unless an admin forces you to do this as a sanction for disobeying any rules.</li> <li>Bomb planting in a way it can’t be reached is forbidden.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="clientrules"></a>4.2.3 Client rules The admin is allowed to take over your computer before, during and after a game and have a look. Without the pc’s owner in question nearby, the person in question can appoint someone to stay with the admin to make sure no privacy issues are violated. Any trace evidence of cheats found on a player’s computer – even if such discovery took place outside of a game – can lead to exclusion from any competition. For NVIDIA graphics card users: The use of Ambient Occlusion is strictly forbidden. If you are caught using this setting, this will result in a direct loss of the match. Getting caught for a 2nd time will result in removal from the tournament. This setting can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings. The following commands are forbidden: <ul> <li>mat_hdr_enabled</li> </ul> The following startparameters are forbidden: <ul> <li>+mat_hdr_enabled 0/1</li> <li>+mat_hdr_leven 0/1/2</li> </ul> In your game client cfg-folder you’re only allowed to have config files. Pictures, demos, screenshots and zipped files are forbidden. All other configuration changes are allowed as long as they do not give an unfair edge or advantage comparable to cheating. The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary. Boosting through walls/ceilings/ground, sky walking, map swimming, floating and sharking are all forbidden. To throw grenades inside walls is not allowed. Above walls and roofs is allowed. To plant the bomb in a way that it cannot be reached is forbidden. Places that can be reached with help of a team mate are allowed as long as they are visible. Violating this rule will result in tournament administrators intervention. Changing graphic settings to irregular values can be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalscripts"></a>4.2.4 Illegal scripts In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts: <ul> <li>Stop Shoot scripts [Use or Awp scripts]</li> <li>Center view scripts</li> <li>Turn scripts [180° or similar]</li> <li>No Recoil scripts</li> <li>Burst fire scripts</li> <li>Rate changers (Lag scripts)</li> <li>FPS scripts</li> <li>Anti flash scripts or binding (snd_* bindings)</li> <li>Bunnyhop scripts</li> <li>Stop sound scripts</li> <li>Following Commands/CVars are forbidden</li> <li>+weapon_recoil_model 0 (Startparameter)</li> </ul> The following CVAR values must be used: <ul> <li>cl_bobcycle 0.98 (First Time->Warning)</li> </ul> If there are more than one player who used a wrong client setting, the match will be deleted. Exception: cl_bobcycle Using illegal scripts will be penalized if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized. The use of No-Flash and No-Recoil bindings/scripts in any and all forms will be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="customfiles"></a>4.2.5 Custom files The HUD can be changed as long as no information are deleted or falsified which are available in the standard HUD. If the HUD is changed it has to be readable. If an admin is hindered in his work due to an unreadable HUD, penalty points may be assigned. Protests or supports which adhere to this rule will not be admitted and are rejected directly. Apart from the HUD and the GUI no custom files are allowed. This also includes custom models, changed textures or sounds (volume, soundscapes) are forbidden. <a name="colordepth"></a>4.2.6 Color depth and external programs The usage of a color depth of 16bit is not allowed. The usage of external programs (ex. SweetFX, A3D,...) are not allowed to enhance vision. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalprograms"></a>4.2.7 Illegal programs Changing the game graphics or textures with the help of video card drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. NVidia SLI Display, Riva tuner Overlays) is illegal. Failure to comply with this rule will result in a punishment for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized. If you play with ambient occlusion, it will be punished as cheating!! Punishment will be given regardless of whether the script/binding is executed via external hardware or software. Also binding any snd_ command is forbidden. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="ingameoverlay"></a>4.2.8 In-game overlays All In-Game overlays – provided by the game itself – except the following are forbidden: <ul> <li>net_graph 0</li> <li>net_graph 1</li> <li>cl_showpos 1</li> <li>cl_showfps 1</li> <li>cl_showdemooverlay 1 / -1</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="techprobs"></a>4.2.9 Technical problems and disconnects If a disconnection occurs the game should automatically reconnect. When this doesn’t work, a tournament admin will decide what to do. The tournament admin will make a call in every possible scenario regarding the severity of the problem and how to deal with it. But, the following guidelines are in place in the event of a disconnect: <ul> <li>In the case where Frag-o-Matic is responsible for the disconnect, the round needs to be restored to the start of the round where the disconnection happened. I.e. follow the steps as described under “4.3.2 Server crash”.</li> <li>When a player is responsible for his own disconnect, the team with 4 players can decide to continue to play 4v5 or use a pause as described in “4.1.6 Usage of pause”.</li> <li>The disconnected player can then reconnect to the match. If that player fails to reconnect, then the match will continue 4v5.</li> <li>If another Frag-o-Matic participant is responsible for causing a problem, then the match needs to be paused and a tournament admin needs to be notified to make a call on what to do.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.3 CS:GO server <a name="serversettings"></a>4.3.1 Server settings Frag-o-Matic will supply hardware for all servers. All games related to the tournament must be played on these servers. All matches will be played using the latest version of CS:GO and the official Frag-o-Matic CS:GO server config. All matches have to be played on an official Frag-o-Matic CS:GO tournament server and on the provided server number (as listed on our fom.be website, in the csgo compo section). We’ll use a standard (ESL) 5v5 pro league tournament config on a 128 tickrate server: <ul> <li>Startmoney: 0</li> <li>Maxrounds: 30</li> <li>Roundtime: 1m 55s (1.92)</li> <li>Freezetime: 12 seconds</li> <li>C4timer: 40 seconds</li> <li>Pause: 1x 5minutes per half each map.</li> <li>Overtime: MR3 - .000 startmoney</li> <li>Time during half time: 13 seconds</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="servercrash"></a>4.3.2 Server crash In the event of a server crash, after notifying a tournament admin and having them restart the the server, both teams have to re-join the same server and use the following command: <ul> <li>rcon mp_backup_restore_list_files</li> </ul> This will show you the backup files before the server crashed. 1 team captain then executes the correct file by using the following command: <ul> <li>rcon mp_backup_restore_load_file</li> </ul> Example: rcon mp_backup_restore_load_file backup_round12.txt All previous settings (score, money, armor, weapons,...) are then reset to the round before the server crashed and the match is set to paused. To continue the match, use the unpause command: <ul> <li>rcon mp_unpause_match</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="serverlag"></a>4.3.3 Server (var) lag Teams are given the time to play a warm-up match on their server before every compo match if they wish to do so. It’s not allowed to switch to another server once the compo match has been started. Test the server before the match starts. Any server problems should be reported to a tournament admin by going to the compo desk after sending an email with the information below. In the event that you experience any lag during or before a match, please note the time(s) and contact us via Discord or the Compo Desk. We'll escalate this information and, if possible, provide a solution for upcoming matches. The statement or report of (possible) lag in a match is a not valid argument in a protest. However, sending us the data above will give your team the time necessary to avoid any possible forfeits when you notify us at the compo desk after sending your email. Failure in providing us this data will not allow your team to deviate from our time schedule. We strive to provide all our servers lag free. We would like to thank you in helping us improve our servers. <a name="serverplugins"></a>4.3.4 Server plugins No extra plugins will be installed on our CS:GO servers. <a name="rconusage"></a>4.3.5 RCON usage RCON is only allowed as described in “4.1.2 Game setup”. Usage of RCON outside the game setup is penalised by receiving an instant forfeit for the team using any other RCON commands. We monitor all servers and RCON logs and will use this as evidence to hand out a match forfeit to the team using RCON outside of the game setup rules. <a name="rconusage"></a>4.3.6 Warmup servers Subject to availability, we will provide warmup servers. The settings will mirror our war servers as close as possible, but won’t be managed by the csgo team. Participants in our competition are allowed to use our warmup servers as such, to warm up, practice nade throws, practice aim,etc… We will not guarantee availability of those servers, since they will depend on the overall capacity. If warmup servers are available, they cannot ever be used for playing matches. If a match has been played on one of those servers though, the end-scores will still count. It is the responsibility of both teams the correct (assigned) server is joined. At any time, we can convert one of those servers to an official war server (In cases of need). It will at that point no longer show up as a warmup server. <a name="copyright"></a>5. Copyright Notice Copyright © 2005-2022 by E-EVENTS VZW All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher, addressed at <a href="mailto:csgo@fom.be">csgo@fom.be</a> </li> </ul>
 showsponsor(false)
 sponsorcontent
 showfiles(false)
 filescontent
 prizescontent<h1> First Place </h1> <ul> <li> <h3>525 €</h3> </li> </ul> <h1>Second Place</h1> <ul> <li> <h3>315 €</h3> </li> </ul> <h1>Third Place</h1> <ul> <li> <h3>210 €</h3> </li> </ul>
 precompo(false)
 donations0
 donationAmount0
 scheduleregistration closes at 21! please make sure all games are played on time! poules will be made and will be playable. saturday 10am we will start with the brackets semi final will be at 10am on sunday with afterwards the grand final Have fun and Good luck!
 faq
 sponsorUrl
 sponsorImg(null)
 sortTimeLabel0
 TeamA(array)
 id10265
 nameBASTARDS.AF9K
 leaderId5352
 compoId367
 pouleId1452
 notes
 withdrew(false)
 TeamB(array)
 id10375
 namePertinax eSports
 leaderId2961
 compoId367
 pouleId1452
 notes
 withdrew(false)
 AdminEdit(array)
 id(null)
 facebook_id(null)
 username(null)
 new_username(null)
 nickname(null)
 password(null)
 firstname(null)
 lastname(null)
 active(null)
 validationCode(null)
 mailValidationCode(null)
 group_id(null)
 created(null)
 modified(null)
 last_login(null)
 street(null)
 nr(null)
 bus(null)
 zip(null)
 city(null)
 country(null)
 phone(null)
 gsm(null)
 gender(null)
 birthdate(null)
 clanId(null)
 clantrust(null)
 clanjoinId(null)
 hwbudget(null)
 education(null)
 profession(null)
 hoursaweek(null)
 language(null)
 oldId(null)
 receive_newsletter(null)
 imageUrl(null)
 slug(null)
 fb_link(null)
 fb_location(null)
 CPU(null)
 MOBO(null)
 GFX(null)
 RAM(null)
 steamName(null)
 steamId(null)
 originName(null)
 lolSummonerName(null)
 Other(null)
 comment(null)
 seat_id(null)
 msg_notifications(null)
 mouseHand(null)
 deviceId(null)
 alternative_login(null)
- team(array)
 Team(array)
 id10265
 nameBASTARDS.AF9K
 leaderId5352
 compoId367
 pouleId1452
 notes
 withdrew(false)
 Compo(array)
 id367
 nameGRAND - CS:GO
 steamGameId(null)
 nrPlayersTeam5
 maxTeams64
 compoTypeId0
 nrPoules3
 nrWinnersPoule4
 compoStateId5
 eventId46
 roundDE2
 addSecondaryFinal(false)
 adminId8749
 adminId2(null)
 bannerUrl(null)
 description<h1>password to the servers: war</h1> 
 tagId31
 allowDrawInPoule1
 nrLosersToBrackets0
 pauzed0
 rulebookFrag-o-Matic 24.0 Rulebook Counter-Strike:Global Offensive (CS:GO) Introduction This is the official rulebook for the Frag-o-Matic 24.1 CS:GO competition, that will take place from the 1st until the 3rd of September 2023. These rules apply to the players throughout all stages of CS:GO competition. Failure to adhere to these rules may be penalized as outlined. It should be noted that the tournament administrators have the final word, and have the power to decide on any circumstances that are not outlined by this document, and in extreme cases may overrule the rulebook in order to preserve fair play and sportsmanship. Frag-o-Matic reserves the right to change these rules at any time. The CS:GO admin team wishes you good luck in the tournament and hopes that you have an enjoyable competition. We’ll do our utmost best to make it fair, fun and exciting for everyone involved. <a name="navigation"></a>Table of contents <ol> <li><a href="#admin">Admins and communication</a></li> <li><a href="#compo">Compo overview</a> <ol> <li><a href="#participants">Participants</a></li> <li><a href="#teamsheets">Team sheets</a></li> <li><a href="#teamnames">Team names</a></li> <li><a href="#teammanager">Team manager / coach</a></li> <li><a href="#teamcaptain">Team captain</a></li> <li><a href="#players">Players</a> <ol> <li><a href="#grstandard">Grooming standards</a></li> </ol> </li> <li><a href="#cheating">Cheating</a> <ol> <li><a href="#forbiditems">Forbidden items</a></li> </ol> </li> <li><a href="#match">Match protests and forfeit</a> <ol> <li><a href="#definitions">Definition</a></li> <li><a href="#matchprotest">Match protest rules</a></li> <li><a href="#forfeitrules">Forfeit rules</a></li> </ol> </li> <li><a href="#seeding">Seeding</a></li> </ol> </li> <li><a href="#general">General</a> <ol> <li><a href="#generalrules">General rules</a></li> <li><a href="#sanctions">Sanctions and disputes</a></li> <li><a href="#confidentiality">Confidentiality</a></li> <li><a href="#coc">Code of conduct</a></li> <li><a href="#drugsalcohol">Drugs and alcohol</a></li> <li><a href="#betting">Betting</a></li> <li><a href="#addagreement">Additional agreements</a></li> <li><a href="#streaming">Streaming, interviews and media</a> <ol> <li><a href="#broadcasting">Broadcasting</a></li> <li><a href="#matchmedia">Match media</a></li> <li><a href="#screenshots">Screenshots</a></li> </ol> </li> <li><a href="#playerchanges">Player changes</a></li> <li><a href="#prizemoney">Prize money</a></li> </ol> </li> <li><a href="#csgorules">Counter-Strike:Global Offensive rules</a> <ol> <li><a href="#tournament">Tournament structure and time schedule</a> <ol> <li><a href="#penalties">Penalties and forfeits during the time schedule</a></li> <li><a href="#compomaxteams">Compo sign-up and max teams</a></li> <li><a href="#structure">Structure</a></li> <li><a href="#gamesetup">Game setup</a></li> <li><a href="#vetosystem">Veto system</a></li> <li><a href="#compospecificrules">Compo specific rules</a></li> <li><a href="#usageofpause">Usage of pause</a></li> <li><a href="#demofiles">Demo files</a></li> </ol> </li> <li><a href="#matchprocedure">Match procedure</a> <ol> <li><a href="#maplist">Map list</a></li> <li><a href="#matchrules">Match rules</a></li> <li><a href="#clientrules">Client rules</a></li> <li><a href="#illegalscripts">Illegal scripts</a></li> <li><a href="#customfiles">Custom files</a></li> <li><a href="#colordepth">Color depth and external programs</a></li> <li><a href="#illegalprograms">Illegal programs</a></li> <li><a href="#ingameoverlay">In-game overlays</a></li> <li><a href="#techprobs">Technical problems and disconnects</a></li> </ol> </li> <li><a href="#csgoserver">CS:GO server</a> <ol> <li><a href="#serversettings">Server settings</a></li> <li><a href="#servercrash">Server crash</a></li> <li><a href="#serverlag">Server (var) lag</a></li> <li><a href="#serverplugins">Server plugins</a></li> <li><a href="#rconusage">RCON usage</a></li> <li><a href="#warmupservers">Warmup servers</a></li> </ol> </li> </ol> </li> <li><a href="#copyright">Copyright Notice</a></li> </ol> <a name="admin"></a>1. Admins and communication <hr /> Communication before the LAN: <ul> <li>General contact > <a href="mailto:csgo@fom.be">csgo@fom.be</a></li> </ul> Please email us any feedback before and after the LAN event. CS:GO admin team: <ul> <li>Dragon <ul> <li>Steam: https://steamcommunity.com/profiles/76561198244170010/</li> <li>Discord: dragon (main communication line)</li> </ul> </li> </ul> Communication during the LAN: The communication during the LAN will be through Steam, Discord or at the Compo Desk. We will be available as much as possible in the <a href="https://discord.gg/URX6v82Wmp" target="_blank">#csgo channel</a>. We will use this as a second channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #csgo channel. Discord will be our main communication channel. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compo"></a>2. Compo overview <hr /> <a name="participants"></a> 2.1 Participants Due to lack of time, we have a tight schedule. Therefore we can make the decision to force teams to only participate in 1 grand compo! We will contact the teams who are signed in for 2 grand compo’s at the moment and they will need to make a choice. When a team refuses, we will remove them from the competition to make room for other teams. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamsheets"></a> 2.2 Team sheets As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops. A rule violation by any player in a team may lead the tournament admins to sanction the entire team, even if the rest of the team was not aware of the violation. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamnames"></a> 2.3 Team names <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teammanager"></a> 2.4 Team manager / coach The team manager does not have any responsibilities. The team manager is eligible to play for his team in matches, providing he’s indicated as a “Player” on the team in the team sheet. The communication with the team will not go via the team manager, all communication will go via the team captain! Spectators are not allowed on our servers. Only tournament admins may be in spectator mode during a match. The only exception is: coaches are allowed to spectate a match using the coach's command, only if the tournament admin is notified, and thus to spectate their team only. They are obligated to use the “coach t” or “coach ct” command before the match start and aren’t allowed to join after a match has been started. If noticed that the coach is abusing this rule, the team will get punished for it (e.g. round loss, side loss or match loss). During a match, the coach may only communicate with the players during freeze-time, warm up, half-time, or during one of the 4 timeouts. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamcaptain"></a> 2.5 Team captain We consider the one who registered the team into the compo on the Frag-o-Matic website as captain! The clan leader or team captain is responsible for his team and all the players in that team. It is recommended that the team captain is fluent in English or Dutch, as he will be required to communicate with the tournament admins. The team captain must read and understand the rulebook. The team captain is responsible for ensuring his team and players adhere to the rules. Ignorance of the rules is not an excuse for rule violations. The team captain may choose at any time to nominate another player in or manager of his team as team captain for any reason. Such nominations must be reported by the team captain, either in person or in writing, to the admins before the game starts. All official communication between a competing team and the tournament admins must be conducted by the team captain. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="players"></a> 2.6 Players All players must read and understand the CSGO rulebook. Any player in violation of a rule, will be sanctioned as described in this rulebook. Each team must have five players on the match server at the match start time as indicated by the schedule, unless permission has been granted by the tournament admins to play with less than five players. Only players registered for a team in the tournament may play for that team unless otherwise discussed with the tournament admin. All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins. Players registered for a team in the tournament may not play for any other team in the same tournament. Each player has to use their nickname that is similar to the nickname he/she has entered on their fom.be account. All players for a team must be clearly identifiable in-game with a uniform tag for that team and a separate, noticeably different nickname for each player. Players may not significantly change their nickname during the tournament. Any nickname they use during the tournament must always obviously visibly correspond to their original nickname. You are not allowed to change your nickname in-game. If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning. 3 warnings are equal to a forfeit in 1 match. Player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate. Make sure your steam account is linked with your fom.be account corresponding to your nickname. Players are strictly prohibited from using any other person’s steam account for any reason whatsoever during the CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="grstandard"></a> 2.6.1 Grooming standards People participating in the CS:GO tournament are expected to normal grooming standards. You may be asked to take action if you or your clothing have a look or odor that’s offensive to other players. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="cheating"></a> 2.7 Cheating During Frag-o-Matic we won’t investigate cheaters from an external event. When we discover someone cheating during our LAN, that player and his team will be banned from the compo and the player will be also banned for the next Frag-o-Matic edition. Furthermore we will investigate reports of players cheating during other tournaments until 2 weeks before the LAN. When a player is discovered cheating during another tournament/platform 12 months before the event occurs, then that player will not be allowed to play on that edition of Frag-o-Matic within the CS:GO competition and the edition after that. If one of the following rules apply, then that player will not be allowed to compete in our tournament: Caught cheating within a tournament/platform 12 months before the start date of our event. There needs to be enough evidence for that player, that he/she was cheating and the tournament admins will judge if the evidence is valid OR if he/she was caught cheating on the following platforms: <ul> <li><a href="ts3server://ts.fom.lan">ts.fom.lan</a> - CS:GO admin channel</li> <li>Discord: <a href="https://discord.gg/MbPY2ge">https://discord.gg/MbPY2ge</a> <ul> <li>Teams are only allowed to use a uniform team name for their team.</li> <li>Teams may not change their team name during the tournament.</li> <li>Teams may not change their team in-game tag during the tournament, unless none was set.</li> <li>Duplicating team names of other teams is not allowed.</li> <li>Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.</li> <li>Team names are not allowed to be offensive.</li> <li>Please make sure your team name is filled in on your fom.be profile.</li> </ul> <ul> <li>Faceit</li> <li>Esl</li> <li>Valve (vac ban for any Counter strike: Global Offensive game)</li> <li>ESEA</li> <li>Cevo</li> </ul> </li> <li>When a player is caught selling or buying cheats. In any case the admin will have the final decision. This means that the admin will review the evidence and make the final call. If a player shows the intention of coming to our tournament to cheat and we’re provided evidence of this. Everyone from the community may send evidence to csgo@fom.be, when they suspect someone participating at Frag-o-Matic of cheating. All forms of cheating in matches are forbidden, and will result in an overall forfeit in the tournament. Possibilities for cheating in Counter-Strike:Global Offensive are, for example; all kinds of multi-hacks, wallhack, aimbot, colored models, no-recoil, no-smoke, no-flash and sound changes. All hardware or software that has an influence on the game in such a way that the essence of the game is affected are banned from this tournament. Any use of this kind of hardware will result in a disqualification of the tournament as it will be recognized as cheating. When proven that a player is not cooperating in his own ban research or is lying on purpose. He will get banned for 1 edition. You can find our banlist at http://www.fom.be/contents/view/cs-go-banlist The mentioned people in our ban list are not allowed in the CS:GO tournaments at Frag-O-Matic until the edition that’s stated there. When these people compete under a false name nonetheless or try to circumvent the rules then they will receive an extended or permanent ban. Here are some of the other examples of ways to gain advantages, this list may not be the full list but if players are unsure of certain things, they should seek to ask the tournament admins first: Flash Bang, Smoke Grenade, and Hand Grenade Bugs - it is illegal to use any flash bang, smoke grenade, or hand grenade bugs, regardless of intent. Silent Bomb Plants - ALL bomb plants must be done in a position where your opponents can hear you. There should be no rotation in players to gain money advantages throughout a match. The bomb must be planted on solid surfaces on the map, ie where an opponent can defuse from, so not up in the air or floating. Illegal Bomb Defuses - No player can defuse a bomb through any other solid object on the map, it has to be done in clear view. It is also forbidden to try to intentionally distort your hitboxes during a defuse situation to prevent an opponent from killing you in game. Walking/Boosting through walls - No player should walk, boost through walls or roofs. To do so will see your team penalized for that round. Map Exploits - Boosts that include the use of clipping are strictly forbidden. The term “Clipping” defines that when a player is boosted can see through certain parts of the map (ie over/under walls, or through solid objects on the map). If any player or team feels unsure on a new advantage they have found through their practice sessions, they are welcome to show this specific spot to the tournament team to review. Any player or team that does this will be treated to the strictest confidence as not to jeopardize your strategic advantage, however we can rule on whether it is a legal move. We strongly advise teams to give us plenty of time ahead of an event so we can review it in good time and make good judgement on it. The game admins may inspect your machine at any time throughout the event to inspect for cheats or hacks within your game files, steam cloud and anywhere on your PC or memory sticks. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="forbiditems"></a>2.7.1 Forbidden items During the lan, to prevent cheating by using external devices or items, the following items are forbidden: <ul> <li>Smartwatches; Having or carrying a smartwatch during the event, when competing in the CS:GO competition, that player will immediately be disqualified from the competition.</li> <li>Alienware Wireless Headset AW988; Visual representation of audio isn’t allowed.</li> <li>AR (augmented reality) glasses</li> <li>Hardware from the brand “Bloody” (these are mice that come with software that reduces recoil on weapons)</li> </ul> Any other electronic devices (like smartphones) that are used during a match will be considered suspicious and we’ll ask that they’re not used. If, during a match, the suspicious device is still in use; the team of the player using the device will receive a warning. After 3 warnings the team will receive a disqualification from the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="match"></a>2.8 Match protests and forfeit <a name="definitions"></a> 2.8.1 Definition A protest is a raised issue for problems that affect the match outcome; a protest may even be filed during a match for things like incorrect server settings and other related issues. A protest is the official communication between a team captain and a tournament admin. A forfeit is a lose or surrender. <a name="matchprotest"></a> 2.8.2 Match protest rules Participants are only allowed to issue a match protest before the beginning of their next match. The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “they are cheaters” will not be enough. Insults and flaming are strictly prohibited in a protest, and may result in the protest being ruled against the insulting party. <a name="forfeitrules"></a> 2.8.3 Forfeit rules A forfeit can be called for a single match or the entire competition from a competing team for their team. Only the team captain can raise a forfeit for their team. A forfeit can also be raised by an admin as a penalty for wrongdoing. For example, in most cases where a competing team doesn’t follow the time schedule. The tournament admins can always force a forfeit. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="seeding"></a>2.9 Seeding Seeding is done through an objective outlook towards data provided by all participants for every event. Every participant is required to provide us their main steam account, ESEA and/or CEVO profile, FACEit level and previous wins/achievements. The supplied data is only kept and used for one event to calculate an individual “score” based on reached rank, played time, csgo hours and historical performance/achievements from Frag-o-Matic or other tournaments. The team sum of 5 individual scores will show an objective score where the higher the score, the higher the team seeding. The tournament admins won’t seed teams higher based on any subjective opinions. If no statistical data was provided for all 5 team member, than that team will be seeded beyond top 16. <a name="general"></a>3. General <hr /> <a name="generalrules"></a> 3.1 General rules Frag-o-Matic Counter strike:Global Offensive (CS:GO) 5v5 tournament is a local area network (LAN) tournament. By competing in this tournament, teams and players accept these rules in full. Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation. In the beginning of the LAN the team captains can sit together with the admin to discuss the rules and to make adjustments if needed. The decisions are made by the admin. If you have any issues with the rules, you can explain this by sending an email to <a href="mailto:csgo@fom.be">csgo@fom.be</a> up to one week before the start of the event. Clarification of any point in the rules is available from the tournament admins at any time during the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="sanctions"></a>3.2 Sanctions and disputes Sanctions and disputes will be resolved by the main tournament admin. The admin’s decision on any sanction or dispute is final. Abusive behavior towards the Frag-o-Matic staff, tournament admins or opponents at any time during the tournament is unacceptable and will be punished with warnings. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="confidentiality"></a>3.3 Confidentiality The content of protests, support communication, discussions or any other correspondence with tournament officials and administrators are considered as strictly confidential. The publication of such material is prohibited. If the contents has been shared without consent then this could lead to a team’s disqualification. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="coc"></a>3.4 Code of conduct Any form of aggression<a href="#coc_aggression">*</a> (both verbally and physically) will not be tolerated. Any and all physical aggression will be sanctioned with an immediate disqualification by that person or team performing the physical act (both actioned and reactioned). Any verbal aggression will be sanctioned by a time-out for that person or team. A time-out is either set in time (hours/day) or in amount of matches when a player or team is not allowed to participate in the CS:GO competition. Any situation that is about to escalate should be dealt with in a calm and diplomatic manner. An audience with any Frag-o-Matic crew member (CS:GO admin or Frag-o-Matic team leaders) can always be called for at any time during the event. Keep in mind that this audience can not be used to waste time or get a time advantage. At any point, the CS:GO tournament admins can decide to continue with the competition with or without consent from either players or other Frag-o-Matic staff. In the event when a single player or more are accused of cheating, the event will continue nonetheless. Evidence will be presented to the tournament admins and a call will be made at a later stage of the event. This rule is set to not cause any delays and have the situation under control. Any player(s) or team(s) ignoring this rule will receive a forfeit. Any player or team ignoring a CS:GO admin will be sanctioned with a warning. 3 warnings are equal to a forfeit of 1 match. <a name="coc_aggression"></a>*A form of aggression is described as: <ul> <li>Instrumental aggression -- Aggression aimed at obtaining an object, privilege or space with no deliberate intent to harm another person. Typical of participants wanting to get ahead of the competition with lies, anger, bullying, criticizing other people behind their backs, leaving others out of a group or otherwise ostracizing them, turning people against each other, dismissing the opinions of others (passive aggression).</li> <li>Hostile aggression -- Aggression intended to harm another person, such as hitting/kicking/biting someone (active aggression). Threatening to beat up someone (nonverbal intimidation). Sending threatening messages through emails, phone calls, or social media, or making threats against someone's life, shouting, and swearing (verbal hostility). Breaking someone's computer, destroying someone's cell phone, or other forms of vandalism (destruction of property).</li> <li>Relational aggression -- A form of hostile aggression that does damage to another's peer relationships, as in social exclusion, gossiping or rumor spreading. Examples: Arguments within a team after a lose that lead to a verbal fight.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="drugsalcohol"></a>3.5 Drugs and alcohol To play a match under the influence of any drugs or performance enhancers is strictly prohibited, and may be punished with exclusion from the tournament. If an admin finds that a player is not capable of competing in the competition because of intoxication, the admin can exclude that person from the entire tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="betting"></a>3.6 Betting Betting on any match in the CS:GO tournament is strictly forbidden. <a name="addagreement"></a>3.7 Additional agreements Teams may be required to play any match on the stage. If so, teams will be notified at least 20 minutes prior to the start time of that match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="streaming"></a>3.8 Streaming, interviews and media <a name="broadcasting"></a>3.8.1 Broadcasting Frag-o-Matic reserves the right to broadcast any match or demo, teams may not refuse such broadcasts. All forms of client side game broadcasting are NOT allowed. Frag-o-Matic participants are not allowed to watch a local GOTV if a CS:GO server broadcasts a game. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchmedia"></a>3.8.2 Match media All match media (screenshots, demos, etc.) must be kept until the end of the event. Faking or manipulating match media is forbidden and will result in exclusion from the tournament. Match media should be named clearly based on what it is. It is not possible to file a protest to complain about bad match media naming. However if a tournament admin is hindered in their work because of bad match media naming, then a tournament admin will give a warning. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="screenshots"></a>3.8.3 Screenshots The admin can ask for screenshots of every game on any moment during the event. When he does this, the team leader has 15 minutes time to deliver the screenshot to the admin. A screenshot of the scoreboard at the end of each half must be taken. When this is not done by a team it can result in a lost match when one of the other teams complains about a score. An RCON status screenshot must be taken: <ul> <li>at the beginning of the match</li> <li>in case of a server/player change</li> <li>if a player reconnects</li> </ul> RCON status screenshots made with the help of programs like HLSW etc. are not sufficient. In order to take an RCON status you have to use the console command “rcon status” (don’t forget to enter your RCON password) and take a screenshot of that. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="playerchanges"></a>3.9 Player changes Teams are permitted to substitute players (only with another player not active in the CS:GO competition) during pauses and between rounds, if they have permission from the tournament admin. Consent for substitutions must be obtained from the tournament admins, and substitute players must be registered for that team in the tournament. You can make this clear to the admin by using the contact information in section ‘Admins and communication’. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="prizemoney"></a>3.10 Prize money When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="csgorules"></a> 4. Counter-Strike:Global Offensive rules <hr /> <a name="tournament"></a>4.1 Tournament structure and time schedule Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. On Saturday and Sunday, teams must be present at 10:00 (AM) and ready to start playing the rest of their scheduled matches. It can be the case that the tournament admins decide to start earlier or end later, but this will be communicated (to all team captains). An exact time schedule will be provided on our fom.be website for all teams to follow. Each match will have a start time on which the game needs to be started. The team(s) that are responsible where the start time has not been met will receive a forfeit for that match. Whether or not this rule will be applied, is the decision of a tournament admin. The schedule for the tournament may be subject to change at any time. Matches may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice. Games will not be rescheduled to an earlier time in the same day if either of the teams have not yet played a game on that day without the consent of both team captains. Where possible the tournament admins will notify any teams involved in a rescheduled game of the new match start time at least one hour before the new start time. In the event a match is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible. If there’s insufficient time to complete a match, the tournament admins may at any time declare one team as the winner, if that team holds a clear advantage in that match. It is the responsibility of the tournament admins to decide whether a team holds a clear advantage. This rule will only be used in the emergency when the remaining event time is a factor. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="penalties"></a>4.1.1 Penalties and forfeits during the time schedule If 1 or more teams are still playing a match in a previous stage or if 1 team is late and doesn’t start playing their match in the stage where they are; Teams are offered 30 minutes of grace time in both circumstances, after 30 minutes warnings are handed out: After 30 minutes that team, who’s still not playing their scheduled match, will receive a 1st warning from a tournament admin. A notice via our csgo channel on discord and if the team is present and found at their seat they’ll be warned in person as well. A second warning is given in the same manner 5 minutes after the first warning. A third and final warming is given in the same way 5 minutes after that. 5 minutes after the final warning the team who received 3 warnings will receive 1 game loss for their match in the next round. In case of a bo3 in the next round, a bo2 will be played with one win to the team that was on time. If after 15 minutes the team with 3 warnings and one loss in the next round is still not playing, they’ll receive a forfeit from an admin. In case of a bo1 (in the lower bracket for example) we won’t lose any more time and a forfeit will be forced. The forfeit is applied on our fom.be website and a notice is given on Discord in our csgo channel. The tournament admins will keep a record of the warnings and will communicate this to the compo desk. As mentioned in our general rulebook; Non-acceptable excuses for a delay: “We want to eat” isn’t a valid excuses for starting an argument at the compo desk. As a note, we ask that teams only take a maximum of 15 minute breaks in between games and matches to avoid any penalties. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compomaxteams"></a>4.1.2 Compo sign-up and max teams All compo sign-ups are done via our fom.be website. Some rules are already explained in our general rulebook. Any team that is not “full”, meaning the team doesn’t consist of minimum 5 players, will be removed from the compo sign-up one hour before the start of the competition. We allow a maximum 64 teams to register to our CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="structure"></a>4.1.3 Structure Our CS:GO tournament will use a poule system and 3 double elimination brackets (pro, semi-pro and fun). Each poule will consist out of 3-4 teams who will compete against each other to make it into the brackets. Each team within the poule needs to play against any other team within its poule. Following the poule stage, the 2 winners from each poule will advance to a pro bracket, the last 2 teams from each poule will advance to a semi-pro bracket and <s>other teams will proceed to the fun bracket</s>. Our compo structure will use the following setup for pro, semi-pro and fun: <ul> <li>Groupstage > BO1 (best of 1)</li> <li>Upper Bracket > BO3 (best of 3)</li> <li>Lower Bracket > BO1 (best of 1)</li> <li>Pro & semi-pro bracket: <ul> <li>Semi-final (Finals in lower bracket) > BO3 (best of 3)</li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> </li> <li><s>Fun bracket:</s> <ul> <li><s>Semi-final (Finals in lower bracket) > BO1 (best of 1)</s></li> </ul> </li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> When 2 teams have the same amount of points after the poules we will look at the following criteria in order: <ul> <li>The match between the 2 teams</li> <li>The won rounds total</li> <li>The lost rounds total</li> <li>Seeding</li> </ul> We can also look at other criteria if we feel that it's necessary (also cooperation). The admin is allowed to overrule these criteria. If there’s not enough data to validate a criteria the admin can chose to ignore it. A tournament admin can decide to change some matches from BO3 to BO1 or visa versa when needed. (For example: no time to play a BO3). <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="gamesetup"></a>4.1.4 Game setup Matches will be played 5on5. Playing with fewer than five players in any match is only allowed with permission from the tournament admins. Before a match starts, both teams must state that they are ready to start the match. The must do this by having one team member typing ‘ready’ in server chat. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated. Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug. You’ll need to use the following match setup to play every game: <ul> <li>2 teams join the server that is assigned to them on our fom website.</li> <li>The team captains can use the RCON password “godmode” to follow the next steps : <ul> <li>Don’t forget to do ‘cl_mute_enemy_team 0’</li> <li>Change the map to de_mirage (rcon changelevel de_mirage)</li> <li>Load the Frag-o-Matic config (rcon exec fom5on5.cfg)</li> <li>Start a knife round on de_mirage (optional). The winner of this knife round can decide who team A is. Start the map veto process (Veto is explained under ‘Veto system’’).</li> <li>After the Veto the team captain needs to change the map to the first map of Team A (in a BO3) or the single map that was chosen (in a BO1) (rcon changelevel ‘mapname’)</li> <li>Load the fom5on5.cfg again on this map. (rcon exec fom5on5.cfg)</li> <li>After this the teams do another knife round to decide which team will start on which side of the map. The winner of the knife round decides which side they want to start on and that team will also start the match. (rcon mp_restartgame 1)</li> </ul> </li> </ul> If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server can be paused at the end of the current round (see rule ‘Usage of pause’ function) by one of the teams. The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed. If a player/substitute doesn’t connect within that time, then the match is continued 4on5, or 4on4 if the opposing team agrees and the tournament admins are informed. There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="vetosystem"></a>4.1.5 Veto system Our veto process is the next step after playing a knife round, as described in ‘Game setup’. The map(s) chosen to be played in each BO1 and BO3 are done via elimination (i.e. veto). Where ‘team 1 = A’ and ‘team 2 = B’, with A being decided by the winner of the knife round. Teams can also decide who team A/B is without playing a knife round. The maps you don’t want to play as a team, should be the maps that you veto during this process. The veto process needs to be done in server chat. VETO rules best-of-1: ABABAB veto. The map pool exists out of 7 maps. 6 maps are vetoed during this process, 3 maps for each team. The remaining map is the map played in the best-of-1 match. VETO rules best-of-2: ABAB veto AB play. The map pool exists out of 7 maps. 4 maps are vetoed during this process, 2 maps for each team. Out of the 3 remaining maps, 1 team each gets to decide a map to play on. VETO rules best-of-3: A/B veto, A/B play and A/B veto. The map pool exists out of 7 maps. 4 maps are eliminated, and 3 maps are selected to play. Each team needs to veto a map, followed by each team choosing a map and again each team vetoing a map. The remaining map is the third map that needs to be played if both teams win a map. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compospecificrules"></a>4.1.6 Compo specific rules All matches in the group stage are played MR15. All matches in the brackets are played MR15 (meaning, 16 rounds won = game win). In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games are best of three (BO3) in the bracket, 3 maps are decided by veto. The grand final is a best of three (BO3) with map advantage! When in the brackets a game is tied an overtime needs to be played. The overtime will be played MR3 with 10.000$ start money. For the start of the overtime teams will stay on the side which they played the previous half on, during halftime sites will be swapped. Teams will continue to play overtimes until a winner has been found. We have our own special breed of bracket seeding. For more information please contact us in advance. This bracket seeding is law. Obey it. All CS:GO players can only use our ts.fom.lan (local) teamspeak for voice communication. Teams are only allowed to have 5 players + 1 coach in their teamspeak channel whilst in a competition match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="usageofpause"></a>4.1.7 Usage of pause Pauses may be taken for any reason. Teams are permitted 3 pauses per side in each match. Each pause having a maximum duration of 5 minutes, unless authorised by an admin to take a longer pause (in case of technical difficulties, for example). After a “pause”-event, an “unpause“-command needs to be done. Teams can’t unpause without the consent of the other team. Pauses may only be activated at the start of the next round during freeze time. So make sure you tell the other team before round end (in all-chat), that your team will take a pause in the next freeze time. Usage: Type the following commands in console, to activate and deactivate the pause event. Pause = rcon mp_pause_match Unpause = rcon mp_unpause_match Illegal usage: DON’T USE = sv_pause If a team does use sv_pause, they have to surrender 1 round. (by all team members typing “kill” in console) <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="demofiles"></a>4.1.8 Demo files GoTV demos must be active for each match to be recorded. It’s the responsibility of (both) team captains to ensure that GoTV is recording. If this isn’t the case, the tournament admins will be forced to make calls without a recording when a dispute occurs. It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A knife round is part of a match and should be recorded. At least one of the players must be able to upload the knife round on admin request. Protests regarding missing knife rounds are not valid. In general, defective or manipulated demos will be treated as missing demos. If the demo is incomplete, as decided by the admin, it also will be treated as missing demo. If a protest is opened for a match, all match media need to be kept until the end of the event. Demos can only be requested up to a maximum of 30 minutes after a match via the admin. A demo request must state which teams were playing, the name(s) of the map(s) the match(es) was/were played on, the time of the match(es) and the server IP address(es). If a player or a team illegally aborts the match, they lose their right to demand demos. Recording demos is recommended. Our servers will likely record demos for every match but these are only used when there is doubt about a decision the admin has to make. It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.2 Match procedure <a name="maplist"></a>4.2.1 Map list Only the following maps are allowed to be played on during the competition: <ul> <li>de_ancient</li> <li>de_anubis</li> <li>de_inferno</li> <li>de_mirage</li> <li>de_nuke</li> <li>de_overpass</li> <li>de_vertigo</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchrules"></a>4.2.2 Match rules <ul> <li>Diffusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.</li> <li>Throwing grenades/flash bangs/smokes across walls in maps is allowed.</li> <li>Boosting is not considered a bug.</li> <li>Buying and using multiple grenades is allowed but with a max of 2 flash bangs.</li> <li>Multiple grenades are allowed but max 2 flash bangs</li> <li>Bugs on the map must be checked before the match begins. Any protest after the match about map bugs will be ignored.</li> <li>If a player loses connection before the first kill, the match can be restarted. If this happens after the first kill, the server can be paused and have the disconnected player reconnect. Matches won’t be restarted due to disconnections.</li> <li>If you want a player change (sub) during the match, inform the opponent and the compo admins before the match begins!</li> <li>To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.</li> <li>Climbing with help of teammates is allowed in general.</li> <li>Throwing grenades inside walls is not allowed.</li> <li>Self-kills are strictly forbidden, unless an admin forces you to do this as a sanction for disobeying any rules.</li> <li>Bomb planting in a way it can’t be reached is forbidden.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="clientrules"></a>4.2.3 Client rules The admin is allowed to take over your computer before, during and after a game and have a look. Without the pc’s owner in question nearby, the person in question can appoint someone to stay with the admin to make sure no privacy issues are violated. Any trace evidence of cheats found on a player’s computer – even if such discovery took place outside of a game – can lead to exclusion from any competition. For NVIDIA graphics card users: The use of Ambient Occlusion is strictly forbidden. If you are caught using this setting, this will result in a direct loss of the match. Getting caught for a 2nd time will result in removal from the tournament. This setting can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings. The following commands are forbidden: <ul> <li>mat_hdr_enabled</li> </ul> The following startparameters are forbidden: <ul> <li>+mat_hdr_enabled 0/1</li> <li>+mat_hdr_leven 0/1/2</li> </ul> In your game client cfg-folder you’re only allowed to have config files. Pictures, demos, screenshots and zipped files are forbidden. All other configuration changes are allowed as long as they do not give an unfair edge or advantage comparable to cheating. The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary. Boosting through walls/ceilings/ground, sky walking, map swimming, floating and sharking are all forbidden. To throw grenades inside walls is not allowed. Above walls and roofs is allowed. To plant the bomb in a way that it cannot be reached is forbidden. Places that can be reached with help of a team mate are allowed as long as they are visible. Violating this rule will result in tournament administrators intervention. Changing graphic settings to irregular values can be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalscripts"></a>4.2.4 Illegal scripts In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts: <ul> <li>Stop Shoot scripts [Use or Awp scripts]</li> <li>Center view scripts</li> <li>Turn scripts [180° or similar]</li> <li>No Recoil scripts</li> <li>Burst fire scripts</li> <li>Rate changers (Lag scripts)</li> <li>FPS scripts</li> <li>Anti flash scripts or binding (snd_* bindings)</li> <li>Bunnyhop scripts</li> <li>Stop sound scripts</li> <li>Following Commands/CVars are forbidden</li> <li>+weapon_recoil_model 0 (Startparameter)</li> </ul> The following CVAR values must be used: <ul> <li>cl_bobcycle 0.98 (First Time->Warning)</li> </ul> If there are more than one player who used a wrong client setting, the match will be deleted. Exception: cl_bobcycle Using illegal scripts will be penalized if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized. The use of No-Flash and No-Recoil bindings/scripts in any and all forms will be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="customfiles"></a>4.2.5 Custom files The HUD can be changed as long as no information are deleted or falsified which are available in the standard HUD. If the HUD is changed it has to be readable. If an admin is hindered in his work due to an unreadable HUD, penalty points may be assigned. Protests or supports which adhere to this rule will not be admitted and are rejected directly. Apart from the HUD and the GUI no custom files are allowed. This also includes custom models, changed textures or sounds (volume, soundscapes) are forbidden. <a name="colordepth"></a>4.2.6 Color depth and external programs The usage of a color depth of 16bit is not allowed. The usage of external programs (ex. SweetFX, A3D,...) are not allowed to enhance vision. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalprograms"></a>4.2.7 Illegal programs Changing the game graphics or textures with the help of video card drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. NVidia SLI Display, Riva tuner Overlays) is illegal. Failure to comply with this rule will result in a punishment for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized. If you play with ambient occlusion, it will be punished as cheating!! Punishment will be given regardless of whether the script/binding is executed via external hardware or software. Also binding any snd_ command is forbidden. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="ingameoverlay"></a>4.2.8 In-game overlays All In-Game overlays – provided by the game itself – except the following are forbidden: <ul> <li>net_graph 0</li> <li>net_graph 1</li> <li>cl_showpos 1</li> <li>cl_showfps 1</li> <li>cl_showdemooverlay 1 / -1</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="techprobs"></a>4.2.9 Technical problems and disconnects If a disconnection occurs the game should automatically reconnect. When this doesn’t work, a tournament admin will decide what to do. The tournament admin will make a call in every possible scenario regarding the severity of the problem and how to deal with it. But, the following guidelines are in place in the event of a disconnect: <ul> <li>In the case where Frag-o-Matic is responsible for the disconnect, the round needs to be restored to the start of the round where the disconnection happened. I.e. follow the steps as described under “4.3.2 Server crash”.</li> <li>When a player is responsible for his own disconnect, the team with 4 players can decide to continue to play 4v5 or use a pause as described in “4.1.6 Usage of pause”.</li> <li>The disconnected player can then reconnect to the match. If that player fails to reconnect, then the match will continue 4v5.</li> <li>If another Frag-o-Matic participant is responsible for causing a problem, then the match needs to be paused and a tournament admin needs to be notified to make a call on what to do.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.3 CS:GO server <a name="serversettings"></a>4.3.1 Server settings Frag-o-Matic will supply hardware for all servers. All games related to the tournament must be played on these servers. All matches will be played using the latest version of CS:GO and the official Frag-o-Matic CS:GO server config. All matches have to be played on an official Frag-o-Matic CS:GO tournament server and on the provided server number (as listed on our fom.be website, in the csgo compo section). We’ll use a standard (ESL) 5v5 pro league tournament config on a 128 tickrate server: <ul> <li>Startmoney: 0</li> <li>Maxrounds: 30</li> <li>Roundtime: 1m 55s (1.92)</li> <li>Freezetime: 12 seconds</li> <li>C4timer: 40 seconds</li> <li>Pause: 1x 5minutes per half each map.</li> <li>Overtime: MR3 - .000 startmoney</li> <li>Time during half time: 13 seconds</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="servercrash"></a>4.3.2 Server crash In the event of a server crash, after notifying a tournament admin and having them restart the the server, both teams have to re-join the same server and use the following command: <ul> <li>rcon mp_backup_restore_list_files</li> </ul> This will show you the backup files before the server crashed. 1 team captain then executes the correct file by using the following command: <ul> <li>rcon mp_backup_restore_load_file</li> </ul> Example: rcon mp_backup_restore_load_file backup_round12.txt All previous settings (score, money, armor, weapons,...) are then reset to the round before the server crashed and the match is set to paused. To continue the match, use the unpause command: <ul> <li>rcon mp_unpause_match</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="serverlag"></a>4.3.3 Server (var) lag Teams are given the time to play a warm-up match on their server before every compo match if they wish to do so. It’s not allowed to switch to another server once the compo match has been started. Test the server before the match starts. Any server problems should be reported to a tournament admin by going to the compo desk after sending an email with the information below. In the event that you experience any lag during or before a match, please note the time(s) and contact us via Discord or the Compo Desk. We'll escalate this information and, if possible, provide a solution for upcoming matches. The statement or report of (possible) lag in a match is a not valid argument in a protest. However, sending us the data above will give your team the time necessary to avoid any possible forfeits when you notify us at the compo desk after sending your email. Failure in providing us this data will not allow your team to deviate from our time schedule. We strive to provide all our servers lag free. We would like to thank you in helping us improve our servers. <a name="serverplugins"></a>4.3.4 Server plugins No extra plugins will be installed on our CS:GO servers. <a name="rconusage"></a>4.3.5 RCON usage RCON is only allowed as described in “4.1.2 Game setup”. Usage of RCON outside the game setup is penalised by receiving an instant forfeit for the team using any other RCON commands. We monitor all servers and RCON logs and will use this as evidence to hand out a match forfeit to the team using RCON outside of the game setup rules. <a name="rconusage"></a>4.3.6 Warmup servers Subject to availability, we will provide warmup servers. The settings will mirror our war servers as close as possible, but won’t be managed by the csgo team. Participants in our competition are allowed to use our warmup servers as such, to warm up, practice nade throws, practice aim,etc… We will not guarantee availability of those servers, since they will depend on the overall capacity. If warmup servers are available, they cannot ever be used for playing matches. If a match has been played on one of those servers though, the end-scores will still count. It is the responsibility of both teams the correct (assigned) server is joined. At any time, we can convert one of those servers to an official war server (In cases of need). It will at that point no longer show up as a warmup server. <a name="copyright"></a>5. Copyright Notice Copyright © 2005-2022 by E-EVENTS VZW All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher, addressed at <a href="mailto:csgo@fom.be">csgo@fom.be</a> </li> </ul>
 showsponsor(false)
 sponsorcontent
 showfiles(false)
 filescontent
 prizescontent<h1> First Place </h1> <ul> <li> <h3>525 €</h3> </li> </ul> <h1>Second Place</h1> <ul> <li> <h3>315 €</h3> </li> </ul> <h1>Third Place</h1> <ul> <li> <h3>210 €</h3> </li> </ul>
 precompo(false)
 donations0
 donationAmount0
 scheduleregistration closes at 21! please make sure all games are played on time! poules will be made and will be playable. saturday 10am we will start with the brackets semi final will be at 10am on sunday with afterwards the grand final Have fun and Good luck!
 faq
 sponsorUrl
 sponsorImg(null)
 sortTimeLabel0
 Leader(array)
 id5352
 facebook_id(null)
 usernamekenney_trz@hotmail.com
 new_username(null)
 nicknamePoederbaas
 password7c3194ddd6ec61d98a0c939f9d71ed4d68213cfe
 firstnameKenney
 lastnamevan ransbeeck
 active1
 validationCodeetatebymuj
 mailValidationCode
 group_id5
 created2015-01-07 19:14:44
 modified2025-01-21 18:40:05
 last_login2025-01-24 22:41:50
 streetvredestraat
 nr1
 bus2
 zip2845
 cityniel
 countryBE
 phone
 gsm0476367106
 genderm
 birthdate1990-04-03
 clanId4445
 clantrust1
 clanjoinId(null)
 hwbudget> 2500 EUR
 educationmaster (other)
 professionother
 hoursaweek10
 languagedut
 oldId(null)
 receive_newsletter(false)
 imageUrlupload/users/Poederbaas_41804908_2010852158953583_7389267503626584064_n.jpg
 slugkenaii
 fb_link
 fb_location
 CPURyzen 9 7900X
 MOBOAORUS EXTREME X670
 GFXRTX 4090
 RAM32GB 6400Mhz
 steamNameKannonen voer
 steamId76561198156523884
 originNameKenaiiR36
 lolSummonerName
 Otherwatercooled system custom loop
 comment
 seat_id(null)
 msg_notifications(true)
 mouseHandright
 deviceId
 alternative_login(false)
 Poule(array)
 id1452
 compoId367
 namePoule A
 Members(array)
 0(array)
 id5352
 facebook_id(null)
 usernamekenney_trz@hotmail.com
 new_username(null)
 nicknamePoederbaas
 password7c3194ddd6ec61d98a0c939f9d71ed4d68213cfe
 firstnameKenney
 lastnamevan ransbeeck
 active1
 validationCodeetatebymuj
 mailValidationCode
 group_id5
 created2015-01-07 19:14:44
 modified2025-01-21 18:40:05
 last_login2025-01-24 22:41:50
 streetvredestraat
 nr1
 bus2
 zip2845
 cityniel
 countryBE
 phone
 gsm0476367106
 genderm
 birthdate1990-04-03
 clanId4445
 clantrust1
 clanjoinId(null)
 hwbudget> 2500 EUR
 educationmaster (other)
 professionother
 hoursaweek10
 languagedut
 oldId(null)
 receive_newsletter(false)
 imageUrlupload/users/Poederbaas_41804908_2010852158953583_7389267503626584064_n.jpg
 slugkenaii
 fb_link
 fb_location
 CPURyzen 9 7900X
 MOBOAORUS EXTREME X670
 GFXRTX 4090
 RAM32GB 6400Mhz
 steamNameKannonen voer
 steamId76561198156523884
 originNameKenaiiR36
 lolSummonerName
 Otherwatercooled system custom loop
 comment
 seat_id(null)
 msg_notifications(true)
 mouseHandright
 deviceId
 alternative_login(false)
 TeamUser(array)
 id21408
 teamId10265
 userId5352
 date2023-08-17 00:01:25
 seatNrI-5
 registered2
 1(array)
 id8720
 facebook_id(null)
 usernamekenny.vermunicht87@gmail.com
 new_username(null)
 nicknameKyo
 passwordd6ac535c345b5e75fdc00fd9e00e9d45eee5018e
 firstnameKenny
 lastnameVermunicht
 active1
 validationCodeutuvuryzyn
 mailValidationCode
 group_id5
 created2018-12-26 18:53:34
 modified2023-11-23 12:35:14
 last_login2024-12-19 20:07:23
 streetHet Aarkeland
 nr4
 bus
 zip5328 GR
 cityRossum
 countryNL
 phone
 gsm
 genderm
 birthdate1987-05-29
 clanId4445
 clantrust1
 clanjoinId(null)
 hwbudget
 education
 profession
 hoursaweek
 languagedut
 oldId(null)
 receive_newsletter(true)
 imageUrlupload/users/Kyo_tumblr_25b8be3facbf3fe0c3657f7c8a963625_bacd9861_640.gif
 slugkyo
 fb_link
 fb_location
 CPUIntel Core i7-9700K
 MOBOAorus Z370 ultra gaming 2.0
 GFXRTX 2080ti
 RAM32 GB DDR4-3200
 steamName(null)
 steamId(null)
 originName
 lolSummonerName
 Otherwatercooled system custom loop
 comment
 seat_id(null)
 msg_notifications(true)
 mouseHandright
 deviceId
 alternative_login(false)
 TeamUser(array)
 id21411
 teamId10265
 userId8720
 date2023-08-17 00:02:00
 seatNrI-7
 registered2
 2(array)
 id5896
 facebook_id(null)
 usernameDylanwolfframm@gmail.com
 new_username(null)
 nicknameDeurneWest
 password001f0ef50dcb3ff11ace1ce2610e3cc039a3e3f2
 firstnameDylan
 lastnameWolfframm
 active1
 validationCodeneqygazamu
 mailValidationCode
 group_id5
 created2015-08-03 21:01:09
 modified2023-07-11 22:50:54
 last_login2025-01-12 15:16:51
 streetBeemdenlaan
 nr46
 bus
 zip2900
 citySchoten
 countryBE
 phone
 gsm0468576026
 genderm
 birthdate1994-06-02
 clanId4445
 clantrust0
 clanjoinId(null)
 hwbudget
 education
 profession
 hoursaweek
 languageeng
 oldId(null)
 receive_newsletter(true)
 imageUrl
 slugmythz-1
 fb_link
 fb_location
 CPU
 MOBO
 GFX
 RAM
 steamNameLucy
 steamId76561198001408333
 originName
 lolSummonerNamejanet42069
 Other
 comment
 seat_id(null)
 msg_notifications(true)
 mouseHandright
 deviceId
 alternative_login(false)
 TeamUser(array)
 id21412
 teamId10265
 userId5896
 date2023-08-17 00:02:11
 seatNrI-4
 registered2
 3(array)
 id7769
 facebook_id(null)
 usernamedaantje220@hotmail.com
 new_username(null)
 nicknameRupel
 password2af0052c12c4fb42518bf86bec4cfaa4dd0cd878
 firstnameDaan
 lastnameWaegeman
 active1
 validationCodeezahaduduh
 mailValidationCode
 group_id5
 created2017-08-11 13:43:16
 modified2023-12-10 01:31:04
 last_login2024-02-19 11:54:42
 streetVoorhout
 nr72
 busc
 zip9190
 cityStekene
 countryBE
 phone(null)
 gsm
 genderm
 birthdate1994-01-11
 clanId4445
 clantrust0
 clanjoinId(null)
 hwbudget
 education
 profession
 hoursaweek
 languagedut
 oldId(null)
 receive_newsletter(false)
 imageUrlupload/users/Rupel_FullColor_TransparentBg_1280x1024_72dpi.png
 slugrupel
 fb_link
 fb_location
 CPU
 MOBO
 GFX
 RAM
 steamName(null)
 steamId(null)
 originName
 lolSummonerName
 Other
 comment
 seat_id(null)
 msg_notifications(true)
 mouseHandright
 deviceId
 alternative_login(false)
 TeamUser(array)
 id21413
 teamId10265
 userId7769
 date2023-08-17 00:02:19
 seatNrG-35
 registered1
 4(array)
 id5690
 facebook_id(null)
 usernamekoning_m@live.be
 new_username(null)
 nicknameKM.
 password92d9222ffe54c06bf17f67befb5ea4bfb0875f13
 firstnameMathias
 lastnameFieberitz
 active1
 validationCodesamunadehe
 mailValidationCode
 group_id5
 created2015-06-30 19:10:19
 modified2024-02-04 15:28:28
 last_login2025-01-20 16:38:20
 streetWulpstraat
 nr21
 bus10
 zip2170
 cityMerksem
 countryBE
 phone(null)
 gsm0498037204
 genderm
 birthdate1991-03-03
 clanId4445
 clantrust0
 clanjoinId(null)
 hwbudget1500 - 2500 EUR
 educationhigh school
 professionother
 hoursaweek
 languagedut
 oldId(null)
 receive_newsletter(false)
 imageUrlupload/users/KM._Screenshot2023-01-03at21-41-25DoesSmokingWeedActuallyMakeYouDumb.png
 slugkoningm
 fb_link
 fb_location
 CPU
 MOBO
 GFX
 RAM
 steamName♔M.
 steamId76561197990700048
 originNameBelgium
 lolSummonerNamezehKing
 Other
 comment
 seat_id(null)
 msg_notifications(true)
 mouseHandright
 deviceId
 alternative_login(false)
 TeamUser(array)
 id21457
 teamId10265
 userId5690
 date2023-08-17 20:43:48
 seatNrG-36
 registered1
 5(array)
 id4547
 facebook_id(null)
 usernameliam.teunen@hotmail.com
 new_username(null)
 nicknameyookes
 password8296a862674200e415a920750f9c74b219464835
 firstnameLiam
 lastnameTeunen
 active1
 validationCodemuhevaqyga
 mailValidationCode
 group_id9
 created2014-07-07 22:40:06
 modified2024-08-26 20:56:57
 last_login2025-01-24 09:04:04
 streetPoolsterhof
 nr60
 bus
 zip3318RM
 cityDordrecht
 countryNL
 phone
 gsm0648547878
 genderm
 birthdate1995-12-07
 clanId4445
 clantrust0
 clanjoinId(null)
 hwbudget
 education
 profession
 hoursaweek
 languagedut
 oldId(null)
 receive_newsletter(true)
 imageUrl
 slugyookes
 fb_link
 fb_location
 CPU
 MOBO
 GFX
 RAM
 steamName(null)
 steamId(null)
 originName
 lolSummonerNameyookes
 Other
 commentv25.1 csgo
 seat_id(null)
 msg_notifications(true)
 mouseHandright
 deviceId
 alternative_login(false)
 TeamUser(array)
 id21493
 teamId10265
 userId4547
 date2023-08-18 13:20:47
 seatNrI-2
 registered2
- compo(array)
 Compo(array)
 id367
 nameGRAND - CS:GO
 steamGameId(null)
 nrPlayersTeam5
 maxTeams64
 compoTypeId0
 nrPoules3
 nrWinnersPoule4
 compoStateId5
 eventId46
 roundDE2
 addSecondaryFinal(false)
 adminId8749
 adminId2(null)
 bannerUrl(null)
 description<h1>password to the servers: war</h1> 
 tagId31
 allowDrawInPoule1
 nrLosersToBrackets0
 pauzed0
 rulebookFrag-o-Matic 24.0 Rulebook Counter-Strike:Global Offensive (CS:GO) Introduction This is the official rulebook for the Frag-o-Matic 24.1 CS:GO competition, that will take place from the 1st until the 3rd of September 2023. These rules apply to the players throughout all stages of CS:GO competition. Failure to adhere to these rules may be penalized as outlined. It should be noted that the tournament administrators have the final word, and have the power to decide on any circumstances that are not outlined by this document, and in extreme cases may overrule the rulebook in order to preserve fair play and sportsmanship. Frag-o-Matic reserves the right to change these rules at any time. The CS:GO admin team wishes you good luck in the tournament and hopes that you have an enjoyable competition. We’ll do our utmost best to make it fair, fun and exciting for everyone involved. <a name="navigation"></a>Table of contents <ol> <li><a href="#admin">Admins and communication</a></li> <li><a href="#compo">Compo overview</a> <ol> <li><a href="#participants">Participants</a></li> <li><a href="#teamsheets">Team sheets</a></li> <li><a href="#teamnames">Team names</a></li> <li><a href="#teammanager">Team manager / coach</a></li> <li><a href="#teamcaptain">Team captain</a></li> <li><a href="#players">Players</a> <ol> <li><a href="#grstandard">Grooming standards</a></li> </ol> </li> <li><a href="#cheating">Cheating</a> <ol> <li><a href="#forbiditems">Forbidden items</a></li> </ol> </li> <li><a href="#match">Match protests and forfeit</a> <ol> <li><a href="#definitions">Definition</a></li> <li><a href="#matchprotest">Match protest rules</a></li> <li><a href="#forfeitrules">Forfeit rules</a></li> </ol> </li> <li><a href="#seeding">Seeding</a></li> </ol> </li> <li><a href="#general">General</a> <ol> <li><a href="#generalrules">General rules</a></li> <li><a href="#sanctions">Sanctions and disputes</a></li> <li><a href="#confidentiality">Confidentiality</a></li> <li><a href="#coc">Code of conduct</a></li> <li><a href="#drugsalcohol">Drugs and alcohol</a></li> <li><a href="#betting">Betting</a></li> <li><a href="#addagreement">Additional agreements</a></li> <li><a href="#streaming">Streaming, interviews and media</a> <ol> <li><a href="#broadcasting">Broadcasting</a></li> <li><a href="#matchmedia">Match media</a></li> <li><a href="#screenshots">Screenshots</a></li> </ol> </li> <li><a href="#playerchanges">Player changes</a></li> <li><a href="#prizemoney">Prize money</a></li> </ol> </li> <li><a href="#csgorules">Counter-Strike:Global Offensive rules</a> <ol> <li><a href="#tournament">Tournament structure and time schedule</a> <ol> <li><a href="#penalties">Penalties and forfeits during the time schedule</a></li> <li><a href="#compomaxteams">Compo sign-up and max teams</a></li> <li><a href="#structure">Structure</a></li> <li><a href="#gamesetup">Game setup</a></li> <li><a href="#vetosystem">Veto system</a></li> <li><a href="#compospecificrules">Compo specific rules</a></li> <li><a href="#usageofpause">Usage of pause</a></li> <li><a href="#demofiles">Demo files</a></li> </ol> </li> <li><a href="#matchprocedure">Match procedure</a> <ol> <li><a href="#maplist">Map list</a></li> <li><a href="#matchrules">Match rules</a></li> <li><a href="#clientrules">Client rules</a></li> <li><a href="#illegalscripts">Illegal scripts</a></li> <li><a href="#customfiles">Custom files</a></li> <li><a href="#colordepth">Color depth and external programs</a></li> <li><a href="#illegalprograms">Illegal programs</a></li> <li><a href="#ingameoverlay">In-game overlays</a></li> <li><a href="#techprobs">Technical problems and disconnects</a></li> </ol> </li> <li><a href="#csgoserver">CS:GO server</a> <ol> <li><a href="#serversettings">Server settings</a></li> <li><a href="#servercrash">Server crash</a></li> <li><a href="#serverlag">Server (var) lag</a></li> <li><a href="#serverplugins">Server plugins</a></li> <li><a href="#rconusage">RCON usage</a></li> <li><a href="#warmupservers">Warmup servers</a></li> </ol> </li> </ol> </li> <li><a href="#copyright">Copyright Notice</a></li> </ol> <a name="admin"></a>1. Admins and communication <hr /> Communication before the LAN: <ul> <li>General contact > <a href="mailto:csgo@fom.be">csgo@fom.be</a></li> </ul> Please email us any feedback before and after the LAN event. CS:GO admin team: <ul> <li>Dragon <ul> <li>Steam: https://steamcommunity.com/profiles/76561198244170010/</li> <li>Discord: dragon (main communication line)</li> </ul> </li> </ul> Communication during the LAN: The communication during the LAN will be through Steam, Discord or at the Compo Desk. We will be available as much as possible in the <a href="https://discord.gg/URX6v82Wmp" target="_blank">#csgo channel</a>. We will use this as a second channel to remind everyone to play, of scheduling or changes. Important server-info will also be communicated in the #csgo channel. Discord will be our main communication channel. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compo"></a>2. Compo overview <hr /> <a name="participants"></a> 2.1 Participants Due to lack of time, we have a tight schedule. Therefore we can make the decision to force teams to only participate in 1 grand compo! We will contact the teams who are signed in for 2 grand compo’s at the moment and they will need to make a choice. When a team refuses, we will remove them from the competition to make room for other teams. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamsheets"></a> 2.2 Team sheets As teams may be required to compete on the stage, it is required that all teams remove any offensive material from their desktops. A rule violation by any player in a team may lead the tournament admins to sanction the entire team, even if the rest of the team was not aware of the violation. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamnames"></a> 2.3 Team names <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teammanager"></a> 2.4 Team manager / coach The team manager does not have any responsibilities. The team manager is eligible to play for his team in matches, providing he’s indicated as a “Player” on the team in the team sheet. The communication with the team will not go via the team manager, all communication will go via the team captain! Spectators are not allowed on our servers. Only tournament admins may be in spectator mode during a match. The only exception is: coaches are allowed to spectate a match using the coach's command, only if the tournament admin is notified, and thus to spectate their team only. They are obligated to use the “coach t” or “coach ct” command before the match start and aren’t allowed to join after a match has been started. If noticed that the coach is abusing this rule, the team will get punished for it (e.g. round loss, side loss or match loss). During a match, the coach may only communicate with the players during freeze-time, warm up, half-time, or during one of the 4 timeouts. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="teamcaptain"></a> 2.5 Team captain We consider the one who registered the team into the compo on the Frag-o-Matic website as captain! The clan leader or team captain is responsible for his team and all the players in that team. It is recommended that the team captain is fluent in English or Dutch, as he will be required to communicate with the tournament admins. The team captain must read and understand the rulebook. The team captain is responsible for ensuring his team and players adhere to the rules. Ignorance of the rules is not an excuse for rule violations. The team captain may choose at any time to nominate another player in or manager of his team as team captain for any reason. Such nominations must be reported by the team captain, either in person or in writing, to the admins before the game starts. All official communication between a competing team and the tournament admins must be conducted by the team captain. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="players"></a> 2.6 Players All players must read and understand the CSGO rulebook. Any player in violation of a rule, will be sanctioned as described in this rulebook. Each team must have five players on the match server at the match start time as indicated by the schedule, unless permission has been granted by the tournament admins to play with less than five players. Only players registered for a team in the tournament may play for that team unless otherwise discussed with the tournament admin. All players must play at their designated seats for all tournament games unless otherwise instructed by the tournament admins. Players registered for a team in the tournament may not play for any other team in the same tournament. Each player has to use their nickname that is similar to the nickname he/she has entered on their fom.be account. All players for a team must be clearly identifiable in-game with a uniform tag for that team and a separate, noticeably different nickname for each player. Players may not significantly change their nickname during the tournament. Any nickname they use during the tournament must always obviously visibly correspond to their original nickname. You are not allowed to change your nickname in-game. If an admin’s job is hindered because of wrong or difficult nicknames or clan tags, the team will get a warning. 3 warnings are equal to a forfeit in 1 match. Player nicknames may not be offensive. Tournament admins reserve the right to reject any tag or nickname they deem inappropriate. Make sure your steam account is linked with your fom.be account corresponding to your nickname. Players are strictly prohibited from using any other person’s steam account for any reason whatsoever during the CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="grstandard"></a> 2.6.1 Grooming standards People participating in the CS:GO tournament are expected to normal grooming standards. You may be asked to take action if you or your clothing have a look or odor that’s offensive to other players. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="cheating"></a> 2.7 Cheating During Frag-o-Matic we won’t investigate cheaters from an external event. When we discover someone cheating during our LAN, that player and his team will be banned from the compo and the player will be also banned for the next Frag-o-Matic edition. Furthermore we will investigate reports of players cheating during other tournaments until 2 weeks before the LAN. When a player is discovered cheating during another tournament/platform 12 months before the event occurs, then that player will not be allowed to play on that edition of Frag-o-Matic within the CS:GO competition and the edition after that. If one of the following rules apply, then that player will not be allowed to compete in our tournament: Caught cheating within a tournament/platform 12 months before the start date of our event. There needs to be enough evidence for that player, that he/she was cheating and the tournament admins will judge if the evidence is valid OR if he/she was caught cheating on the following platforms: <ul> <li><a href="ts3server://ts.fom.lan">ts.fom.lan</a> - CS:GO admin channel</li> <li>Discord: <a href="https://discord.gg/MbPY2ge">https://discord.gg/MbPY2ge</a> <ul> <li>Teams are only allowed to use a uniform team name for their team.</li> <li>Teams may not change their team name during the tournament.</li> <li>Teams may not change their team in-game tag during the tournament, unless none was set.</li> <li>Duplicating team names of other teams is not allowed.</li> <li>Duplicating (exactly or approximately) the tags used by another team in the tournament is not permitted.</li> <li>Team names are not allowed to be offensive.</li> <li>Please make sure your team name is filled in on your fom.be profile.</li> </ul> <ul> <li>Faceit</li> <li>Esl</li> <li>Valve (vac ban for any Counter strike: Global Offensive game)</li> <li>ESEA</li> <li>Cevo</li> </ul> </li> <li>When a player is caught selling or buying cheats. In any case the admin will have the final decision. This means that the admin will review the evidence and make the final call. If a player shows the intention of coming to our tournament to cheat and we’re provided evidence of this. Everyone from the community may send evidence to csgo@fom.be, when they suspect someone participating at Frag-o-Matic of cheating. All forms of cheating in matches are forbidden, and will result in an overall forfeit in the tournament. Possibilities for cheating in Counter-Strike:Global Offensive are, for example; all kinds of multi-hacks, wallhack, aimbot, colored models, no-recoil, no-smoke, no-flash and sound changes. All hardware or software that has an influence on the game in such a way that the essence of the game is affected are banned from this tournament. Any use of this kind of hardware will result in a disqualification of the tournament as it will be recognized as cheating. When proven that a player is not cooperating in his own ban research or is lying on purpose. He will get banned for 1 edition. You can find our banlist at http://www.fom.be/contents/view/cs-go-banlist The mentioned people in our ban list are not allowed in the CS:GO tournaments at Frag-O-Matic until the edition that’s stated there. When these people compete under a false name nonetheless or try to circumvent the rules then they will receive an extended or permanent ban. Here are some of the other examples of ways to gain advantages, this list may not be the full list but if players are unsure of certain things, they should seek to ask the tournament admins first: Flash Bang, Smoke Grenade, and Hand Grenade Bugs - it is illegal to use any flash bang, smoke grenade, or hand grenade bugs, regardless of intent. Silent Bomb Plants - ALL bomb plants must be done in a position where your opponents can hear you. There should be no rotation in players to gain money advantages throughout a match. The bomb must be planted on solid surfaces on the map, ie where an opponent can defuse from, so not up in the air or floating. Illegal Bomb Defuses - No player can defuse a bomb through any other solid object on the map, it has to be done in clear view. It is also forbidden to try to intentionally distort your hitboxes during a defuse situation to prevent an opponent from killing you in game. Walking/Boosting through walls - No player should walk, boost through walls or roofs. To do so will see your team penalized for that round. Map Exploits - Boosts that include the use of clipping are strictly forbidden. The term “Clipping” defines that when a player is boosted can see through certain parts of the map (ie over/under walls, or through solid objects on the map). If any player or team feels unsure on a new advantage they have found through their practice sessions, they are welcome to show this specific spot to the tournament team to review. Any player or team that does this will be treated to the strictest confidence as not to jeopardize your strategic advantage, however we can rule on whether it is a legal move. We strongly advise teams to give us plenty of time ahead of an event so we can review it in good time and make good judgement on it. The game admins may inspect your machine at any time throughout the event to inspect for cheats or hacks within your game files, steam cloud and anywhere on your PC or memory sticks. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="forbiditems"></a>2.7.1 Forbidden items During the lan, to prevent cheating by using external devices or items, the following items are forbidden: <ul> <li>Smartwatches; Having or carrying a smartwatch during the event, when competing in the CS:GO competition, that player will immediately be disqualified from the competition.</li> <li>Alienware Wireless Headset AW988; Visual representation of audio isn’t allowed.</li> <li>AR (augmented reality) glasses</li> <li>Hardware from the brand “Bloody” (these are mice that come with software that reduces recoil on weapons)</li> </ul> Any other electronic devices (like smartphones) that are used during a match will be considered suspicious and we’ll ask that they’re not used. If, during a match, the suspicious device is still in use; the team of the player using the device will receive a warning. After 3 warnings the team will receive a disqualification from the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="match"></a>2.8 Match protests and forfeit <a name="definitions"></a> 2.8.1 Definition A protest is a raised issue for problems that affect the match outcome; a protest may even be filed during a match for things like incorrect server settings and other related issues. A protest is the official communication between a team captain and a tournament admin. A forfeit is a lose or surrender. <a name="matchprotest"></a> 2.8.2 Match protest rules Participants are only allowed to issue a match protest before the beginning of their next match. The protest must contain detailed info about why the protest was filed, how the discrepancy came to be and when the discrepancy occurred. A protest may be declined if proper documentation is not presented. A simple “they are cheaters” will not be enough. Insults and flaming are strictly prohibited in a protest, and may result in the protest being ruled against the insulting party. <a name="forfeitrules"></a> 2.8.3 Forfeit rules A forfeit can be called for a single match or the entire competition from a competing team for their team. Only the team captain can raise a forfeit for their team. A forfeit can also be raised by an admin as a penalty for wrongdoing. For example, in most cases where a competing team doesn’t follow the time schedule. The tournament admins can always force a forfeit. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="seeding"></a>2.9 Seeding Seeding is done through an objective outlook towards data provided by all participants for every event. Every participant is required to provide us their main steam account, ESEA and/or CEVO profile, FACEit level and previous wins/achievements. The supplied data is only kept and used for one event to calculate an individual “score” based on reached rank, played time, csgo hours and historical performance/achievements from Frag-o-Matic or other tournaments. The team sum of 5 individual scores will show an objective score where the higher the score, the higher the team seeding. The tournament admins won’t seed teams higher based on any subjective opinions. If no statistical data was provided for all 5 team member, than that team will be seeded beyond top 16. <a name="general"></a>3. General <hr /> <a name="generalrules"></a> 3.1 General rules Frag-o-Matic Counter strike:Global Offensive (CS:GO) 5v5 tournament is a local area network (LAN) tournament. By competing in this tournament, teams and players accept these rules in full. Teams which violate these rules will be sanctioned, and may be removed from the tournament without compensation. In the beginning of the LAN the team captains can sit together with the admin to discuss the rules and to make adjustments if needed. The decisions are made by the admin. If you have any issues with the rules, you can explain this by sending an email to <a href="mailto:csgo@fom.be">csgo@fom.be</a> up to one week before the start of the event. Clarification of any point in the rules is available from the tournament admins at any time during the tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="sanctions"></a>3.2 Sanctions and disputes Sanctions and disputes will be resolved by the main tournament admin. The admin’s decision on any sanction or dispute is final. Abusive behavior towards the Frag-o-Matic staff, tournament admins or opponents at any time during the tournament is unacceptable and will be punished with warnings. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="confidentiality"></a>3.3 Confidentiality The content of protests, support communication, discussions or any other correspondence with tournament officials and administrators are considered as strictly confidential. The publication of such material is prohibited. If the contents has been shared without consent then this could lead to a team’s disqualification. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="coc"></a>3.4 Code of conduct Any form of aggression<a href="#coc_aggression">*</a> (both verbally and physically) will not be tolerated. Any and all physical aggression will be sanctioned with an immediate disqualification by that person or team performing the physical act (both actioned and reactioned). Any verbal aggression will be sanctioned by a time-out for that person or team. A time-out is either set in time (hours/day) or in amount of matches when a player or team is not allowed to participate in the CS:GO competition. Any situation that is about to escalate should be dealt with in a calm and diplomatic manner. An audience with any Frag-o-Matic crew member (CS:GO admin or Frag-o-Matic team leaders) can always be called for at any time during the event. Keep in mind that this audience can not be used to waste time or get a time advantage. At any point, the CS:GO tournament admins can decide to continue with the competition with or without consent from either players or other Frag-o-Matic staff. In the event when a single player or more are accused of cheating, the event will continue nonetheless. Evidence will be presented to the tournament admins and a call will be made at a later stage of the event. This rule is set to not cause any delays and have the situation under control. Any player(s) or team(s) ignoring this rule will receive a forfeit. Any player or team ignoring a CS:GO admin will be sanctioned with a warning. 3 warnings are equal to a forfeit of 1 match. <a name="coc_aggression"></a>*A form of aggression is described as: <ul> <li>Instrumental aggression -- Aggression aimed at obtaining an object, privilege or space with no deliberate intent to harm another person. Typical of participants wanting to get ahead of the competition with lies, anger, bullying, criticizing other people behind their backs, leaving others out of a group or otherwise ostracizing them, turning people against each other, dismissing the opinions of others (passive aggression).</li> <li>Hostile aggression -- Aggression intended to harm another person, such as hitting/kicking/biting someone (active aggression). Threatening to beat up someone (nonverbal intimidation). Sending threatening messages through emails, phone calls, or social media, or making threats against someone's life, shouting, and swearing (verbal hostility). Breaking someone's computer, destroying someone's cell phone, or other forms of vandalism (destruction of property).</li> <li>Relational aggression -- A form of hostile aggression that does damage to another's peer relationships, as in social exclusion, gossiping or rumor spreading. Examples: Arguments within a team after a lose that lead to a verbal fight.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="drugsalcohol"></a>3.5 Drugs and alcohol To play a match under the influence of any drugs or performance enhancers is strictly prohibited, and may be punished with exclusion from the tournament. If an admin finds that a player is not capable of competing in the competition because of intoxication, the admin can exclude that person from the entire tournament. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="betting"></a>3.6 Betting Betting on any match in the CS:GO tournament is strictly forbidden. <a name="addagreement"></a>3.7 Additional agreements Teams may be required to play any match on the stage. If so, teams will be notified at least 20 minutes prior to the start time of that match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="streaming"></a>3.8 Streaming, interviews and media <a name="broadcasting"></a>3.8.1 Broadcasting Frag-o-Matic reserves the right to broadcast any match or demo, teams may not refuse such broadcasts. All forms of client side game broadcasting are NOT allowed. Frag-o-Matic participants are not allowed to watch a local GOTV if a CS:GO server broadcasts a game. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchmedia"></a>3.8.2 Match media All match media (screenshots, demos, etc.) must be kept until the end of the event. Faking or manipulating match media is forbidden and will result in exclusion from the tournament. Match media should be named clearly based on what it is. It is not possible to file a protest to complain about bad match media naming. However if a tournament admin is hindered in their work because of bad match media naming, then a tournament admin will give a warning. 3 warnings are equal to a forfeit in 1 match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="screenshots"></a>3.8.3 Screenshots The admin can ask for screenshots of every game on any moment during the event. When he does this, the team leader has 15 minutes time to deliver the screenshot to the admin. A screenshot of the scoreboard at the end of each half must be taken. When this is not done by a team it can result in a lost match when one of the other teams complains about a score. An RCON status screenshot must be taken: <ul> <li>at the beginning of the match</li> <li>in case of a server/player change</li> <li>if a player reconnects</li> </ul> RCON status screenshots made with the help of programs like HLSW etc. are not sufficient. In order to take an RCON status you have to use the console command “rcon status” (don’t forget to enter your RCON password) and take a screenshot of that. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="playerchanges"></a>3.9 Player changes Teams are permitted to substitute players (only with another player not active in the CS:GO competition) during pauses and between rounds, if they have permission from the tournament admin. Consent for substitutions must be obtained from the tournament admins, and substitute players must be registered for that team in the tournament. You can make this clear to the admin by using the contact information in section ‘Admins and communication’. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="prizemoney"></a>3.10 Prize money When you subscribe to this competition you agree to our prize money policy: http://www.fom.be/contents/view/prizemoney-policy <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="csgorules"></a> 4. Counter-Strike:Global Offensive rules <hr /> <a name="tournament"></a>4.1 Tournament structure and time schedule Games will be scheduled to be played between 23:00 on Friday and 18:00 on Sunday. On Saturday and Sunday, teams must be present at 10:00 (AM) and ready to start playing the rest of their scheduled matches. It can be the case that the tournament admins decide to start earlier or end later, but this will be communicated (to all team captains). An exact time schedule will be provided on our fom.be website for all teams to follow. Each match will have a start time on which the game needs to be started. The team(s) that are responsible where the start time has not been met will receive a forfeit for that match. Whether or not this rule will be applied, is the decision of a tournament admin. The schedule for the tournament may be subject to change at any time. Matches may be rescheduled to a later time, delayed, postponed or cancelled at any time by the tournament admins without prior notice. Games will not be rescheduled to an earlier time in the same day if either of the teams have not yet played a game on that day without the consent of both team captains. Where possible the tournament admins will notify any teams involved in a rescheduled game of the new match start time at least one hour before the new start time. In the event a match is cancelled, the tournament admins will notify the teams involved as quickly as reasonably possible. If there’s insufficient time to complete a match, the tournament admins may at any time declare one team as the winner, if that team holds a clear advantage in that match. It is the responsibility of the tournament admins to decide whether a team holds a clear advantage. This rule will only be used in the emergency when the remaining event time is a factor. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="penalties"></a>4.1.1 Penalties and forfeits during the time schedule If 1 or more teams are still playing a match in a previous stage or if 1 team is late and doesn’t start playing their match in the stage where they are; Teams are offered 30 minutes of grace time in both circumstances, after 30 minutes warnings are handed out: After 30 minutes that team, who’s still not playing their scheduled match, will receive a 1st warning from a tournament admin. A notice via our csgo channel on discord and if the team is present and found at their seat they’ll be warned in person as well. A second warning is given in the same manner 5 minutes after the first warning. A third and final warming is given in the same way 5 minutes after that. 5 minutes after the final warning the team who received 3 warnings will receive 1 game loss for their match in the next round. In case of a bo3 in the next round, a bo2 will be played with one win to the team that was on time. If after 15 minutes the team with 3 warnings and one loss in the next round is still not playing, they’ll receive a forfeit from an admin. In case of a bo1 (in the lower bracket for example) we won’t lose any more time and a forfeit will be forced. The forfeit is applied on our fom.be website and a notice is given on Discord in our csgo channel. The tournament admins will keep a record of the warnings and will communicate this to the compo desk. As mentioned in our general rulebook; Non-acceptable excuses for a delay: “We want to eat” isn’t a valid excuses for starting an argument at the compo desk. As a note, we ask that teams only take a maximum of 15 minute breaks in between games and matches to avoid any penalties. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compomaxteams"></a>4.1.2 Compo sign-up and max teams All compo sign-ups are done via our fom.be website. Some rules are already explained in our general rulebook. Any team that is not “full”, meaning the team doesn’t consist of minimum 5 players, will be removed from the compo sign-up one hour before the start of the competition. We allow a maximum 64 teams to register to our CS:GO competition. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="structure"></a>4.1.3 Structure Our CS:GO tournament will use a poule system and 3 double elimination brackets (pro, semi-pro and fun). Each poule will consist out of 3-4 teams who will compete against each other to make it into the brackets. Each team within the poule needs to play against any other team within its poule. Following the poule stage, the 2 winners from each poule will advance to a pro bracket, the last 2 teams from each poule will advance to a semi-pro bracket and <s>other teams will proceed to the fun bracket</s>. Our compo structure will use the following setup for pro, semi-pro and fun: <ul> <li>Groupstage > BO1 (best of 1)</li> <li>Upper Bracket > BO3 (best of 3)</li> <li>Lower Bracket > BO1 (best of 1)</li> <li>Pro & semi-pro bracket: <ul> <li>Semi-final (Finals in lower bracket) > BO3 (best of 3)</li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> </li> <li><s>Fun bracket:</s> <ul> <li><s>Semi-final (Finals in lower bracket) > BO1 (best of 1)</s></li> </ul> </li> <li>Final > BO3 (best of 3) with map advantage</li> </ul> When 2 teams have the same amount of points after the poules we will look at the following criteria in order: <ul> <li>The match between the 2 teams</li> <li>The won rounds total</li> <li>The lost rounds total</li> <li>Seeding</li> </ul> We can also look at other criteria if we feel that it's necessary (also cooperation). The admin is allowed to overrule these criteria. If there’s not enough data to validate a criteria the admin can chose to ignore it. A tournament admin can decide to change some matches from BO3 to BO1 or visa versa when needed. (For example: no time to play a BO3). <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="gamesetup"></a>4.1.4 Game setup Matches will be played 5on5. Playing with fewer than five players in any match is only allowed with permission from the tournament admins. Before a match starts, both teams must state that they are ready to start the match. The must do this by having one team member typing ‘ready’ in server chat. Should a player or a team have temporary problems, the opponent must be informed and the start must be repeated. Bugs due to map loading (e.g. missing boxes, ladders or similar) must be checked before the match starts and if they appear the map must be reloaded. You cannot protest after the match to complain about this type of bug. You’ll need to use the following match setup to play every game: <ul> <li>2 teams join the server that is assigned to them on our fom website.</li> <li>The team captains can use the RCON password “godmode” to follow the next steps : <ul> <li>Don’t forget to do ‘cl_mute_enemy_team 0’</li> <li>Change the map to de_mirage (rcon changelevel de_mirage)</li> <li>Load the Frag-o-Matic config (rcon exec fom5on5.cfg)</li> <li>Start a knife round on de_mirage (optional). The winner of this knife round can decide who team A is. Start the map veto process (Veto is explained under ‘Veto system’’).</li> <li>After the Veto the team captain needs to change the map to the first map of Team A (in a BO3) or the single map that was chosen (in a BO1) (rcon changelevel ‘mapname’)</li> <li>Load the fom5on5.cfg again on this map. (rcon exec fom5on5.cfg)</li> <li>After this the teams do another knife round to decide which team will start on which side of the map. The winner of the knife round decides which side they want to start on and that team will also start the match. (rcon mp_restartgame 1)</li> </ul> </li> </ul> If a player drops before the first kill has been made in the first round, the match will be restarted. If a player drops after the first kill has been made, the server can be paused at the end of the current round (see rule ‘Usage of pause’ function) by one of the teams. The waiting time for a dropped player is 10 minutes. If the player or a substitute rejoins the server and both teams are ready, the game can be resumed. If a player/substitute doesn’t connect within that time, then the match is continued 4on5, or 4on4 if the opposing team agrees and the tournament admins are informed. There are no forbidden weapons or grenades. Feel free to use all new weapons and grenades implemented in CS:GO. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="vetosystem"></a>4.1.5 Veto system Our veto process is the next step after playing a knife round, as described in ‘Game setup’. The map(s) chosen to be played in each BO1 and BO3 are done via elimination (i.e. veto). Where ‘team 1 = A’ and ‘team 2 = B’, with A being decided by the winner of the knife round. Teams can also decide who team A/B is without playing a knife round. The maps you don’t want to play as a team, should be the maps that you veto during this process. The veto process needs to be done in server chat. VETO rules best-of-1: ABABAB veto. The map pool exists out of 7 maps. 6 maps are vetoed during this process, 3 maps for each team. The remaining map is the map played in the best-of-1 match. VETO rules best-of-2: ABAB veto AB play. The map pool exists out of 7 maps. 4 maps are vetoed during this process, 2 maps for each team. Out of the 3 remaining maps, 1 team each gets to decide a map to play on. VETO rules best-of-3: A/B veto, A/B play and A/B veto. The map pool exists out of 7 maps. 4 maps are eliminated, and 3 maps are selected to play. Each team needs to veto a map, followed by each team choosing a map and again each team vetoing a map. The remaining map is the third map that needs to be played if both teams win a map. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="compospecificrules"></a>4.1.6 Compo specific rules All matches in the group stage are played MR15. All matches in the brackets are played MR15 (meaning, 16 rounds won = game win). In the group stage, matches are played best of one (BO1) on a map decided by veto (as described above). All games are best of three (BO3) in the bracket, 3 maps are decided by veto. The grand final is a best of three (BO3) with map advantage! When in the brackets a game is tied an overtime needs to be played. The overtime will be played MR3 with 10.000$ start money. For the start of the overtime teams will stay on the side which they played the previous half on, during halftime sites will be swapped. Teams will continue to play overtimes until a winner has been found. We have our own special breed of bracket seeding. For more information please contact us in advance. This bracket seeding is law. Obey it. All CS:GO players can only use our ts.fom.lan (local) teamspeak for voice communication. Teams are only allowed to have 5 players + 1 coach in their teamspeak channel whilst in a competition match. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="usageofpause"></a>4.1.7 Usage of pause Pauses may be taken for any reason. Teams are permitted 3 pauses per side in each match. Each pause having a maximum duration of 5 minutes, unless authorised by an admin to take a longer pause (in case of technical difficulties, for example). After a “pause”-event, an “unpause“-command needs to be done. Teams can’t unpause without the consent of the other team. Pauses may only be activated at the start of the next round during freeze time. So make sure you tell the other team before round end (in all-chat), that your team will take a pause in the next freeze time. Usage: Type the following commands in console, to activate and deactivate the pause event. Pause = rcon mp_pause_match Unpause = rcon mp_unpause_match Illegal usage: DON’T USE = sv_pause If a team does use sv_pause, they have to surrender 1 round. (by all team members typing “kill” in console) <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="demofiles"></a>4.1.8 Demo files GoTV demos must be active for each match to be recorded. It’s the responsibility of (both) team captains to ensure that GoTV is recording. If this isn’t the case, the tournament admins will be forced to make calls without a recording when a dispute occurs. It’s recommended for all players to record point of view (POV) demos for the full duration of all matches without exception. A knife round is part of a match and should be recorded. At least one of the players must be able to upload the knife round on admin request. Protests regarding missing knife rounds are not valid. In general, defective or manipulated demos will be treated as missing demos. If the demo is incomplete, as decided by the admin, it also will be treated as missing demo. If a protest is opened for a match, all match media need to be kept until the end of the event. Demos can only be requested up to a maximum of 30 minutes after a match via the admin. A demo request must state which teams were playing, the name(s) of the map(s) the match(es) was/were played on, the time of the match(es) and the server IP address(es). If a player or a team illegally aborts the match, they lose their right to demand demos. Recording demos is recommended. Our servers will likely record demos for every match but these are only used when there is doubt about a decision the admin has to make. It is strictly forbidden to edit demos. If a demo is manipulated, it will be treated as missing demo. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.2 Match procedure <a name="maplist"></a>4.2.1 Map list Only the following maps are allowed to be played on during the competition: <ul> <li>de_ancient</li> <li>de_anubis</li> <li>de_inferno</li> <li>de_mirage</li> <li>de_nuke</li> <li>de_overpass</li> <li>de_vertigo</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchrules"></a>4.2.2 Match rules <ul> <li>Diffusing through walls, crates or any other object is not allowed. The bomb must always be fully visible when defusing.</li> <li>Throwing grenades/flash bangs/smokes across walls in maps is allowed.</li> <li>Boosting is not considered a bug.</li> <li>Buying and using multiple grenades is allowed but with a max of 2 flash bangs.</li> <li>Multiple grenades are allowed but max 2 flash bangs</li> <li>Bugs on the map must be checked before the match begins. Any protest after the match about map bugs will be ignored.</li> <li>If a player loses connection before the first kill, the match can be restarted. If this happens after the first kill, the server can be paused and have the disconnected player reconnect. Matches won’t be restarted due to disconnections.</li> <li>If you want a player change (sub) during the match, inform the opponent and the compo admins before the match begins!</li> <li>To boost through walls, ceilings or the ground, sky walking, map swimming, floating and sharking are all forbidden.</li> <li>Climbing with help of teammates is allowed in general.</li> <li>Throwing grenades inside walls is not allowed.</li> <li>Self-kills are strictly forbidden, unless an admin forces you to do this as a sanction for disobeying any rules.</li> <li>Bomb planting in a way it can’t be reached is forbidden.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="clientrules"></a>4.2.3 Client rules The admin is allowed to take over your computer before, during and after a game and have a look. Without the pc’s owner in question nearby, the person in question can appoint someone to stay with the admin to make sure no privacy issues are violated. Any trace evidence of cheats found on a player’s computer – even if such discovery took place outside of a game – can lead to exclusion from any competition. For NVIDIA graphics card users: The use of Ambient Occlusion is strictly forbidden. If you are caught using this setting, this will result in a direct loss of the match. Getting caught for a 2nd time will result in removal from the tournament. This setting can be found in your NVIDIA Control Panel > 3D Settings > Manage 3D settings. The following commands are forbidden: <ul> <li>mat_hdr_enabled</li> </ul> The following startparameters are forbidden: <ul> <li>+mat_hdr_enabled 0/1</li> <li>+mat_hdr_leven 0/1/2</li> </ul> In your game client cfg-folder you’re only allowed to have config files. Pictures, demos, screenshots and zipped files are forbidden. All other configuration changes are allowed as long as they do not give an unfair edge or advantage comparable to cheating. The using of bugs is not allowed. Should a bug that is not listed be used, an admin will decide if a penalty is necessary. Boosting through walls/ceilings/ground, sky walking, map swimming, floating and sharking are all forbidden. To throw grenades inside walls is not allowed. Above walls and roofs is allowed. To plant the bomb in a way that it cannot be reached is forbidden. Places that can be reached with help of a team mate are allowed as long as they are visible. Violating this rule will result in tournament administrators intervention. Changing graphic settings to irregular values can be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalscripts"></a>4.2.4 Illegal scripts In general, all scripts are illegal except for buy, toggle & demo scripts. Some examples of illegal scripts: <ul> <li>Stop Shoot scripts [Use or Awp scripts]</li> <li>Center view scripts</li> <li>Turn scripts [180° or similar]</li> <li>No Recoil scripts</li> <li>Burst fire scripts</li> <li>Rate changers (Lag scripts)</li> <li>FPS scripts</li> <li>Anti flash scripts or binding (snd_* bindings)</li> <li>Bunnyhop scripts</li> <li>Stop sound scripts</li> <li>Following Commands/CVars are forbidden</li> <li>+weapon_recoil_model 0 (Startparameter)</li> </ul> The following CVAR values must be used: <ul> <li>cl_bobcycle 0.98 (First Time->Warning)</li> </ul> If there are more than one player who used a wrong client setting, the match will be deleted. Exception: cl_bobcycle Using illegal scripts will be penalized if the script could lead to a game advantage. This depends on the script concerned and it is up to the responsible admin to decide about this. It does not matter whether the script has been used or not. If the config files of a user contain illegal scripts or parts of illegal scripts, he will be penalized. The use of No-Flash and No-Recoil bindings/scripts in any and all forms will be punished. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="customfiles"></a>4.2.5 Custom files The HUD can be changed as long as no information are deleted or falsified which are available in the standard HUD. If the HUD is changed it has to be readable. If an admin is hindered in his work due to an unreadable HUD, penalty points may be assigned. Protests or supports which adhere to this rule will not be admitted and are rejected directly. Apart from the HUD and the GUI no custom files are allowed. This also includes custom models, changed textures or sounds (volume, soundscapes) are forbidden. <a name="colordepth"></a>4.2.6 Color depth and external programs The usage of a color depth of 16bit is not allowed. The usage of external programs (ex. SweetFX, A3D,...) are not allowed to enhance vision. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="illegalprograms"></a>4.2.7 Illegal programs Changing the game graphics or textures with the help of video card drivers or similar tools is illegal. Furthermore any kind of overlay that displays the system performance while playing (e.g. NVidia SLI Display, Riva tuner Overlays) is illegal. Failure to comply with this rule will result in a punishment for the player and the team. Tools that only display the FPS are legal. Regardless of being actively used, if these scripts are found in part or in full in your config files, you will be penalized. If you play with ambient occlusion, it will be punished as cheating!! Punishment will be given regardless of whether the script/binding is executed via external hardware or software. Also binding any snd_ command is forbidden. <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="ingameoverlay"></a>4.2.8 In-game overlays All In-Game overlays – provided by the game itself – except the following are forbidden: <ul> <li>net_graph 0</li> <li>net_graph 1</li> <li>cl_showpos 1</li> <li>cl_showfps 1</li> <li>cl_showdemooverlay 1 / -1</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="techprobs"></a>4.2.9 Technical problems and disconnects If a disconnection occurs the game should automatically reconnect. When this doesn’t work, a tournament admin will decide what to do. The tournament admin will make a call in every possible scenario regarding the severity of the problem and how to deal with it. But, the following guidelines are in place in the event of a disconnect: <ul> <li>In the case where Frag-o-Matic is responsible for the disconnect, the round needs to be restored to the start of the round where the disconnection happened. I.e. follow the steps as described under “4.3.2 Server crash”.</li> <li>When a player is responsible for his own disconnect, the team with 4 players can decide to continue to play 4v5 or use a pause as described in “4.1.6 Usage of pause”.</li> <li>The disconnected player can then reconnect to the match. If that player fails to reconnect, then the match will continue 4v5.</li> <li>If another Frag-o-Matic participant is responsible for causing a problem, then the match needs to be paused and a tournament admin needs to be notified to make a call on what to do.</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="matchprocedure"></a>4.3 CS:GO server <a name="serversettings"></a>4.3.1 Server settings Frag-o-Matic will supply hardware for all servers. All games related to the tournament must be played on these servers. All matches will be played using the latest version of CS:GO and the official Frag-o-Matic CS:GO server config. All matches have to be played on an official Frag-o-Matic CS:GO tournament server and on the provided server number (as listed on our fom.be website, in the csgo compo section). We’ll use a standard (ESL) 5v5 pro league tournament config on a 128 tickrate server: <ul> <li>Startmoney: 0</li> <li>Maxrounds: 30</li> <li>Roundtime: 1m 55s (1.92)</li> <li>Freezetime: 12 seconds</li> <li>C4timer: 40 seconds</li> <li>Pause: 1x 5minutes per half each map.</li> <li>Overtime: MR3 - .000 startmoney</li> <li>Time during half time: 13 seconds</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="servercrash"></a>4.3.2 Server crash In the event of a server crash, after notifying a tournament admin and having them restart the the server, both teams have to re-join the same server and use the following command: <ul> <li>rcon mp_backup_restore_list_files</li> </ul> This will show you the backup files before the server crashed. 1 team captain then executes the correct file by using the following command: <ul> <li>rcon mp_backup_restore_load_file</li> </ul> Example: rcon mp_backup_restore_load_file backup_round12.txt All previous settings (score, money, armor, weapons,...) are then reset to the round before the server crashed and the match is set to paused. To continue the match, use the unpause command: <ul> <li>rcon mp_unpause_match</li> </ul> <a href="#navigation" style="color: rgb(23, 88, 127);">Back to top</a> <a name="serverlag"></a>4.3.3 Server (var) lag Teams are given the time to play a warm-up match on their server before every compo match if they wish to do so. It’s not allowed to switch to another server once the compo match has been started. Test the server before the match starts. Any server problems should be reported to a tournament admin by going to the compo desk after sending an email with the information below. In the event that you experience any lag during or before a match, please note the time(s) and contact us via Discord or the Compo Desk. We'll escalate this information and, if possible, provide a solution for upcoming matches. The statement or report of (possible) lag in a match is a not valid argument in a protest. However, sending us the data above will give your team the time necessary to avoid any possible forfeits when you notify us at the compo desk after sending your email. Failure in providing us this data will not allow your team to deviate from our time schedule. We strive to provide all our servers lag free. We would like to thank you in helping us improve our servers. <a name="serverplugins"></a>4.3.4 Server plugins No extra plugins will be installed on our CS:GO servers. <a name="rconusage"></a>4.3.5 RCON usage RCON is only allowed as described in “4.1.2 Game setup”. Usage of RCON outside the game setup is penalised by receiving an instant forfeit for the team using any other RCON commands. We monitor all servers and RCON logs and will use this as evidence to hand out a match forfeit to the team using RCON outside of the game setup rules. <a name="rconusage"></a>4.3.6 Warmup servers Subject to availability, we will provide warmup servers. The settings will mirror our war servers as close as possible, but won’t be managed by the csgo team. Participants in our competition are allowed to use our warmup servers as such, to warm up, practice nade throws, practice aim,etc… We will not guarantee availability of those servers, since they will depend on the overall capacity. If warmup servers are available, they cannot ever be used for playing matches. If a match has been played on one of those servers though, the end-scores will still count. It is the responsibility of both teams the correct (assigned) server is joined. At any time, we can convert one of those servers to an official war server (In cases of need). It will at that point no longer show up as a warmup server. <a name="copyright"></a>5. Copyright Notice Copyright © 2005-2022 by E-EVENTS VZW All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. For permission requests, write to the publisher, addressed at <a href="mailto:csgo@fom.be">csgo@fom.be</a> </li> </ul>
 showsponsor(false)
 sponsorcontent
 showfiles(false)
 filescontent
 prizescontent<h1> First Place </h1> <ul> <li> <h3>525 €</h3> </li> </ul> <h1>Second Place</h1> <ul> <li> <h3>315 €</h3> </li> </ul> <h1>Third Place</h1> <ul> <li> <h3>210 €</h3> </li> </ul>
 precompo(false)
 donations0
 donationAmount0
 scheduleregistration closes at 21! please make sure all games are played on time! poules will be made and will be playable. saturday 10am we will start with the brackets semi final will be at 10am on sunday with afterwards the grand final Have fun and Good luck!
 faq
 sponsorUrl
 sponsorImg(null)
 sortTimeLabel0
 Event(array)
 id46
 nameFrag-o-Matic 24.1
 description
 starttime2023-09-01 18:00:00
 endtime2023-09-03 18:00:00
 locationOktoberhallen
 streetSchrovestraat
 nr22A
 bus
 zip9280
 cityWieze
 countryBelgium
 slugfrag-o-matic-24-1
 oldId(null)
 nrParticipants1000
 bbq(false)
 usedHal0
 Admin(array)
 id8749
 facebook_id(null)
 usernametimlaforce@outlook.com
 new_username(null)
 nicknameDragon
 password6a205eb25ef1de84cdd48fc4ef10a2c80752fb18
 firstnametim
 lastnamelaforce
 active1
 validationCodevapumabava
 mailValidationCode
 group_id9
 created2019-01-04 00:06:59
 modified2023-08-06 01:08:09
 last_login2025-01-11 14:11:09
 streetStationsstraat
 nr90
 bus2
 zip9450
 cityHaaltert
 countryBE
 phone
 gsm0470072987
 genderm
 birthdate1996-02-06
 clanId5040
 clantrust0
 clanjoinId(null)
 hwbudget> 2500 EUR
 education
 professionother
 hoursaweek
 languageeng
 oldId(null)
 receive_newsletter(false)
 imageUrlupload/users/Dragon_spongery.png
 slugdragonbeard
 fb_link
 fb_location
 CPUAMD Ryzen 7 3700x
 MOBOMicro-Star International Co. Ltd. MPG X570 GAMING EDGE WIFI (MS-7C37) (AM4)
 GFX3071MB NVIDIA GeForce RTX 2080 Ti (ASUStek Computer Inc)
 RAM32gig
 steamName(null)
 steamId(null)
 originName
 lolSummonerNametolstyak
 Other465GB Samsung SSD 970 EVO 500GB (Unknown (SSD)) 1863GB Seagate ST2000DM008-2FR102 (SATA (SSD)) ZOWIE XL LCD (1920x1080@240Hz) Razer Huntsman Elite
 comment
 seat_id(null)
 msg_notifications(true)
 mouseHandright
 deviceId
 alternative_login(false)
 Admin2(array)
 id(null)
 facebook_id(null)
 username(null)
 new_username(null)
 nickname(null)
 password(null)
 firstname(null)
 lastname(null)
 active(null)
 validationCode(null)
 mailValidationCode(null)
 group_id(null)
 created(null)
 modified(null)
 last_login(null)
 street(null)
 nr(null)
 bus(null)
 zip(null)
 city(null)
 country(null)
 phone(null)
 gsm(null)
 gender(null)
 birthdate(null)
 clanId(null)
 clantrust(null)
 clanjoinId(null)
 hwbudget(null)
 education(null)
 profession(null)
 hoursaweek(null)
 language(null)
 oldId(null)
 receive_newsletter(null)
 imageUrl(null)
 slug(null)
 fb_link(null)
 fb_location(null)
 CPU(null)
 MOBO(null)
 GFX(null)
 RAM(null)
 steamName(null)
 steamId(null)
 originName(null)
 lolSummonerName(null)
 Other(null)
 comment(null)
 seat_id(null)
 msg_notifications(null)
 mouseHand(null)
 deviceId(null)
 alternative_login(null)
 CompoState(array)
 id5
 nameBrackets in progress
 Tag(array)
 id31
 tagNameCSGO
 bannerUrlupload/tags/banner_CompoTag_CSGO.jpg
 parentId(null)
 slugcsgo
 colorgreen
 Teams(array)
 0(array)
 id10265
 nameBASTARDS.AF9K
 leaderId5352
 compoId367
 pouleId1452
 notes
 withdrew(false)
 1(array)
 id10268
 nameTeam Bouletjjj
 leaderId6262
 compoId367
 pouleId1454
 notes
 withdrew(false)
 2(array)
 id10277
 nameSchizophrenic
 leaderId9704
 compoId367
 pouleId1453
 notes
 withdrew(false)
 3(array)
 id10299
 nameVlamski
 leaderId10144
 compoId367
 pouleId1452
 notes
 withdrew(false)
 4(array)
 id10324
 nameSM1L3RS
 leaderId9989
 compoId367
 pouleId1454
 notes
 withdrew(false)
 5(array)
 id10336
 nameBorn2Throw
 leaderId9602
 compoId367
 pouleId1452
 notes
 withdrew(false)
 6(array)
 id10367
 nameAnti-Icon
 leaderId4920
 compoId367
 pouleId1453
 notes
 withdrew(false)
 7(array)
 id10375
 namePertinax eSports
 leaderId2961
 compoId367
 pouleId1452
 notes
 withdrew(false)
 8(array)
 id10429
 nameSnuifkikkers
 leaderId9719
 compoId367
 pouleId1454
 notes
 withdrew(false)
 9(array)
 id10509
 nameiNTERMiXED
 leaderId1362
 compoId367
 pouleId1453
 notes
 withdrew(false)
 10(array)
 id10518
 nameTe Weinig Gaming
 leaderId8075
 compoId367
 pouleId1453
 notesEZ WIN
 withdrew(false)
 Wars(array)
 0(array)
 id27959
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10265
 teamB10299
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB6
 scoreBByB16
 finalScoreA6
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1452
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 06:30:44
 1(array)
 id27960
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10265
 teamB10336
 scoreAByA4
 scoreBByA16
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA4
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1452
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 06:30:42
 2(array)
 id27961
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10265
 teamB10375
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB1
 scoreBByB16
 finalScoreA1
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1452
 level2
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 06:30:38
 3(array)
 id27962
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10299
 teamB10375
 scoreAByA12
 scoreBByA16
 scoreAByB12
 scoreBByB16
 finalScoreA12
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1452
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 03:42:23
 4(array)
 id27963
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10299
 teamB10336
 scoreAByA16
 scoreBByA10
 scoreAByB16
 scoreBByB10
 finalScoreA16
 finalScoreB10
 winnerWarId(null)
 loserWarId(null)
 pouleId1452
 level2
 playable1
 mapname(null)
 time(null)
 screen1Aimg/upload/screenshots/27963/20230901233340_1.jpg
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-01 23:44:29
 5(array)
 id27964
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10336
 teamB10375
 scoreAByA5
 scoreBByA16
 scoreAByB5
 scoreBByB16
 finalScoreA5
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1452
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 02:25:19
 6(array)
 id27965
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10277
 teamB10367
 scoreAByA16
 scoreBByA6
 scoreAByB16
 scoreBByB6
 finalScoreA16
 finalScoreB6
 winnerWarId(null)
 loserWarId(null)
 pouleId1453
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 02:21:48
 7(array)
 id27966
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10277
 teamB10509
 scoreAByA16
 scoreBByA5
 scoreAByB16
 scoreBByB5
 finalScoreA16
 finalScoreB5
 winnerWarId(null)
 loserWarId(null)
 pouleId1453
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 01:14:05
 8(array)
 id27967
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10277
 teamB10518
 scoreAByA16
 scoreBByA4
 scoreAByB16
 scoreBByB4
 finalScoreA16
 finalScoreB4
 winnerWarId(null)
 loserWarId(null)
 pouleId1453
 level2
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 03:32:59
 9(array)
 id27968
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10367
 teamB10518
 scoreAByA16
 scoreBByA3
 scoreAByB16
 scoreBByB3
 finalScoreA16
 finalScoreB3
 winnerWarId(null)
 loserWarId(null)
 pouleId1453
 level1
 playable1
 mapname(null)
 time(null)
 screen1Aimg/upload/screenshots/27968/16497089.735000001_image.png
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 03:33:11
 10(array)
 id27969
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10367
 teamB10509
 scoreAByA16
 scoreBByA1
 scoreAByB16
 scoreBByB1
 finalScoreA16
 finalScoreB1
 winnerWarId(null)
 loserWarId(null)
 pouleId1453
 level2
 playable1
 mapname(null)
 time(null)
 screen1Aimg/upload/screenshots/27969/11737429.995000003_image.png
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-01 23:56:38
 11(array)
 id27970
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10509
 teamB10518
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA0
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1453
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 11:43:21
 12(array)
 id27971
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10268
 teamB10324
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA16
 finalScoreB5
 winnerWarId(null)
 loserWarId(null)
 pouleId1454
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-01 23:02:26
 13(array)
 id27972
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10268
 teamB10429
 scoreAByA12
 scoreBByA16
 scoreAByB12
 scoreBByB16
 finalScoreA12
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1454
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 00:39:00
 14(array)
 id27973
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType(null)
 compoId367
 teamA10324
 teamB10429
 scoreAByA0
 scoreBByA16
 scoreAByB1
 scoreBByB16
 finalScoreA1
 finalScoreB16
 winnerWarId(null)
 loserWarId(null)
 pouleId1454
 level2
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 06:30:50
 15(array)
 id28181
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10277
 teamB(null)
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28189
 loserWarId28196
 pouleId(null)
 level0
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 16(array)
 id28182
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10324
 teamB10265
 scoreAByA0
 scoreBByA16
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA0
 finalScoreB16
 winnerWarId28189
 loserWarId28196
 pouleId(null)
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 13:17:36
 17(array)
 id28183
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10429
 teamB(null)
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28190
 loserWarId28197
 pouleId(null)
 level0
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 18(array)
 id28184
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10299
 teamB(null)
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28190
 loserWarId28197
 pouleId(null)
 level0
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 19(array)
 id28185
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10375
 teamB(null)
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28191
 loserWarId28198
 pouleId(null)
 level0
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 20(array)
 id28186
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10336
 teamB10518
 scoreAByA2
 scoreBByA0
 scoreAByB2
 scoreBByB0
 finalScoreA2
 finalScoreB0
 winnerWarId28191
 loserWarId28198
 pouleId(null)
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 14:21:30
 21(array)
 id28187
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10367
 teamB(null)
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28192
 loserWarId28199
 pouleId(null)
 level0
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 22(array)
 id28188
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10268
 teamB10509
 scoreAByA2
 scoreBByA0
 scoreAByB2
 scoreBByB0
 finalScoreA2
 finalScoreB0
 winnerWarId28192
 loserWarId28199
 pouleId(null)
 level0
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 14:13:21
 23(array)
 id28189
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10277
 teamB10265
 scoreAByA2
 scoreBByA0
 scoreAByB2
 scoreBByB0
 finalScoreA2
 finalScoreB0
 winnerWarId28193
 loserWarId28203
 pouleId(null)
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 14:27:23
 24(array)
 id28190
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10429
 teamB10299
 scoreAByA2
 scoreBByA1
 scoreAByB2
 scoreBByB1
 finalScoreA2
 finalScoreB1
 winnerWarId28193
 loserWarId28202
 pouleId(null)
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 17:52:16
 25(array)
 id28191
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10375
 teamB10336
 scoreAByA2
 scoreBByA0
 scoreAByB2
 scoreBByB0
 finalScoreA2
 finalScoreB0
 winnerWarId28194
 loserWarId28201
 pouleId(null)
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 21:52:24
 26(array)
 id28192
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10367
 teamB10268
 scoreAByA2
 scoreBByA0
 scoreAByB2
 scoreBByB0
 finalScoreA2
 finalScoreB0
 winnerWarId28194
 loserWarId28200
 pouleId(null)
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 17:25:39
 27(array)
 id28193
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10277
 teamB10429
 scoreAByA2
 scoreBByA0
 scoreAByB0
 scoreBByB2
 finalScoreA2
 finalScoreB0
 winnerWarId28195
 loserWarId28206
 pouleId(null)
 level2
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 22:02:54
 28(array)
 id28194
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10375
 teamB10367
 scoreAByA2
 scoreBByA0
 scoreAByB2
 scoreBByB0
 finalScoreA2
 finalScoreB0
 winnerWarId28195
 loserWarId28207
 pouleId(null)
 level2
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 21:52:16
 29(array)
 id28195
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType1
 compoId367
 teamA10277
 teamB10375
 scoreAByA2
 scoreBByA0
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA2
 finalScoreB0
 winnerWarId28210
 loserWarId28209
 pouleId(null)
 level3
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-03 02:14:19
 30(array)
 id28196
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA(null)
 teamB10324
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28200
 loserWarId(null)
 pouleId(null)
 level0
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 31(array)
 id28197
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA(null)
 teamB(null)
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28201
 loserWarId(null)
 pouleId(null)
 level0
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 32(array)
 id28198
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA(null)
 teamB10518
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28202
 loserWarId(null)
 pouleId(null)
 level0
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 33(array)
 id28199
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA(null)
 teamB10509
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28203
 loserWarId(null)
 pouleId(null)
 level0
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 34(array)
 id28200
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10324
 teamB10268
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB0
 scoreBByB16
 finalScoreA0
 finalScoreB16
 winnerWarId28204
 loserWarId(null)
 pouleId(null)
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 18:32:29
 35(array)
 id28201
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA(null)
 teamB10336
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA(null)
 finalScoreB(null)
 winnerWarId28204
 loserWarId(null)
 pouleId(null)
 level1
 playable0
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate(null)
 36(array)
 id28202
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10518
 teamB10299
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA1
 finalScoreB16
 winnerWarId28205
 loserWarId(null)
 pouleId(null)
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 20:37:27
 37(array)
 id28203
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10509
 teamB10265
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA1
 finalScoreB0
 winnerWarId28205
 loserWarId(null)
 pouleId(null)
 level1
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 19:30:26
 38(array)
 id28204
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10268
 teamB10336
 scoreAByA1
 scoreBByA0
 scoreAByB16
 scoreBByB10
 finalScoreA16
 finalScoreB10
 winnerWarId28206
 loserWarId(null)
 pouleId(null)
 level2
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 20:37:44
 39(array)
 id28205
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10299
 teamB10509
 scoreAByA16
 scoreBByA0
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA16
 finalScoreB0
 winnerWarId28207
 loserWarId(null)
 pouleId(null)
 level2
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-02 22:34:08
 40(array)
 id28206
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10268
 teamB10429
 scoreAByA16
 scoreBByA13
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA16
 finalScoreB13
 winnerWarId28208
 loserWarId(null)
 pouleId(null)
 level3
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-03 01:09:01
 41(array)
 id28207
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10299
 teamB10367
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB1
 scoreBByB2
 finalScoreA1
 finalScoreB2
 winnerWarId28208
 loserWarId(null)
 pouleId(null)
 level3
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-03 04:11:46
 42(array)
 id28208
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10268
 teamB10367
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA0
 finalScoreB1
 winnerWarId28209
 loserWarId28211
 pouleId(null)
 level4
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-03 06:35:50
 43(array)
 id28209
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType2
 compoId367
 teamA10367
 teamB10375
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA1
 finalScoreB0
 winnerWarId28210
 loserWarId28211
 pouleId(null)
 level5
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-03 13:46:20
 44(array)
 id28210
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType3
 compoId367
 teamA10277
 teamB10367
 scoreAByA2
 scoreBByA0
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA2
 finalScoreB0
 winnerWarId(null)
 loserWarId(null)
 pouleId(null)
 level6
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-03 14:39:59
 45(array)
 id28211
 screen1B(null)
 screen2B(null)
 screen3B(null)
 screen4B(null)
 bracketType4
 compoId367
 teamA10268
 teamB10375
 scoreAByA(null)
 scoreBByA(null)
 scoreAByB(null)
 scoreBByB(null)
 finalScoreA0
 finalScoreB1
 winnerWarId(null)
 loserWarId(null)
 pouleId(null)
 level6
 playable1
 mapname(null)
 time(null)
 screen1A(null)
 screen2A(null)
 screen3A(null)
 screen4A(null)
 prevTeamA(null)
 prevTeamB(null)
 screen1Admin(null)
 screen2Admin(null)
 adminEditID(null)
 adminEditDate(null)
 finalScoreDate2023-09-03 13:47:18
- langen
- topNewsTournament(array)
 0(array)
 Newspost(array)
 id1161
 title_enbe quiet Partnership!
 title_nlbe quiet Partnership!
 imageUrlupload/newsposts/banner_adjusted.jpg
 spotlightImgUrlupload/newsposts/banner_adjusted_spotlight.jpg
 slugbe-quiet-1
 startDate2025-01-25 22:11:50
 spotlight(true)
 Maintag(array)
 bannerUrl(null)
 tagNameFoM 26.0
 slugfom-26-0
 colorgreen
 1(array)
 Newspost(array)
 id1165
 title_enGame in Comfort: Reserve Your Speedseat Now!
 title_nlGame in Comfort: Reserveer Nu Jouw Speedseat!
 imageUrlupload/newsposts/banner_speedseats245.jpg
 spotlightImgUrlupload/newsposts/banner_speedseats245_spotlight.jpg
 sluggame-in-comfort-reserveer-nu-jouw-speedseat
 startDate2025-01-24 21:19:35
 spotlight(true)
 Maintag(array)
 bannerUrl(null)
 tagNameFoM 26.0
 slugfom-26-0
 colorgreen
 2(array)
 Newspost(array)
 id1163
 title_enAlternate at Frag-o-Matic!
 title_nlAlternate op Frag-o-Matic!
 imageUrlupload/newsposts/banner_326435180_5673349109453991_6796126376389233884_n.png
 spotlightImgUrlupload/newsposts/banner_326435180_5673349109453991_6796126376389233884_n_spotlight.png
 slugalternate-at-frag-o-matic
 startDate2025-01-23 20:33:29
 spotlight(true)
 Maintag(array)
 bannerUrl(null)
 tagNameFoM 26.0
 slugfom-26-0
 colorgreen
 3(array)
 Newspost(array)
 id1166
 title_enCompo Registration Open: Join Now!
 title_nlCompo Registration Open: Join Now!
 imageUrlupload/newsposts/banner_tournaments-open.jpg
 spotlightImgUrlupload/newsposts/banner_tournaments-open_spotlight.jpg
 slugcompo-registration-open-join-now
 startDate2025-01-21 18:25:47
 spotlight(true)
 Maintag(array)
 bannerUrl(null)
 tagNameFoM 26.0
 slugfom-26-0
 colorgreen
- topNews(array)
 0(array)
 Newspost(array)
 id1161
 title_enbe quiet Partnership!
 title_nlbe quiet Partnership!
 imageUrlupload/newsposts/banner_adjusted.jpg
 spotlightImgUrlupload/newsposts/banner_adjusted_spotlight.jpg
 slugbe-quiet-1
 startDate2025-01-25 22:11:50
 spotlight(true)
 Maintag(array)
 bannerUrl(null)
 1(array)
 Newspost(array)
 id1165
 title_enGame in Comfort: Reserve Your Speedseat Now!
 title_nlGame in Comfort: Reserveer Nu Jouw Speedseat!
 imageUrlupload/newsposts/banner_speedseats245.jpg
 spotlightImgUrlupload/newsposts/banner_speedseats245_spotlight.jpg
 sluggame-in-comfort-reserveer-nu-jouw-speedseat
 startDate2025-01-24 21:19:35
 spotlight(true)
 Maintag(array)
 bannerUrl(null)
 2(array)
 Newspost(array)
 id1163
 title_enAlternate at Frag-o-Matic!
 title_nlAlternate op Frag-o-Matic!
 imageUrlupload/newsposts/banner_326435180_5673349109453991_6796126376389233884_n.png
 spotlightImgUrlupload/newsposts/banner_326435180_5673349109453991_6796126376389233884_n_spotlight.png
 slugalternate-at-frag-o-matic
 startDate2025-01-23 20:33:29
 spotlight(true)
 Maintag(array)
 bannerUrl(null)
 3(array)
 Newspost(array)
 id1166
 title_enCompo Registration Open: Join Now!
 title_nlCompo Registration Open: Join Now!
 imageUrlupload/newsposts/banner_tournaments-open.jpg
 spotlightImgUrlupload/newsposts/banner_tournaments-open_spotlight.jpg
 slugcompo-registration-open-join-now
 startDate2025-01-21 18:25:47
 spotlight(true)
 Maintag(array)
 bannerUrl(null)
- order(null)
- configNrParticipantsOpen530
- configNrParticipants520
- currentEvent(array)
 id49
 nameFrag-o-Matic 26.0
 description
 starttime2025-02-28 18:00:00
 endtime2025-03-02 18:00:00
 locationOktoberhallen
 streetSchrovestraat
 nr22A
 bus
 zip9280
 cityWieze
 countryBelgium
 slugfrag-o-matic-26-0
 oldId(null)
 nrParticipants1000
 bbq(false)
 usedHal0
- menuItems(array)
 0(array)
 MenuItem(array)
 id1
 titleHome
 typedirect_link
 link/
 layout(null)
 enabled(true)
 MenuSubItem(empty)
 1(array)
 MenuItem(array)
 id2
 titleEvent
 typedropdown
 link(null)
 layoutevent
 enabled(true)
 MenuSubItem(array)
 0(array)
 id1
 menu_item_id2
 titleEvent Info
 layout_position1
 enabled(true)
 MenuLink(array)
 0(array)
 id1
 menu_sub_item_id1
 titleGeneral info
 url/contents/view/event-information
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id1
 target_self
 image(null)
 position1
 enabled(true)
 1(array)
 id2
 menu_sub_item_id1
 titleWhat is a LAN party?
 url/contents/view/what-is-a-lan-party
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id2
 target_self
 image(null)
 position2
 enabled(true)
 2(array)
 id3
 menu_sub_item_id1
 titleAbout Frag-o-Matic
 url/contents/view/frag-o-matic-events
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id3
 target_self
 image(null)
 position3
 enabled(true)
 3(array)
 id4
 menu_sub_item_id1
 titleWhat to bring?
 url/contents/view/what-to-bring
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id4
 target_self
 image(null)
 position4
 enabled(true)
 4(array)
 id5
 menu_sub_item_id1
 titleLocation & Transport
 url/contents/view/location-and-transport
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id5
 target_self
 image(null)
 position5
 enabled(true)
 5(array)
 id6
 menu_sub_item_id1
 titleVisitor entrance
 url/contents/view/visitors
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id6
 target_self
 image(null)
 position6
 enabled(true)
 6(array)
 id7
 menu_sub_item_id1
 titleSleeping accommodations
 url/contents/view/sleeping-accomodations
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id7
 target_self
 image(null)
 position7
 enabled(true)
 1(array)
 id2
 menu_item_id2
 titleEvent Tickets
 layout_position2
 enabled(true)
 MenuLink(array)
 0(array)
 id8
 menu_sub_item_id2
 titleTicket Types
 url/contents/view/tickets
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id8
 target_self
 image(null)
 position1
 enabled(true)
 1(array)
 id9
 menu_sub_item_id2
 titleTicketing Procedure
 url/contents/view/ticketing-procedure
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id9
 target_self
 image(null)
 position2
 enabled(true)
 2(array)
 id10
 menu_sub_item_id2
 titleParticipants
 url/events/subscriptions
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position3
 enabled(true)
 3(array)
 id11
 menu_sub_item_id2
 titleBuy Your Ticket
 url/products/category/fomtickets
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position4
 enabled(true)
 2(array)
 id3
 menu_item_id2
 titleEvent Service
 layout_position3
 enabled(true)
 MenuLink(array)
 0(array)
 id12
 menu_sub_item_id3
 titleSeatmap
 url/seatmaps/view
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id10
 target_self
 image(null)
 position1
 enabled(true)
 1(array)
 id13
 menu_sub_item_id3
 titleParking Spot
 url/contents/view/parking
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id11
 target_self
 image(null)
 position2
 enabled(true)
 2(array)
 id14
 menu_sub_item_id3
 titleSpeedseats Rental
 url/contents/view/speedseat-rental
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id12
 target_self
 image(null)
 position3
 enabled(true)
 3(array)
 id37
 menu_sub_item_id3
 titleAlternate PC Rental
 url/contents/view/pc-rental
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id12
 target_self
 image(null)
 position3
 enabled(true)
 3(array)
 id4
 menu_item_id2
 titleEvent Catering
 layout_position4
 enabled(true)
 MenuLink(array)
 0(array)
 id15
 menu_sub_item_id4
 titleFood & Drinks
 url/contents/view/food-and-drink
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id13
 target_self
 image(null)
 position1
 enabled(true)
 2(array)
 MenuItem(array)
 id3
 titleTournaments
 typedropdown
 link(null)
 layouttoornament
 enabled(true)
 MenuSubItem(array)
 0(array)
 id5
 menu_item_id3
 titleGrand Tournaments
 layout_position1
 enabled(true)
 MenuLink(array)
 0(array)
 id16
 menu_sub_item_id5
 titleCOUNTER-STRIKE 2 (5VS5)
 url/compos/view/434
 link_typeinternal_compo
 internal_compo_id434
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position1
 enabled(true)
 1(array)
 id17
 menu_sub_item_id5
 titleLEAGUE OF LEGENDS (5VS5)
 url/compos/view/437
 link_typeinternal_compo
 internal_compo_id437
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position2
 enabled(true)
 2(array)
 id18
 menu_sub_item_id5
 titleROCKET LEAGUE (3VS3)
 url/compos/view/438
 link_typeinternal_compo
 internal_compo_id438
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position3
 enabled(true)
 1(array)
 id6
 menu_item_id3
 titleConsole Arena
 layout_position2
 enabled(true)
 MenuLink(array)
 0(array)
 id19
 menu_sub_item_id6
 titleSTREET FIGHTER 6
 urlhttps://www.start.gg/tournament/frag-o-matic-26-0/event/street-fighter-6-presented-by-frag-o-matic
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id(null)
 target_blank
 image(null)
 position1
 enabled(true)
 1(array)
 id20
 menu_sub_item_id6
 titleTEKKEN 8
 urlhttps://www.start.gg/tournament/frag-o-matic-26-0/event/tekken-8-main-event-presented-by-frag-o-matic
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id(null)
 target_blank
 image(null)
 position2
 enabled(true)
 2(array)
 id21
 menu_sub_item_id6
 titleMORTAL KOMBAT 1
 urlhttps://www.start.gg/tournament/frag-o-matic-26-0/event/mortal-kombat-1-presented-by-frag-o-matic
 link_typeexternal
 internal_compo_id(null)
 internal_newspost_id(null)
 internal_content_id(null)
 target_blank
 image(null)
 position3
 enabled(true)
 3(array)
 id28
 menu_sub_item_id6
 titleEA Sports FC 24
 url/compos/view/451
 link_typeinternal_compo
 internal_compo_id451
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position3
 enabled(true)
 4(array)
 id29
 menu_sub_item_id6
 titleEA Sports F1 24
 url/compos/view/447
 link_typeinternal_compo
 internal_compo_id447
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position4
 enabled(true)
 2(array)
 id7
 menu_item_id3
 titleSolo Tournaments
 layout_position3
 enabled(true)
 MenuLink(array)
 0(array)
 id23
 menu_sub_item_id7
 titleLOL TEAM FIGHT TACTICS
 url/compos/view/441
 link_typeinternal_compo
 internal_compo_id441
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position2
 enabled(true)
 1(array)
 id30
 menu_sub_item_id7
 titleAge Of Empires II
 url/compos/view/440
 link_typeinternal_compo
 internal_compo_id440
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position2
 enabled(true)
 2(array)
 id35
 menu_sub_item_id7
 titleHearthstone
 url/compos/view/439
 link_typeinternal_compo
 internal_compo_id439
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position2
 enabled(true)
 3(array)
 id36
 menu_sub_item_id7
 titleQuake Champions
 url/compos/view/435
 link_typeinternal_compo
 internal_compo_id435
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position2
 enabled(true)
 3(array)
 id8
 menu_item_id3
 titleTeam Tournaments
 layout_position4
 enabled(true)
 MenuLink(array)
 0(array)
 id24
 menu_sub_item_id8
 titlePUBG: BATTLEGROUNDS (4VSP)
 url/compos/view/432
 link_typeinternal_compo
 internal_compo_id432
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position2
 enabled(true)
 1(array)
 id25
 menu_sub_item_id8
 titleMarvel Rivals (6VS6)
 url/compos/view/436
 link_typeinternal_compo
 internal_compo_id436
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position1
 enabled(true)
 2(array)
 id27
 menu_sub_item_id8
 titleROCKET LEAGUE (2VS2)
 url/compos/view/442
 link_typeinternal_compo
 internal_compo_id442
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position3
 enabled(true)
 3(array)
 id31
 menu_sub_item_id8
 titleLeague of Legends ARAM (5VS5)
 url/compos/view/443
 link_typeinternal_compo
 internal_compo_id443
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position4
 enabled(true)
 4(array)
 id9
 menu_item_id3
 titleFun Tournaments
 layout_position5
 enabled(true)
 MenuLink(array)
 0(array)
 id32
 menu_sub_item_id9
 titleKICKER (2VS2)
 url/compos/view/444
 link_typeinternal_compo
 internal_compo_id444
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position4
 enabled(true)
 1(array)
 id33
 menu_sub_item_id9
 titleAIRHOCKEY (1VS1)
 url/compos/view/445
 link_typeinternal_compo
 internal_compo_id445
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position5
 enabled(true)
 2(array)
 id34
 menu_sub_item_id9
 titleDARTS (1VS1)
 url/compos/view/446
 link_typeinternal_compo
 internal_compo_id446
 internal_newspost_id(null)
 internal_content_id(null)
 target_self
 image(null)
 position6
 enabled(true)
 3(array)
 MenuItem(array)
 id4
 titlePartners
 typedirect_link
 link/contents/view/partners
 layout(null)
 enabled(true)
 MenuSubItem(empty)
 4(array)
 MenuItem(array)
 id5
 titleTickets
 typedirect_link
 link/products/category/fomtickets
 layout(null)
 enabled(true)
 MenuSubItem(empty)
- $request->data(empty)
- $this->validationErrors(array)
 Permission(empty)
 Aro(empty)
 Aco(empty)
 MenuItem(empty)
 MenuSubItem(empty)
 MenuLink(empty)
 Content(empty)
 Newspost(empty)
 Config(empty)
 Event(empty)
 Order(empty)
 Orderstate(empty)
 Customer(empty)
 DefaultProvider(empty)
 Orderlines(empty)
 Payments(empty)
 Logs(empty)
 IPN(empty)
 Team(empty)
 Compo(empty)
 Leader(empty)
 Poule(empty)
 Members(empty)
 TeamUser(empty)
 User(empty)
 Ticket(empty)
 TicketState(empty)
 Buyer(empty)
 Owner(empty)
 Operator(empty)
 Product(empty)
 Type(empty)
 Seat(empty)
 Seatmap(empty)
 War(empty)
 TeamA(empty)
 TeamB(empty)
 AdminEdit(empty)
 Admin(empty)
 Admin2(empty)
 CompoState(empty)
 Tag(empty)
 Teams(empty)
 Wars(empty)
- Loaded Helpers(array)
 0Session
 1Form
 2Html
 3Javascript
 4Time
 5Multiselect
 6Shop
 7Ajax
 8Text
 9Sidebar
 10Cache
 11Number
 12SimpleGraph
 13DebugTimer
 14Toolbar
 15HtmlToolbar
====

Environment

App Constants

Constant	Value
E_ERROR	1
E_RECOVERABLE_ERROR	4096
E_WARNING	2
E_PARSE	4
E_NOTICE	8
E_STRICT	2048
E_DEPRECATED	8192
E_CORE_ERROR	16
E_CORE_WARNING	32
E_COMPILE_ERROR	64
E_COMPILE_WARNING	128
E_USER_ERROR	256
E_USER_WARNING	512
E_USER_NOTICE	1024
E_USER_DEPRECATED	16384
E_ALL	32767
DEBUG_BACKTRACE_PROVIDE_OBJECT	1
DEBUG_BACKTRACE_IGNORE_ARGS	2
TRUE	1
FALSE
ZEND_THREAD_SAFE
ZEND_DEBUG_BUILD
NULL
PHP_VERSION	5.6.40-0+deb8u12
PHP_MAJOR_VERSION	5
PHP_MINOR_VERSION	6
PHP_RELEASE_VERSION	40
PHP_EXTRA_VERSION	-0+deb8u12
PHP_VERSION_ID	50640
PHP_ZTS	0
PHP_DEBUG	0
PHP_OS	Linux
PHP_SAPI	apache2handler
DEFAULT_INCLUDE_PATH	.:/usr/share/php:/usr/share/pear
PEAR_INSTALL_DIR	/usr/share/php
PEAR_EXTENSION_DIR	/usr/lib/php5/20131226
PHP_EXTENSION_DIR	/usr/lib/php5/20131226
PHP_PREFIX	/usr
PHP_BINDIR	/usr/bin
PHP_MANDIR	/usr/share/man
PHP_LIBDIR	/usr/lib/php5
PHP_DATADIR	/usr/share/php5
PHP_SYSCONFDIR	/etc
PHP_LOCALSTATEDIR	/var
PHP_CONFIG_FILE_PATH	/etc/php5/apache2
PHP_CONFIG_FILE_SCAN_DIR	/etc/php5/apache2/conf.d
PHP_SHLIB_SUFFIX	so
PHP_EOL
PHP_MAXPATHLEN	4096
PHP_INT_MAX	9223372036854775807
PHP_INT_SIZE	8
PHP_BINARY
PHP_OUTPUT_HANDLER_START	1
PHP_OUTPUT_HANDLER_WRITE	0
PHP_OUTPUT_HANDLER_FLUSH	4
PHP_OUTPUT_HANDLER_CLEAN	2
PHP_OUTPUT_HANDLER_FINAL	8
PHP_OUTPUT_HANDLER_CONT	0
PHP_OUTPUT_HANDLER_END	8
PHP_OUTPUT_HANDLER_CLEANABLE	16
PHP_OUTPUT_HANDLER_FLUSHABLE	32
PHP_OUTPUT_HANDLER_REMOVABLE	64
PHP_OUTPUT_HANDLER_STDFLAGS	112
PHP_OUTPUT_HANDLER_STARTED	4096
PHP_OUTPUT_HANDLER_DISABLED	8192
UPLOAD_ERR_OK	0
UPLOAD_ERR_INI_SIZE	1
UPLOAD_ERR_FORM_SIZE	2
UPLOAD_ERR_PARTIAL	3
UPLOAD_ERR_NO_FILE	4
UPLOAD_ERR_NO_TMP_DIR	6
UPLOAD_ERR_CANT_WRITE	7
UPLOAD_ERR_EXTENSION	8
DATE_ATOM	Y-m-d\TH:i:sP
DATE_COOKIE	l, d-M-Y H:i:s T
DATE_ISO8601	Y-m-d\TH:i:sO
DATE_RFC822	D, d M y H:i:s O
DATE_RFC850	l, d-M-y H:i:s T
DATE_RFC1036	D, d M y H:i:s O
DATE_RFC1123	D, d M Y H:i:s O
DATE_RFC2822	D, d M Y H:i:s O
DATE_RFC3339	Y-m-d\TH:i:sP
DATE_RSS	D, d M Y H:i:s O
DATE_W3C	Y-m-d\TH:i:sP
SUNFUNCS_RET_TIMESTAMP	0
SUNFUNCS_RET_STRING	1
SUNFUNCS_RET_DOUBLE	2
LIBXML_VERSION	20901
LIBXML_DOTTED_VERSION	2.9.1
LIBXML_LOADED_VERSION	20901
LIBXML_NOENT	2
LIBXML_DTDLOAD	4
LIBXML_DTDATTR	8
LIBXML_DTDVALID	16
LIBXML_NOERROR	32
LIBXML_NOWARNING	64
LIBXML_NOBLANKS	256
LIBXML_XINCLUDE	1024
LIBXML_NSCLEAN	8192
LIBXML_NOCDATA	16384
LIBXML_NONET	2048
LIBXML_PEDANTIC	128
LIBXML_COMPACT	65536
LIBXML_NOXMLDECL	2
LIBXML_PARSEHUGE	524288
LIBXML_NOEMPTYTAG	4
LIBXML_SCHEMA_CREATE	1
LIBXML_HTML_NOIMPLIED	8192
LIBXML_HTML_NODEFDTD	4
LIBXML_ERR_NONE	0
LIBXML_ERR_WARNING	1
LIBXML_ERR_ERROR	2
LIBXML_ERR_FATAL	3
OPENSSL_VERSION_TEXT	OpenSSL 1.0.1t 3 May 2016
OPENSSL_VERSION_NUMBER	268439887
X509_PURPOSE_SSL_CLIENT	1
X509_PURPOSE_SSL_SERVER	2
X509_PURPOSE_NS_SSL_SERVER	3
X509_PURPOSE_SMIME_SIGN	4
X509_PURPOSE_SMIME_ENCRYPT	5
X509_PURPOSE_CRL_SIGN	6
X509_PURPOSE_ANY	7
OPENSSL_ALGO_SHA1	1
OPENSSL_ALGO_MD5	2
OPENSSL_ALGO_MD4	3
OPENSSL_ALGO_DSS1	5
OPENSSL_ALGO_SHA224	6
OPENSSL_ALGO_SHA256	7
OPENSSL_ALGO_SHA384	8
OPENSSL_ALGO_SHA512	9
OPENSSL_ALGO_RMD160	10
PKCS7_DETACHED	64
PKCS7_TEXT	1
PKCS7_NOINTERN	16
PKCS7_NOVERIFY	32
PKCS7_NOCHAIN	8
PKCS7_NOCERTS	2
PKCS7_NOATTR	256
PKCS7_BINARY	128
PKCS7_NOSIGS	4
OPENSSL_PKCS1_PADDING	1
OPENSSL_SSLV23_PADDING	2
OPENSSL_NO_PADDING	3
OPENSSL_PKCS1_OAEP_PADDING	4
OPENSSL_DEFAULT_STREAM_CIPHERS	ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128:AES256:HIGH:!SSLv2:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!RC4:!ADH
OPENSSL_CIPHER_RC2_40	0
OPENSSL_CIPHER_RC2_128	1
OPENSSL_CIPHER_RC2_64	2
OPENSSL_CIPHER_DES	3
OPENSSL_CIPHER_3DES	4
OPENSSL_CIPHER_AES_128_CBC	5
OPENSSL_CIPHER_AES_192_CBC	6
OPENSSL_CIPHER_AES_256_CBC	7
OPENSSL_KEYTYPE_RSA	0
OPENSSL_KEYTYPE_DSA	1
OPENSSL_KEYTYPE_DH	2
OPENSSL_KEYTYPE_EC	3
OPENSSL_RAW_DATA	1
OPENSSL_ZERO_PADDING	2
OPENSSL_TLSEXT_SERVER_NAME	1
PREG_PATTERN_ORDER	1
PREG_SET_ORDER	2
PREG_OFFSET_CAPTURE	256
PREG_SPLIT_NO_EMPTY	1
PREG_SPLIT_DELIM_CAPTURE	2
PREG_SPLIT_OFFSET_CAPTURE	4
PREG_GREP_INVERT	1
PREG_NO_ERROR	0
PREG_INTERNAL_ERROR	1
PREG_BACKTRACK_LIMIT_ERROR	2
PREG_RECURSION_LIMIT_ERROR	3
PREG_BAD_UTF8_ERROR	4
PREG_BAD_UTF8_OFFSET_ERROR	5
PCRE_VERSION	8.35 2014-04-04
FORCE_GZIP	31
FORCE_DEFLATE	15
ZLIB_ENCODING_RAW	-15
ZLIB_ENCODING_GZIP	31
ZLIB_ENCODING_DEFLATE	15
CAL_GREGORIAN	0
CAL_JULIAN	1
CAL_JEWISH	2
CAL_FRENCH	3
CAL_NUM_CALS	4
CAL_DOW_DAYNO	0
CAL_DOW_SHORT	2
CAL_DOW_LONG	1
CAL_MONTH_GREGORIAN_SHORT	0
CAL_MONTH_GREGORIAN_LONG	1
CAL_MONTH_JULIAN_SHORT	2
CAL_MONTH_JULIAN_LONG	3
CAL_MONTH_JEWISH	4
CAL_MONTH_FRENCH	5
CAL_EASTER_DEFAULT	0
CAL_EASTER_ROMAN	1
CAL_EASTER_ALWAYS_GREGORIAN	2
CAL_EASTER_ALWAYS_JULIAN	3
CAL_JEWISH_ADD_ALAFIM_GERESH	2
CAL_JEWISH_ADD_ALAFIM	4
CAL_JEWISH_ADD_GERESHAYIM	8
XML_ELEMENT_NODE	1
XML_ATTRIBUTE_NODE	2
XML_TEXT_NODE	3
XML_CDATA_SECTION_NODE	4
XML_ENTITY_REF_NODE	5
XML_ENTITY_NODE	6
XML_PI_NODE	7
XML_COMMENT_NODE	8
XML_DOCUMENT_NODE	9
XML_DOCUMENT_TYPE_NODE	10
XML_DOCUMENT_FRAG_NODE	11
XML_NOTATION_NODE	12
XML_HTML_DOCUMENT_NODE	13
XML_DTD_NODE	14
XML_ELEMENT_DECL_NODE	15
XML_ATTRIBUTE_DECL_NODE	16
XML_ENTITY_DECL_NODE	17
XML_NAMESPACE_DECL_NODE	18
XML_LOCAL_NAMESPACE	18
XML_ATTRIBUTE_CDATA	1
XML_ATTRIBUTE_ID	2
XML_ATTRIBUTE_IDREF	3
XML_ATTRIBUTE_IDREFS	4
XML_ATTRIBUTE_ENTITY	6
XML_ATTRIBUTE_NMTOKEN	7
XML_ATTRIBUTE_NMTOKENS	8
XML_ATTRIBUTE_ENUMERATION	9
XML_ATTRIBUTE_NOTATION	10
DOM_PHP_ERR	0
DOM_INDEX_SIZE_ERR	1
DOMSTRING_SIZE_ERR	2
DOM_HIERARCHY_REQUEST_ERR	3
DOM_WRONG_DOCUMENT_ERR	4
DOM_INVALID_CHARACTER_ERR	5
DOM_NO_DATA_ALLOWED_ERR	6
DOM_NO_MODIFICATION_ALLOWED_ERR	7
DOM_NOT_FOUND_ERR	8
DOM_NOT_SUPPORTED_ERR	9
DOM_INUSE_ATTRIBUTE_ERR	10
DOM_INVALID_STATE_ERR	11
DOM_SYNTAX_ERR	12
DOM_INVALID_MODIFICATION_ERR	13
DOM_NAMESPACE_ERR	14
DOM_INVALID_ACCESS_ERR	15
DOM_VALIDATION_ERR	16
HASH_HMAC	1
MHASH_CRC32	0
MHASH_MD5	1
MHASH_SHA1	2
MHASH_HAVAL256	3
MHASH_RIPEMD160	5
MHASH_TIGER	7
MHASH_GOST	8
MHASH_CRC32B	9
MHASH_HAVAL224	10
MHASH_HAVAL192	11
MHASH_HAVAL160	12
MHASH_HAVAL128	13
MHASH_TIGER128	14
MHASH_TIGER160	15
MHASH_MD4	16
MHASH_SHA256	17
MHASH_ADLER32	18
MHASH_SHA224	19
MHASH_SHA512	20
MHASH_SHA384	21
MHASH_WHIRLPOOL	22
MHASH_RIPEMD128	23
MHASH_RIPEMD256	24
MHASH_RIPEMD320	25
MHASH_SNEFRU256	27
MHASH_MD2	28
MHASH_FNV132	29
MHASH_FNV1A32	30
MHASH_FNV164	31
MHASH_FNV1A64	32
MHASH_JOAAT	33
FILEINFO_NONE	0
FILEINFO_SYMLINK	2
FILEINFO_MIME	1040
FILEINFO_MIME_TYPE	16
FILEINFO_MIME_ENCODING	1024
FILEINFO_DEVICES	8
FILEINFO_CONTINUE	32
FILEINFO_PRESERVE_ATIME	128
FILEINFO_RAW	256
INPUT_POST	0
INPUT_GET	1
INPUT_COOKIE	2
INPUT_ENV	4
INPUT_SERVER	5
INPUT_SESSION	6
INPUT_REQUEST	99
FILTER_FLAG_NONE	0
FILTER_REQUIRE_SCALAR	33554432
FILTER_REQUIRE_ARRAY	16777216
FILTER_FORCE_ARRAY	67108864
FILTER_NULL_ON_FAILURE	134217728
FILTER_VALIDATE_INT	257
FILTER_VALIDATE_BOOLEAN	258
FILTER_VALIDATE_FLOAT	259
FILTER_VALIDATE_REGEXP	272
FILTER_VALIDATE_URL	273
FILTER_VALIDATE_EMAIL	274
FILTER_VALIDATE_IP	275
FILTER_VALIDATE_MAC	276
FILTER_DEFAULT	516
FILTER_UNSAFE_RAW	516
FILTER_SANITIZE_STRING	513
FILTER_SANITIZE_STRIPPED	513
FILTER_SANITIZE_ENCODED	514
FILTER_SANITIZE_SPECIAL_CHARS	515
FILTER_SANITIZE_FULL_SPECIAL_CHARS	522
FILTER_SANITIZE_EMAIL	517
FILTER_SANITIZE_URL	518
FILTER_SANITIZE_NUMBER_INT	519
FILTER_SANITIZE_NUMBER_FLOAT	520
FILTER_SANITIZE_MAGIC_QUOTES	521
FILTER_CALLBACK	1024
FILTER_FLAG_ALLOW_OCTAL	1
FILTER_FLAG_ALLOW_HEX	2
FILTER_FLAG_STRIP_LOW	4
FILTER_FLAG_STRIP_HIGH	8
FILTER_FLAG_STRIP_BACKTICK	512
FILTER_FLAG_ENCODE_LOW	16
FILTER_FLAG_ENCODE_HIGH	32
FILTER_FLAG_ENCODE_AMP	64
FILTER_FLAG_NO_ENCODE_QUOTES	128
FILTER_FLAG_EMPTY_STRING_NULL	256
FILTER_FLAG_ALLOW_FRACTION	4096
FILTER_FLAG_ALLOW_THOUSAND	8192
FILTER_FLAG_ALLOW_SCIENTIFIC	16384
FILTER_FLAG_SCHEME_REQUIRED	65536
FILTER_FLAG_HOST_REQUIRED	131072
FILTER_FLAG_PATH_REQUIRED	262144
FILTER_FLAG_QUERY_REQUIRED	524288
FILTER_FLAG_IPV4	1048576
FILTER_FLAG_IPV6	2097152
FILTER_FLAG_NO_RES_RANGE	4194304
FILTER_FLAG_NO_PRIV_RANGE	8388608
FTP_ASCII	1
FTP_TEXT	1
FTP_BINARY	2
FTP_IMAGE	2
FTP_AUTORESUME	-1
FTP_TIMEOUT_SEC	0
FTP_AUTOSEEK	1
FTP_USEPASVADDRESS	2
FTP_FAILED	0
FTP_FINISHED	1
FTP_MOREDATA	2
ICONV_IMPL	glibc
ICONV_VERSION	2.19
ICONV_MIME_DECODE_STRICT	1
ICONV_MIME_DECODE_CONTINUE_ON_ERROR	2
MB_OVERLOAD_MAIL	1
MB_OVERLOAD_STRING	2
MB_OVERLOAD_REGEX	4
MB_CASE_UPPER	0
MB_CASE_LOWER	1
MB_CASE_TITLE	2
PHP_SESSION_DISABLED	0
PHP_SESSION_NONE	1
PHP_SESSION_ACTIVE	2
POSIX_F_OK	0
POSIX_X_OK	1
POSIX_W_OK	2
POSIX_R_OK	4
POSIX_S_IFREG	32768
POSIX_S_IFCHR	8192
POSIX_S_IFBLK	24576
POSIX_S_IFIFO	4096
POSIX_S_IFSOCK	49152
CONNECTION_ABORTED	1
CONNECTION_NORMAL	0
CONNECTION_TIMEOUT	2
INI_USER	1
INI_PERDIR	2
INI_SYSTEM	4
INI_ALL	7
INI_SCANNER_NORMAL	0
INI_SCANNER_RAW	1
INI_SCANNER_TYPED	2
PHP_URL_SCHEME	0
PHP_URL_HOST	1
PHP_URL_PORT	2
PHP_URL_USER	3
PHP_URL_PASS	4
PHP_URL_PATH	5
PHP_URL_QUERY	6
PHP_URL_FRAGMENT	7
PHP_QUERY_RFC1738	1
PHP_QUERY_RFC3986	2
M_E	2.718281828459
M_LOG2E	1.442695040889
M_LOG10E	0.43429448190325
M_LN2	0.69314718055995
M_LN10	2.302585092994
M_PI	3.1415926535898
M_PI_2	1.5707963267949
M_PI_4	0.78539816339745
M_1_PI	0.31830988618379
M_2_PI	0.63661977236758
M_SQRTPI	1.7724538509055
M_2_SQRTPI	1.1283791670955
M_LNPI	1.1447298858494
M_EULER	0.57721566490153
M_SQRT2	1.4142135623731
M_SQRT1_2	0.70710678118655
M_SQRT3	1.7320508075689
INF	INF
NAN	NAN
PHP_ROUND_HALF_UP	1
PHP_ROUND_HALF_DOWN	2
PHP_ROUND_HALF_EVEN	3
PHP_ROUND_HALF_ODD	4
INFO_GENERAL	1
INFO_CREDITS	2
INFO_CONFIGURATION	4
INFO_MODULES	8
INFO_ENVIRONMENT	16
INFO_VARIABLES	32
INFO_LICENSE	64
INFO_ALL	4294967295
CREDITS_GROUP	1
CREDITS_GENERAL	2
CREDITS_SAPI	4
CREDITS_MODULES	8
CREDITS_DOCS	16
CREDITS_FULLPAGE	32
CREDITS_QA	64
CREDITS_ALL	4294967295
HTML_SPECIALCHARS	0
HTML_ENTITIES	1
ENT_COMPAT	2
ENT_QUOTES	3
ENT_NOQUOTES	0
ENT_IGNORE	4
ENT_SUBSTITUTE	8
ENT_DISALLOWED	128
ENT_HTML401	0
ENT_XML1	16
ENT_XHTML	32
ENT_HTML5	48
STR_PAD_LEFT	0
STR_PAD_RIGHT	1
STR_PAD_BOTH	2
PATHINFO_DIRNAME	1
PATHINFO_BASENAME	2
PATHINFO_EXTENSION	4
PATHINFO_FILENAME	8
CHAR_MAX	127
LC_CTYPE	0
LC_NUMERIC	1
LC_TIME	2
LC_COLLATE	3
LC_MONETARY	4
LC_ALL	6
LC_MESSAGES	5
SEEK_SET	0
SEEK_CUR	1
SEEK_END	2
LOCK_SH	1
LOCK_EX	2
LOCK_UN	3
LOCK_NB	4
STREAM_NOTIFY_CONNECT	2
STREAM_NOTIFY_AUTH_REQUIRED	3
STREAM_NOTIFY_AUTH_RESULT	10
STREAM_NOTIFY_MIME_TYPE_IS	4
STREAM_NOTIFY_FILE_SIZE_IS	5
STREAM_NOTIFY_REDIRECTED	6
STREAM_NOTIFY_PROGRESS	7
STREAM_NOTIFY_FAILURE	9
STREAM_NOTIFY_COMPLETED	8
STREAM_NOTIFY_RESOLVE	1
STREAM_NOTIFY_SEVERITY_INFO	0
STREAM_NOTIFY_SEVERITY_WARN	1
STREAM_NOTIFY_SEVERITY_ERR	2
STREAM_FILTER_READ	1
STREAM_FILTER_WRITE	2
STREAM_FILTER_ALL	3
STREAM_CLIENT_PERSISTENT	1
STREAM_CLIENT_ASYNC_CONNECT	2
STREAM_CLIENT_CONNECT	4
STREAM_CRYPTO_METHOD_ANY_CLIENT	63
STREAM_CRYPTO_METHOD_SSLv2_CLIENT	3
STREAM_CRYPTO_METHOD_SSLv3_CLIENT	5
STREAM_CRYPTO_METHOD_SSLv23_CLIENT	57
STREAM_CRYPTO_METHOD_TLS_CLIENT	9
STREAM_CRYPTO_METHOD_TLSv1_0_CLIENT	9
STREAM_CRYPTO_METHOD_TLSv1_1_CLIENT	17
STREAM_CRYPTO_METHOD_TLSv1_2_CLIENT	33
STREAM_CRYPTO_METHOD_ANY_SERVER	62
STREAM_CRYPTO_METHOD_SSLv2_SERVER	2
STREAM_CRYPTO_METHOD_SSLv3_SERVER	4
STREAM_CRYPTO_METHOD_SSLv23_SERVER	56
STREAM_CRYPTO_METHOD_TLS_SERVER	8
STREAM_CRYPTO_METHOD_TLSv1_0_SERVER	8
STREAM_CRYPTO_METHOD_TLSv1_1_SERVER	16
STREAM_CRYPTO_METHOD_TLSv1_2_SERVER	32
STREAM_SHUT_RD	0
STREAM_SHUT_WR	1
STREAM_SHUT_RDWR	2
STREAM_PF_INET	2
STREAM_PF_INET6	10
STREAM_PF_UNIX	1
STREAM_IPPROTO_IP	0
STREAM_IPPROTO_TCP	6
STREAM_IPPROTO_UDP	17
STREAM_IPPROTO_ICMP	1
STREAM_IPPROTO_RAW	255
STREAM_SOCK_STREAM	1
STREAM_SOCK_DGRAM	2
STREAM_SOCK_RAW	3
STREAM_SOCK_SEQPACKET	5
STREAM_SOCK_RDM	4
STREAM_PEEK	2
STREAM_OOB	1
STREAM_SERVER_BIND	4
STREAM_SERVER_LISTEN	8
FILE_USE_INCLUDE_PATH	1
FILE_IGNORE_NEW_LINES	2
FILE_SKIP_EMPTY_LINES	4
FILE_APPEND	8
FILE_NO_DEFAULT_CONTEXT	16
FILE_TEXT	0
FILE_BINARY	0
FNM_NOESCAPE	2
FNM_PATHNAME	1
FNM_PERIOD	4
FNM_CASEFOLD	16
PSFS_PASS_ON	2
PSFS_FEED_ME	1
PSFS_ERR_FATAL	0
PSFS_FLAG_NORMAL	0
PSFS_FLAG_FLUSH_INC	1
PSFS_FLAG_FLUSH_CLOSE	2
PASSWORD_DEFAULT	1
PASSWORD_BCRYPT	1
PASSWORD_BCRYPT_DEFAULT_COST	10
ABDAY_1	131072
ABDAY_2	131073
ABDAY_3	131074
ABDAY_4	131075
ABDAY_5	131076
ABDAY_6	131077
ABDAY_7	131078
DAY_1	131079
DAY_2	131080
DAY_3	131081
DAY_4	131082
DAY_5	131083
DAY_6	131084
DAY_7	131085
ABMON_1	131086
ABMON_2	131087
ABMON_3	131088
ABMON_4	131089
ABMON_5	131090
ABMON_6	131091
ABMON_7	131092
ABMON_8	131093
ABMON_9	131094
ABMON_10	131095
ABMON_11	131096
ABMON_12	131097
MON_1	131098
MON_2	131099
MON_3	131100
MON_4	131101
MON_5	131102
MON_6	131103
MON_7	131104
MON_8	131105
MON_9	131106
MON_10	131107
MON_11	131108
MON_12	131109
AM_STR	131110
PM_STR	131111
D_T_FMT	131112
D_FMT	131113
T_FMT	131114
T_FMT_AMPM	131115
ERA	131116
ERA_D_T_FMT	131120
ERA_D_FMT	131118
ERA_T_FMT	131121
ALT_DIGITS	131119
CRNCYSTR	262159
RADIXCHAR	65536
THOUSEP	65537
YESEXPR	327680
NOEXPR	327681
CODESET	14
CRYPT_SALT_LENGTH	123
CRYPT_STD_DES	1
CRYPT_EXT_DES	1
CRYPT_MD5	1
CRYPT_BLOWFISH	1
CRYPT_SHA256	1
CRYPT_SHA512	1
DIRECTORY_SEPARATOR	/
PATH_SEPARATOR	:
SCANDIR_SORT_ASCENDING	0
SCANDIR_SORT_DESCENDING	1
SCANDIR_SORT_NONE	2
GLOB_BRACE	1024
GLOB_MARK	2
GLOB_NOSORT	4
GLOB_NOCHECK	16
GLOB_NOESCAPE	64
GLOB_ERR	1
GLOB_ONLYDIR	8192
GLOB_AVAILABLE_FLAGS	9303
LOG_EMERG	0
LOG_ALERT	1
LOG_CRIT	2
LOG_ERR	3
LOG_WARNING	4
LOG_NOTICE	5
LOG_INFO	6
LOG_DEBUG	7
LOG_KERN	0
LOG_USER	8
LOG_MAIL	16
LOG_DAEMON	24
LOG_AUTH	32
LOG_SYSLOG	40
LOG_LPR	48
LOG_NEWS	56
LOG_UUCP	64
LOG_CRON	72
LOG_AUTHPRIV	80
LOG_LOCAL0	128
LOG_LOCAL1	136
LOG_LOCAL2	144
LOG_LOCAL3	152
LOG_LOCAL4	160
LOG_LOCAL5	168
LOG_LOCAL6	176
LOG_LOCAL7	184
LOG_PID	1
LOG_CONS	2
LOG_ODELAY	4
LOG_NDELAY	8
LOG_NOWAIT	16
LOG_PERROR	32
EXTR_OVERWRITE	0
EXTR_SKIP	1
EXTR_PREFIX_SAME	2
EXTR_PREFIX_ALL	3
EXTR_PREFIX_INVALID	4
EXTR_PREFIX_IF_EXISTS	5
EXTR_IF_EXISTS	6
EXTR_REFS	256
SORT_ASC	4
SORT_DESC	3
SORT_REGULAR	0
SORT_NUMERIC	1
SORT_STRING	2
SORT_LOCALE_STRING	5
SORT_NATURAL	6
SORT_FLAG_CASE	8
CASE_LOWER	0
CASE_UPPER	1
COUNT_NORMAL	0
COUNT_RECURSIVE	1
ARRAY_FILTER_USE_BOTH	1
ARRAY_FILTER_USE_KEY	2
ASSERT_ACTIVE	1
ASSERT_CALLBACK	2
ASSERT_BAIL	3
ASSERT_WARNING	4
ASSERT_QUIET_EVAL	5
STREAM_USE_PATH	1
STREAM_IGNORE_URL	2
STREAM_REPORT_ERRORS	8
STREAM_MUST_SEEK	16
STREAM_URL_STAT_LINK	1
STREAM_URL_STAT_QUIET	2
STREAM_MKDIR_RECURSIVE	1
STREAM_IS_URL	1
STREAM_OPTION_BLOCKING	1
STREAM_OPTION_READ_TIMEOUT	4
STREAM_OPTION_READ_BUFFER	2
STREAM_OPTION_WRITE_BUFFER	3
STREAM_BUFFER_NONE	0
STREAM_BUFFER_LINE	1
STREAM_BUFFER_FULL	2
STREAM_CAST_AS_STREAM	0
STREAM_CAST_FOR_SELECT	3
STREAM_META_TOUCH	1
STREAM_META_OWNER	3
STREAM_META_OWNER_NAME	2
STREAM_META_GROUP	5
STREAM_META_GROUP_NAME	4
STREAM_META_ACCESS	6
IMAGETYPE_GIF	1
IMAGETYPE_JPEG	2
IMAGETYPE_PNG	3
IMAGETYPE_SWF	4
IMAGETYPE_PSD	5
IMAGETYPE_BMP	6
IMAGETYPE_TIFF_II	7
IMAGETYPE_TIFF_MM	8
IMAGETYPE_JPC	9
IMAGETYPE_JP2	10
IMAGETYPE_JPX	11
IMAGETYPE_JB2	12
IMAGETYPE_SWC	13
IMAGETYPE_IFF	14
IMAGETYPE_WBMP	15
IMAGETYPE_JPEG2000	9
IMAGETYPE_XBM	16
IMAGETYPE_ICO	17
IMAGETYPE_UNKNOWN	0
IMAGETYPE_COUNT	18
DNS_A	1
DNS_NS	2
DNS_CNAME	16
DNS_SOA	32
DNS_PTR	2048
DNS_HINFO	4096
DNS_MX	16384
DNS_TXT	32768
DNS_SRV	33554432
DNS_NAPTR	67108864
DNS_AAAA	134217728
DNS_A6	16777216
DNS_ANY	268435456
DNS_ALL	251713587
SOAP_1_1	1
SOAP_1_2	2
SOAP_PERSISTENCE_SESSION	1
SOAP_PERSISTENCE_REQUEST	2
SOAP_FUNCTIONS_ALL	999
SOAP_ENCODED	1
SOAP_LITERAL	2
SOAP_RPC	1
SOAP_DOCUMENT	2
SOAP_ACTOR_NEXT	1
SOAP_ACTOR_NONE	2
SOAP_ACTOR_UNLIMATERECEIVER	3
SOAP_COMPRESSION_ACCEPT	32
SOAP_COMPRESSION_GZIP	0
SOAP_COMPRESSION_DEFLATE	16
SOAP_AUTHENTICATION_BASIC	0
SOAP_AUTHENTICATION_DIGEST	1
UNKNOWN_TYPE	999998
XSD_STRING	101
XSD_BOOLEAN	102
XSD_DECIMAL	103
XSD_FLOAT	104
XSD_DOUBLE	105
XSD_DURATION	106
XSD_DATETIME	107
XSD_TIME	108
XSD_DATE	109
XSD_GYEARMONTH	110
XSD_GYEAR	111
XSD_GMONTHDAY	112
XSD_GDAY	113
XSD_GMONTH	114
XSD_HEXBINARY	115
XSD_BASE64BINARY	116
XSD_ANYURI	117
XSD_QNAME	118
XSD_NOTATION	119
XSD_NORMALIZEDSTRING	120
XSD_TOKEN	121
XSD_LANGUAGE	122
XSD_NMTOKEN	123
XSD_NAME	124
XSD_NCNAME	125
XSD_ID	126
XSD_IDREF	127
XSD_IDREFS	128
XSD_ENTITY	129
XSD_ENTITIES	130
XSD_INTEGER	131
XSD_NONPOSITIVEINTEGER	132
XSD_NEGATIVEINTEGER	133
XSD_LONG	134
XSD_INT	135
XSD_SHORT	136
XSD_BYTE	137
XSD_NONNEGATIVEINTEGER	138
XSD_UNSIGNEDLONG	139
XSD_UNSIGNEDINT	140
XSD_UNSIGNEDSHORT	141
XSD_UNSIGNEDBYTE	142
XSD_POSITIVEINTEGER	143
XSD_NMTOKENS	144
XSD_ANYTYPE	145
XSD_ANYXML	147
APACHE_MAP	200
SOAP_ENC_OBJECT	301
SOAP_ENC_ARRAY	300
XSD_1999_TIMEINSTANT	401
XSD_NAMESPACE	http://www.w3.org/2001/XMLSchema
XSD_1999_NAMESPACE	http://www.w3.org/1999/XMLSchema
SOAP_SINGLE_ELEMENT_ARRAYS	1
SOAP_WAIT_ONE_WAY_CALLS	2
SOAP_USE_XSI_ARRAY_TYPE	4
WSDL_CACHE_NONE	0
WSDL_CACHE_DISK	1
WSDL_CACHE_MEMORY	2
WSDL_CACHE_BOTH	3
SOAP_SSL_METHOD_TLS	0
SOAP_SSL_METHOD_SSLv2	1
SOAP_SSL_METHOD_SSLv3	2
SOAP_SSL_METHOD_SSLv23	3
AF_UNIX	1
AF_INET	2
AF_INET6	10
SOCK_STREAM	1
SOCK_DGRAM	2
SOCK_RAW	3
SOCK_SEQPACKET	5
SOCK_RDM	4
MSG_OOB	1
MSG_WAITALL	256
MSG_CTRUNC	8
MSG_TRUNC	32
MSG_PEEK	2
MSG_DONTROUTE	4
MSG_EOR	128
MSG_EOF	512
MSG_CONFIRM	2048
MSG_ERRQUEUE	8192
MSG_NOSIGNAL	16384
MSG_DONTWAIT	64
MSG_MORE	32768
MSG_WAITFORONE	65536
MSG_CMSG_CLOEXEC	1073741824
SO_DEBUG	1
SO_REUSEADDR	2
SO_REUSEPORT	15
SO_KEEPALIVE	9
SO_DONTROUTE	5
SO_LINGER	13
SO_BROADCAST	6
SO_OOBINLINE	10
SO_SNDBUF	7
SO_RCVBUF	8
SO_SNDLOWAT	19
SO_RCVLOWAT	18
SO_SNDTIMEO	21
SO_RCVTIMEO	20
SO_TYPE	3
SO_ERROR	4
SO_BINDTODEVICE	25
SOL_SOCKET	1
SOMAXCONN	128
TCP_NODELAY	1
PHP_NORMAL_READ	1
PHP_BINARY_READ	2
MCAST_JOIN_GROUP	42
MCAST_LEAVE_GROUP	45
MCAST_BLOCK_SOURCE	43
MCAST_UNBLOCK_SOURCE	44
MCAST_JOIN_SOURCE_GROUP	46
MCAST_LEAVE_SOURCE_GROUP	47
IP_MULTICAST_IF	32
IP_MULTICAST_TTL	33
IP_MULTICAST_LOOP	34
IPV6_MULTICAST_IF	17
IPV6_MULTICAST_HOPS	18
IPV6_MULTICAST_LOOP	19
SOCKET_EPERM	1
SOCKET_ENOENT	2
SOCKET_EINTR	4
SOCKET_EIO	5
SOCKET_ENXIO	6
SOCKET_E2BIG	7
SOCKET_EBADF	9
SOCKET_EAGAIN	11
SOCKET_ENOMEM	12
SOCKET_EACCES	13
SOCKET_EFAULT	14
SOCKET_ENOTBLK	15
SOCKET_EBUSY	16
SOCKET_EEXIST	17
SOCKET_EXDEV	18
SOCKET_ENODEV	19
SOCKET_ENOTDIR	20
SOCKET_EISDIR	21
SOCKET_EINVAL	22
SOCKET_ENFILE	23
SOCKET_EMFILE	24
SOCKET_ENOTTY	25
SOCKET_ENOSPC	28
SOCKET_ESPIPE	29
SOCKET_EROFS	30
SOCKET_EMLINK	31
SOCKET_EPIPE	32
SOCKET_ENAMETOOLONG	36
SOCKET_ENOLCK	37
SOCKET_ENOSYS	38
SOCKET_ENOTEMPTY	39
SOCKET_ELOOP	40
SOCKET_EWOULDBLOCK	11
SOCKET_ENOMSG	42
SOCKET_EIDRM	43
SOCKET_ECHRNG	44
SOCKET_EL2NSYNC	45
SOCKET_EL3HLT	46
SOCKET_EL3RST	47
SOCKET_ELNRNG	48
SOCKET_EUNATCH	49
SOCKET_ENOCSI	50
SOCKET_EL2HLT	51
SOCKET_EBADE	52
SOCKET_EBADR	53
SOCKET_EXFULL	54
SOCKET_ENOANO	55
SOCKET_EBADRQC	56
SOCKET_EBADSLT	57
SOCKET_ENOSTR	60
SOCKET_ENODATA	61
SOCKET_ETIME	62
SOCKET_ENOSR	63
SOCKET_ENONET	64
SOCKET_EREMOTE	66
SOCKET_ENOLINK	67
SOCKET_EADV	68
SOCKET_ESRMNT	69
SOCKET_ECOMM	70
SOCKET_EPROTO	71
SOCKET_EMULTIHOP	72
SOCKET_EBADMSG	74
SOCKET_ENOTUNIQ	76
SOCKET_EBADFD	77
SOCKET_EREMCHG	78
SOCKET_ERESTART	85
SOCKET_ESTRPIPE	86
SOCKET_EUSERS	87
SOCKET_ENOTSOCK	88
SOCKET_EDESTADDRREQ	89
SOCKET_EMSGSIZE	90
SOCKET_EPROTOTYPE	91
SOCKET_ENOPROTOOPT	92
SOCKET_EPROTONOSUPPORT	93
SOCKET_ESOCKTNOSUPPORT	94
SOCKET_EOPNOTSUPP	95
SOCKET_EPFNOSUPPORT	96
SOCKET_EAFNOSUPPORT	97
SOCKET_EADDRINUSE	98
SOCKET_EADDRNOTAVAIL	99
SOCKET_ENETDOWN	100
SOCKET_ENETUNREACH	101
SOCKET_ENETRESET	102
SOCKET_ECONNABORTED	103
SOCKET_ECONNRESET	104
SOCKET_ENOBUFS	105
SOCKET_EISCONN	106
SOCKET_ENOTCONN	107
SOCKET_ESHUTDOWN	108
SOCKET_ETOOMANYREFS	109
SOCKET_ETIMEDOUT	110
SOCKET_ECONNREFUSED	111
SOCKET_EHOSTDOWN	112
SOCKET_EHOSTUNREACH	113
SOCKET_EALREADY	114
SOCKET_EINPROGRESS	115
SOCKET_EISNAM	120
SOCKET_EREMOTEIO	121
SOCKET_EDQUOT	122
SOCKET_ENOMEDIUM	123
SOCKET_EMEDIUMTYPE	124
IPPROTO_IP	0
IPPROTO_IPV6	41
SOL_TCP	6
SOL_UDP	17
IPV6_UNICAST_HOPS	16
IPV6_RECVPKTINFO	49
IPV6_PKTINFO	50
IPV6_RECVHOPLIMIT	51
IPV6_HOPLIMIT	52
IPV6_RECVTCLASS	66
IPV6_TCLASS	67
SCM_RIGHTS	1
SCM_CREDENTIALS	2
SO_PASSCRED	16
EXIF_USE_MBSTRING	1
MSG_IPC_NOWAIT	1
MSG_EAGAIN	11
MSG_ENOMSG	42
MSG_NOERROR	2
MSG_EXCEPT	4
T_REQUIRE_ONCE	258
T_REQUIRE	259
T_EVAL	260
T_INCLUDE_ONCE	261
T_INCLUDE	262
T_LOGICAL_OR	263
T_LOGICAL_XOR	264
T_LOGICAL_AND	265
T_PRINT	266
T_YIELD	267
T_POW_EQUAL	268
T_SR_EQUAL	269
T_SL_EQUAL	270
T_XOR_EQUAL	271
T_OR_EQUAL	272
T_AND_EQUAL	273
T_MOD_EQUAL	274
T_CONCAT_EQUAL	275
T_DIV_EQUAL	276
T_MUL_EQUAL	277
T_MINUS_EQUAL	278
T_PLUS_EQUAL	279
T_BOOLEAN_OR	280
T_BOOLEAN_AND	281
T_IS_NOT_IDENTICAL	282
T_IS_IDENTICAL	283
T_IS_NOT_EQUAL	284
T_IS_EQUAL	285
T_IS_GREATER_OR_EQUAL	286
T_IS_SMALLER_OR_EQUAL	287
T_SR	288
T_SL	289
T_INSTANCEOF	290
T_UNSET_CAST	291
T_BOOL_CAST	292
T_OBJECT_CAST	293
T_ARRAY_CAST	294
T_STRING_CAST	295
T_DOUBLE_CAST	296
T_INT_CAST	297
T_DEC	298
T_INC	299
T_POW	300
T_CLONE	301
T_NEW	302
T_EXIT	303
T_IF	304
T_ELSEIF	305
T_ELSE	306
T_ENDIF	307
T_LNUMBER	308
T_DNUMBER	309
T_STRING	310
T_STRING_VARNAME	311
T_VARIABLE	312
T_NUM_STRING	313
T_INLINE_HTML	314
T_CHARACTER	315
T_BAD_CHARACTER	316
T_ENCAPSED_AND_WHITESPACE	317
T_CONSTANT_ENCAPSED_STRING	318
T_ECHO	319
T_DO	320
T_WHILE	321
T_ENDWHILE	322
T_FOR	323
T_ENDFOR	324
T_FOREACH	325
T_ENDFOREACH	326
T_DECLARE	327
T_ENDDECLARE	328
T_AS	329
T_SWITCH	330
T_ENDSWITCH	331
T_CASE	332
T_DEFAULT	333
T_BREAK	334
T_CONTINUE	335
T_GOTO	336
T_FUNCTION	337
T_CONST	338
T_RETURN	339
T_TRY	340
T_CATCH	341
T_FINALLY	342
T_THROW	343
T_USE	344
T_INSTEADOF	345
T_GLOBAL	346
T_PUBLIC	347
T_PROTECTED	348
T_PRIVATE	349
T_FINAL	350
T_ABSTRACT	351
T_STATIC	352
T_VAR	353
T_UNSET	354
T_ISSET	355
T_EMPTY	356
T_HALT_COMPILER	357
T_CLASS	358
T_TRAIT	359
T_INTERFACE	360
T_EXTENDS	361
T_IMPLEMENTS	362
T_OBJECT_OPERATOR	363
T_DOUBLE_ARROW	364
T_LIST	365
T_ARRAY	366
T_CALLABLE	367
T_CLASS_C	368
T_TRAIT_C	369
T_METHOD_C	370
T_FUNC_C	371
T_LINE	372
T_FILE	373
T_COMMENT	374
T_DOC_COMMENT	375
T_OPEN_TAG	376
T_OPEN_TAG_WITH_ECHO	377
T_CLOSE_TAG	378
T_WHITESPACE	379
T_START_HEREDOC	380
T_END_HEREDOC	381
T_DOLLAR_OPEN_CURLY_BRACES	382
T_CURLY_OPEN	383
T_PAAMAYIM_NEKUDOTAYIM	384
T_NAMESPACE	385
T_NS_C	386
T_DIR	387
T_NS_SEPARATOR	388
T_ELLIPSIS	389
T_DOUBLE_COLON	384
XML_ERROR_NONE	0
XML_ERROR_NO_MEMORY	1
XML_ERROR_SYNTAX	2
XML_ERROR_NO_ELEMENTS	3
XML_ERROR_INVALID_TOKEN	4
XML_ERROR_UNCLOSED_TOKEN	5
XML_ERROR_PARTIAL_CHAR	6
XML_ERROR_TAG_MISMATCH	7
XML_ERROR_DUPLICATE_ATTRIBUTE	8
XML_ERROR_JUNK_AFTER_DOC_ELEMENT	9
XML_ERROR_PARAM_ENTITY_REF	10
XML_ERROR_UNDEFINED_ENTITY	11
XML_ERROR_RECURSIVE_ENTITY_REF	12
XML_ERROR_ASYNC_ENTITY	13
XML_ERROR_BAD_CHAR_REF	14
XML_ERROR_BINARY_ENTITY_REF	15
XML_ERROR_ATTRIBUTE_EXTERNAL_ENTITY_REF	16
XML_ERROR_MISPLACED_XML_PI	17
XML_ERROR_UNKNOWN_ENCODING	18
XML_ERROR_INCORRECT_ENCODING	19
XML_ERROR_UNCLOSED_CDATA_SECTION	20
XML_ERROR_EXTERNAL_ENTITY_HANDLING	21
XML_OPTION_CASE_FOLDING	1
XML_OPTION_TARGET_ENCODING	2
XML_OPTION_SKIP_TAGSTART	3
XML_OPTION_SKIP_WHITE	4
XML_SAX_IMPL	libxml
CURLOPT_AUTOREFERER	58
CURLOPT_BINARYTRANSFER	19914
CURLOPT_BUFFERSIZE	98
CURLOPT_CAINFO	10065
CURLOPT_CAPATH	10097
CURLOPT_CONNECTTIMEOUT	78
CURLOPT_COOKIE	10022
CURLOPT_COOKIEFILE	10031
CURLOPT_COOKIEJAR	10082
CURLOPT_COOKIESESSION	96
CURLOPT_CRLF	27
CURLOPT_CUSTOMREQUEST	10036
CURLOPT_DNS_CACHE_TIMEOUT	92
CURLOPT_DNS_USE_GLOBAL_CACHE	91
CURLOPT_EGDSOCKET	10077
CURLOPT_ENCODING	10102
CURLOPT_FAILONERROR	45
CURLOPT_FILE	10001
CURLOPT_FILETIME	69
CURLOPT_FOLLOWLOCATION	52
CURLOPT_FORBID_REUSE	75
CURLOPT_FRESH_CONNECT	74
CURLOPT_FTPAPPEND	50
CURLOPT_FTPLISTONLY	48
CURLOPT_FTPPORT	10017
CURLOPT_FTP_USE_EPRT	106
CURLOPT_FTP_USE_EPSV	85
CURLOPT_HEADER	42
CURLOPT_HEADERFUNCTION	20079
CURLOPT_HTTP200ALIASES	10104
CURLOPT_HTTPGET	80
CURLOPT_HTTPHEADER	10023
CURLOPT_HTTPPROXYTUNNEL	61
CURLOPT_HTTP_VERSION	84
CURLOPT_INFILE	10009
CURLOPT_INFILESIZE	14
CURLOPT_INTERFACE	10062
CURLOPT_KRB4LEVEL	10063
CURLOPT_LOW_SPEED_LIMIT	19
CURLOPT_LOW_SPEED_TIME	20
CURLOPT_MAXCONNECTS	71
CURLOPT_MAXREDIRS	68
CURLOPT_NETRC	51
CURLOPT_NOBODY	44
CURLOPT_NOPROGRESS	43
CURLOPT_NOSIGNAL	99
CURLOPT_PORT	3
CURLOPT_POST	47
CURLOPT_POSTFIELDS	10015
CURLOPT_POSTQUOTE	10039
CURLOPT_PREQUOTE	10093
CURLOPT_PRIVATE	10103
CURLOPT_PROGRESSFUNCTION	20056
CURLOPT_PROXY	10004
CURLOPT_PROXYPORT	59
CURLOPT_PROXYTYPE	101
CURLOPT_PROXYUSERPWD	10006
CURLOPT_PUT	54
CURLOPT_QUOTE	10028
CURLOPT_RANDOM_FILE	10076
CURLOPT_RANGE	10007
CURLOPT_READDATA	10009
CURLOPT_READFUNCTION	20012
CURLOPT_REFERER	10016
CURLOPT_RESUME_FROM	21
CURLOPT_RETURNTRANSFER	19913
CURLOPT_SHARE	10100
CURLOPT_SSLCERT	10025
CURLOPT_SSLCERTPASSWD	10026
CURLOPT_SSLCERTTYPE	10086
CURLOPT_SSLENGINE	10089
CURLOPT_SSLENGINE_DEFAULT	90
CURLOPT_SSLKEY	10087
CURLOPT_SSLKEYPASSWD	10026
CURLOPT_SSLKEYTYPE	10088
CURLOPT_SSLVERSION	32
CURLOPT_SSL_CIPHER_LIST	10083
CURLOPT_SSL_VERIFYHOST	81
CURLOPT_SSL_VERIFYPEER	64
CURLOPT_STDERR	10037
CURLOPT_TELNETOPTIONS	10070
CURLOPT_TIMECONDITION	33
CURLOPT_TIMEOUT	13
CURLOPT_TIMEVALUE	34
CURLOPT_TRANSFERTEXT	53
CURLOPT_UNRESTRICTED_AUTH	105
CURLOPT_UPLOAD	46
CURLOPT_URL	10002
CURLOPT_USERAGENT	10018
CURLOPT_USERPWD	10005
CURLOPT_VERBOSE	41
CURLOPT_WRITEFUNCTION	20011
CURLOPT_WRITEHEADER	10029
CURLE_ABORTED_BY_CALLBACK	42
CURLE_BAD_CALLING_ORDER	44
CURLE_BAD_CONTENT_ENCODING	61
CURLE_BAD_DOWNLOAD_RESUME	36
CURLE_BAD_FUNCTION_ARGUMENT	43
CURLE_BAD_PASSWORD_ENTERED	46
CURLE_COULDNT_CONNECT	7
CURLE_COULDNT_RESOLVE_HOST	6
CURLE_COULDNT_RESOLVE_PROXY	5
CURLE_FAILED_INIT	2
CURLE_FILE_COULDNT_READ_FILE	37
CURLE_FTP_ACCESS_DENIED	9
CURLE_FTP_BAD_DOWNLOAD_RESUME	36
CURLE_FTP_CANT_GET_HOST	15
CURLE_FTP_CANT_RECONNECT	16
CURLE_FTP_COULDNT_GET_SIZE	32
CURLE_FTP_COULDNT_RETR_FILE	19
CURLE_FTP_COULDNT_SET_ASCII	29
CURLE_FTP_COULDNT_SET_BINARY	17
CURLE_FTP_COULDNT_STOR_FILE	25
CURLE_FTP_COULDNT_USE_REST	31
CURLE_FTP_PARTIAL_FILE	18
CURLE_FTP_PORT_FAILED	30
CURLE_FTP_QUOTE_ERROR	21
CURLE_FTP_USER_PASSWORD_INCORRECT	10
CURLE_FTP_WEIRD_227_FORMAT	14
CURLE_FTP_WEIRD_PASS_REPLY	11
CURLE_FTP_WEIRD_PASV_REPLY	13
CURLE_FTP_WEIRD_SERVER_REPLY	8
CURLE_FTP_WEIRD_USER_REPLY	12
CURLE_FTP_WRITE_ERROR	20
CURLE_FUNCTION_NOT_FOUND	41
CURLE_GOT_NOTHING	52
CURLE_HTTP_NOT_FOUND	22
CURLE_HTTP_PORT_FAILED	45
CURLE_HTTP_POST_ERROR	34
CURLE_HTTP_RANGE_ERROR	33
CURLE_HTTP_RETURNED_ERROR	22
CURLE_LDAP_CANNOT_BIND	38
CURLE_LDAP_SEARCH_FAILED	39
CURLE_LIBRARY_NOT_FOUND	40
CURLE_MALFORMAT_USER	24
CURLE_OBSOLETE	50
CURLE_OK	0
CURLE_OPERATION_TIMEDOUT	28
CURLE_OPERATION_TIMEOUTED	28
CURLE_OUT_OF_MEMORY	27
CURLE_PARTIAL_FILE	18
CURLE_READ_ERROR	26
CURLE_RECV_ERROR	56
CURLE_SEND_ERROR	55
CURLE_SHARE_IN_USE	57
CURLE_SSL_CACERT	60
CURLE_SSL_CERTPROBLEM	58
CURLE_SSL_CIPHER	59
CURLE_SSL_CONNECT_ERROR	35
CURLE_SSL_ENGINE_NOTFOUND	53
CURLE_SSL_ENGINE_SETFAILED	54
CURLE_SSL_PEER_CERTIFICATE	51
CURLE_TELNET_OPTION_SYNTAX	49
CURLE_TOO_MANY_REDIRECTS	47
CURLE_UNKNOWN_TELNET_OPTION	48
CURLE_UNSUPPORTED_PROTOCOL	1
CURLE_URL_MALFORMAT	3
CURLE_URL_MALFORMAT_USER	4
CURLE_WRITE_ERROR	23
CURLINFO_CONNECT_TIME	3145733
CURLINFO_CONTENT_LENGTH_DOWNLOAD	3145743
CURLINFO_CONTENT_LENGTH_UPLOAD	3145744
CURLINFO_CONTENT_TYPE	1048594
CURLINFO_EFFECTIVE_URL	1048577
CURLINFO_FILETIME	2097166
CURLINFO_HEADER_OUT	2
CURLINFO_HEADER_SIZE	2097163
CURLINFO_HTTP_CODE	2097154
CURLINFO_LASTONE	43
CURLINFO_NAMELOOKUP_TIME	3145732
CURLINFO_PRETRANSFER_TIME	3145734
CURLINFO_PRIVATE	1048597
CURLINFO_REDIRECT_COUNT	2097172
CURLINFO_REDIRECT_TIME	3145747
CURLINFO_REQUEST_SIZE	2097164
CURLINFO_SIZE_DOWNLOAD	3145736
CURLINFO_SIZE_UPLOAD	3145735
CURLINFO_SPEED_DOWNLOAD	3145737
CURLINFO_SPEED_UPLOAD	3145738
CURLINFO_SSL_VERIFYRESULT	2097165
CURLINFO_STARTTRANSFER_TIME	3145745
CURLINFO_TOTAL_TIME	3145731
CURLMSG_DONE	1
CURLVERSION_NOW	3
CURLM_BAD_EASY_HANDLE	2
CURLM_BAD_HANDLE	1
CURLM_CALL_MULTI_PERFORM	-1
CURLM_INTERNAL_ERROR	4
CURLM_OK	0
CURLM_OUT_OF_MEMORY	3
CURLM_ADDED_ALREADY	7
CURLPROXY_HTTP	0
CURLPROXY_SOCKS4	4
CURLPROXY_SOCKS5	5
CURLPROXY_SOCKS4A	6
CURLPROXY_SOCKS5_HOSTNAME	7
CURLSHOPT_NONE	0
CURLSHOPT_SHARE	1
CURLSHOPT_UNSHARE	2
CURL_HTTP_VERSION_1_0	1
CURL_HTTP_VERSION_1_1	2
CURL_HTTP_VERSION_2_0	3
CURL_HTTP_VERSION_NONE	0
CURL_LOCK_DATA_COOKIE	2
CURL_LOCK_DATA_DNS	3
CURL_LOCK_DATA_SSL_SESSION	4
CURL_NETRC_IGNORED	0
CURL_NETRC_OPTIONAL	1
CURL_NETRC_REQUIRED	2
CURL_SSLVERSION_DEFAULT	0
CURL_SSLVERSION_SSLv2	2
CURL_SSLVERSION_SSLv3	3
CURL_SSLVERSION_TLSv1	1
CURL_TIMECOND_IFMODSINCE	1
CURL_TIMECOND_IFUNMODSINCE	2
CURL_TIMECOND_LASTMOD	3
CURL_TIMECOND_NONE	0
CURL_VERSION_IPV6	1
CURL_VERSION_KERBEROS4	2
CURL_VERSION_LIBZ	8
CURL_VERSION_SSL	4
CURL_VERSION_HTTP2	65536
CURLOPT_HTTPAUTH	107
CURLAUTH_ANY	-17
CURLAUTH_ANYSAFE	-18
CURLAUTH_BASIC	1
CURLAUTH_DIGEST	2
CURLAUTH_GSSNEGOTIATE	4
CURLAUTH_NONE	0
CURLAUTH_NTLM	8
CURLINFO_HTTP_CONNECTCODE	2097174
CURLOPT_FTP_CREATE_MISSING_DIRS	110
CURLOPT_PROXYAUTH	111
CURLE_FILESIZE_EXCEEDED	63
CURLE_LDAP_INVALID_URL	62
CURLINFO_HTTPAUTH_AVAIL	2097175
CURLINFO_RESPONSE_CODE	2097154
CURLINFO_PROXYAUTH_AVAIL	2097176
CURLOPT_FTP_RESPONSE_TIMEOUT	112
CURLOPT_IPRESOLVE	113
CURLOPT_MAXFILESIZE	114
CURL_IPRESOLVE_V4	1
CURL_IPRESOLVE_V6	2
CURL_IPRESOLVE_WHATEVER	0
CURLE_FTP_SSL_FAILED	64
CURLFTPSSL_ALL	3
CURLFTPSSL_CONTROL	2
CURLFTPSSL_NONE	0
CURLFTPSSL_TRY	1
CURLOPT_FTP_SSL	119
CURLOPT_NETRC_FILE	10118
CURLFTPAUTH_DEFAULT	0
CURLFTPAUTH_SSL	1
CURLFTPAUTH_TLS	2
CURLOPT_FTPSSLAUTH	129
CURLOPT_FTP_ACCOUNT	10134
CURLOPT_TCP_NODELAY	121
CURLINFO_OS_ERRNO	2097177
CURLINFO_NUM_CONNECTS	2097178
CURLINFO_SSL_ENGINES	4194331
CURLINFO_COOKIELIST	4194332
CURLOPT_COOKIELIST	10135
CURLOPT_IGNORE_CONTENT_LENGTH	136
CURLOPT_FTP_SKIP_PASV_IP	137
CURLOPT_FTP_FILEMETHOD	138
CURLOPT_CONNECT_ONLY	141
CURLOPT_LOCALPORT	139
CURLOPT_LOCALPORTRANGE	140
CURLFTPMETHOD_MULTICWD	1
CURLFTPMETHOD_NOCWD	2
CURLFTPMETHOD_SINGLECWD	3
CURLINFO_FTP_ENTRY_PATH	1048606
CURLOPT_FTP_ALTERNATIVE_TO_USER	10147
CURLOPT_MAX_RECV_SPEED_LARGE	30146
CURLOPT_MAX_SEND_SPEED_LARGE	30145
CURLOPT_SSL_SESSIONID_CACHE	150
CURLMOPT_PIPELINING	3
CURLE_SSH	79
CURLOPT_FTP_SSL_CCC	154
CURLOPT_SSH_AUTH_TYPES	151
CURLOPT_SSH_PRIVATE_KEYFILE	10153
CURLOPT_SSH_PUBLIC_KEYFILE	10152
CURLFTPSSL_CCC_ACTIVE	2
CURLFTPSSL_CCC_NONE	0
CURLFTPSSL_CCC_PASSIVE	1
CURLOPT_CONNECTTIMEOUT_MS	156
CURLOPT_HTTP_CONTENT_DECODING	158
CURLOPT_HTTP_TRANSFER_DECODING	157
CURLOPT_TIMEOUT_MS	155
CURLMOPT_MAXCONNECTS	6
CURLOPT_KRBLEVEL	10063
CURLOPT_NEW_DIRECTORY_PERMS	160
CURLOPT_NEW_FILE_PERMS	159
CURLOPT_APPEND	50
CURLOPT_DIRLISTONLY	48
CURLOPT_USE_SSL	119
CURLUSESSL_ALL	3
CURLUSESSL_CONTROL	2
CURLUSESSL_NONE	0
CURLUSESSL_TRY	1
CURLOPT_SSH_HOST_PUBLIC_KEY_MD5	10162
CURLOPT_PROXY_TRANSFER_MODE	166
CURLPAUSE_ALL	5
CURLPAUSE_CONT	0
CURLPAUSE_RECV	1
CURLPAUSE_RECV_CONT	0
CURLPAUSE_SEND	4
CURLPAUSE_SEND_CONT	0
CURL_READFUNC_PAUSE	268435457
CURL_WRITEFUNC_PAUSE	268435457
CURLINFO_REDIRECT_URL	1048607
CURLINFO_APPCONNECT_TIME	3145761
CURLINFO_PRIMARY_IP	1048608
CURLOPT_ADDRESS_SCOPE	171
CURLOPT_CRLFILE	10169
CURLOPT_ISSUERCERT	10170
CURLOPT_KEYPASSWD	10026
CURLSSH_AUTH_ANY	-1
CURLSSH_AUTH_DEFAULT	-1
CURLSSH_AUTH_HOST	4
CURLSSH_AUTH_KEYBOARD	8
CURLSSH_AUTH_NONE	0
CURLSSH_AUTH_PASSWORD	2
CURLSSH_AUTH_PUBLICKEY	1
CURLINFO_CERTINFO	4194338
CURLOPT_CERTINFO	172
CURLOPT_PASSWORD	10174
CURLOPT_POSTREDIR	161
CURLOPT_PROXYPASSWORD	10176
CURLOPT_PROXYUSERNAME	10175
CURLOPT_USERNAME	10173
CURLAUTH_DIGEST_IE	16
CURLINFO_CONDITION_UNMET	2097187
CURLOPT_NOPROXY	10177
CURLOPT_PROTOCOLS	181
CURLOPT_REDIR_PROTOCOLS	182
CURLOPT_SOCKS5_GSSAPI_NEC	180
CURLOPT_SOCKS5_GSSAPI_SERVICE	10179
CURLOPT_TFTP_BLKSIZE	178
CURLPROTO_ALL	-1
CURLPROTO_DICT	512
CURLPROTO_FILE	1024
CURLPROTO_FTP	4
CURLPROTO_FTPS	8
CURLPROTO_HTTP	1
CURLPROTO_HTTPS	2
CURLPROTO_LDAP	128
CURLPROTO_LDAPS	256
CURLPROTO_SCP	16
CURLPROTO_SFTP	32
CURLPROTO_TELNET	64
CURLPROTO_TFTP	2048
CURLOPT_SSH_KNOWNHOSTS	10183
CURLINFO_RTSP_CLIENT_CSEQ	2097189
CURLINFO_RTSP_CSEQ_RECV	2097191
CURLINFO_RTSP_SERVER_CSEQ	2097190
CURLINFO_RTSP_SESSION_ID	1048612
CURLOPT_FTP_USE_PRET	188
CURLOPT_MAIL_FROM	10186
CURLOPT_MAIL_RCPT	10187
CURLOPT_RTSP_CLIENT_CSEQ	193
CURLOPT_RTSP_REQUEST	189
CURLOPT_RTSP_SERVER_CSEQ	194
CURLOPT_RTSP_SESSION_ID	10190
CURLOPT_RTSP_STREAM_URI	10191
CURLOPT_RTSP_TRANSPORT	10192
CURLPROTO_IMAP	4096
CURLPROTO_IMAPS	8192
CURLPROTO_POP3	16384
CURLPROTO_POP3S	32768
CURLPROTO_RTSP	262144
CURLPROTO_SMTP	65536
CURLPROTO_SMTPS	131072
CURL_RTSPREQ_ANNOUNCE	3
CURL_RTSPREQ_DESCRIBE	2
CURL_RTSPREQ_GET_PARAMETER	8
CURL_RTSPREQ_OPTIONS	1
CURL_RTSPREQ_PAUSE	6
CURL_RTSPREQ_PLAY	5
CURL_RTSPREQ_RECEIVE	11
CURL_RTSPREQ_RECORD	10
CURL_RTSPREQ_SETUP	4
CURL_RTSPREQ_SET_PARAMETER	9
CURL_RTSPREQ_TEARDOWN	7
CURLINFO_LOCAL_IP	1048617
CURLINFO_LOCAL_PORT	2097194
CURLINFO_PRIMARY_PORT	2097192
CURLOPT_FNMATCH_FUNCTION	20200
CURLOPT_WILDCARDMATCH	197
CURLPROTO_RTMP	524288
CURLPROTO_RTMPE	2097152
CURLPROTO_RTMPS	8388608
CURLPROTO_RTMPT	1048576
CURLPROTO_RTMPTE	4194304
CURLPROTO_RTMPTS	16777216
CURL_FNMATCHFUNC_FAIL	2
CURL_FNMATCHFUNC_MATCH	0
CURL_FNMATCHFUNC_NOMATCH	1
CURLPROTO_GOPHER	33554432
CURLAUTH_ONLY	2147483648
CURLOPT_RESOLVE	10203
CURLOPT_TLSAUTH_PASSWORD	10205
CURLOPT_TLSAUTH_TYPE	10206
CURLOPT_TLSAUTH_USERNAME	10204
CURL_TLSAUTH_SRP	1
CURLOPT_ACCEPT_ENCODING	10102
CURLOPT_TRANSFER_ENCODING	207
CURLGSSAPI_DELEGATION_FLAG	2
CURLGSSAPI_DELEGATION_POLICY_FLAG	1
CURLOPT_GSSAPI_DELEGATION	210
CURLOPT_ACCEPTTIMEOUT_MS	212
CURLOPT_DNS_SERVERS	10211
CURLOPT_MAIL_AUTH	10217
CURLOPT_SSL_OPTIONS	216
CURLOPT_TCP_KEEPALIVE	213
CURLOPT_TCP_KEEPIDLE	214
CURLOPT_TCP_KEEPINTVL	215
CURLSSLOPT_ALLOW_BEAST	1
CURL_SSLVERSION_TLSv1_0	4
CURL_SSLVERSION_TLSv1_1	5
CURL_SSLVERSION_TLSv1_2	6
CURLOPT_SAFE_UPLOAD	-1
IMG_GIF	1
IMG_JPG	2
IMG_JPEG	2
IMG_PNG	4
IMG_WBMP	8
IMG_XPM	16
IMG_WEBP	32
IMG_COLOR_TILED	-5
IMG_COLOR_STYLED	-2
IMG_COLOR_BRUSHED	-3
IMG_COLOR_STYLEDBRUSHED	-4
IMG_COLOR_TRANSPARENT	-6
IMG_ARC_ROUNDED	0
IMG_ARC_PIE	0
IMG_ARC_CHORD	1
IMG_ARC_NOFILL	2
IMG_ARC_EDGED	4
IMG_GD2_RAW	1
IMG_GD2_COMPRESSED	2
IMG_FLIP_HORIZONTAL	1
IMG_FLIP_VERTICAL	2
IMG_FLIP_BOTH	3
IMG_EFFECT_REPLACE	0
IMG_EFFECT_ALPHABLEND	1
IMG_EFFECT_NORMAL	2
IMG_EFFECT_OVERLAY	3
IMG_CROP_DEFAULT	0
IMG_CROP_TRANSPARENT	1
IMG_CROP_BLACK	2
IMG_CROP_WHITE	3
IMG_CROP_SIDES	4
IMG_CROP_THRESHOLD	5
IMG_BELL	1
IMG_BESSEL	2
IMG_BILINEAR_FIXED	3
IMG_BICUBIC	4
IMG_BICUBIC_FIXED	5
IMG_BLACKMAN	6
IMG_BOX	7
IMG_BSPLINE	8
IMG_CATMULLROM	9
IMG_GAUSSIAN	10
IMG_GENERALIZED_CUBIC	11
IMG_HERMITE	12
IMG_HAMMING	13
IMG_HANNING	14
IMG_MITCHELL	15
IMG_POWER	17
IMG_QUADRATIC	18
IMG_SINC	19
IMG_NEAREST_NEIGHBOUR	16
IMG_WEIGHTED4	21
IMG_TRIANGLE	20
IMG_AFFINE_TRANSLATE	0
IMG_AFFINE_SCALE	1
IMG_AFFINE_ROTATE	2
IMG_AFFINE_SHEAR_HORIZONTAL	3
IMG_AFFINE_SHEAR_VERTICAL	4
GD_BUNDLED	0
IMG_FILTER_NEGATE	0
IMG_FILTER_GRAYSCALE	1
IMG_FILTER_BRIGHTNESS	2
IMG_FILTER_CONTRAST	3
IMG_FILTER_COLORIZE	4
IMG_FILTER_EDGEDETECT	5
IMG_FILTER_GAUSSIAN_BLUR	7
IMG_FILTER_SELECTIVE_BLUR	8
IMG_FILTER_EMBOSS	6
IMG_FILTER_MEAN_REMOVAL	9
IMG_FILTER_SMOOTH	10
IMG_FILTER_PIXELATE	11
GD_VERSION	2.1.1-dev
GD_MAJOR_VERSION	2
GD_MINOR_VERSION	1
GD_RELEASE_VERSION	0
GD_EXTRA_VERSION	dev
PNG_NO_FILTER	0
PNG_FILTER_NONE	8
PNG_FILTER_SUB	16
PNG_FILTER_UP	32
PNG_FILTER_AVG	64
PNG_FILTER_PAETH	128
PNG_ALL_FILTERS	248
JSON_HEX_TAG	1
JSON_HEX_AMP	2
JSON_HEX_APOS	4
JSON_HEX_QUOT	8
JSON_FORCE_OBJECT	16
JSON_NUMERIC_CHECK	32
JSON_UNESCAPED_SLASHES	64
JSON_PRETTY_PRINT	128
JSON_UNESCAPED_UNICODE	256
JSON_PARTIAL_OUTPUT_ON_ERROR	512
JSON_ERROR_STATE_MISMATCH	2
JSON_ERROR_CTRL_CHAR	3
JSON_ERROR_UTF8	5
JSON_ERROR_RECURSION	6
JSON_ERROR_INF_OR_NAN	7
JSON_ERROR_UNSUPPORTED_TYPE	8
JSON_ERROR_NONE	0
JSON_ERROR_DEPTH	1
JSON_ERROR_SYNTAX	4
JSON_OBJECT_AS_ARRAY	1
JSON_PARSER_NOTSTRICT	4
JSON_BIGINT_AS_STRING	2
JSON_C_BUNDLED	0
JSON_C_VERSION	0.11.99
MCRYPT_ENCRYPT	0
MCRYPT_DECRYPT	1
MCRYPT_DEV_RANDOM	0
MCRYPT_DEV_URANDOM	1
MCRYPT_RAND	2
MCRYPT_3DES	tripledes
MCRYPT_ARCFOUR_IV	arcfour-iv
MCRYPT_ARCFOUR	arcfour
MCRYPT_BLOWFISH	blowfish
MCRYPT_BLOWFISH_COMPAT	blowfish-compat
MCRYPT_CAST_128	cast-128
MCRYPT_CAST_256	cast-256
MCRYPT_CRYPT	crypt
MCRYPT_DES	des
MCRYPT_ENIGNA	crypt
MCRYPT_GOST	gost
MCRYPT_LOKI97	loki97
MCRYPT_PANAMA	panama
MCRYPT_RC2	rc2
MCRYPT_RIJNDAEL_128	rijndael-128
MCRYPT_RIJNDAEL_192	rijndael-192
MCRYPT_RIJNDAEL_256	rijndael-256
MCRYPT_SAFER64	safer-sk64
MCRYPT_SAFER128	safer-sk128
MCRYPT_SAFERPLUS	saferplus
MCRYPT_SERPENT	serpent
MCRYPT_THREEWAY	threeway
MCRYPT_TRIPLEDES	tripledes
MCRYPT_TWOFISH	twofish
MCRYPT_WAKE	wake
MCRYPT_XTEA	xtea
MCRYPT_IDEA	idea
MCRYPT_MARS	mars
MCRYPT_RC6	rc6
MCRYPT_SKIPJACK	skipjack
MCRYPT_MODE_CBC	cbc
MCRYPT_MODE_CFB	cfb
MCRYPT_MODE_ECB	ecb
MCRYPT_MODE_NOFB	nofb
MCRYPT_MODE_OFB	ofb
MCRYPT_MODE_STREAM	stream
MYSQL_ASSOC	1
MYSQL_NUM	2
MYSQL_BOTH	3
MYSQL_CLIENT_COMPRESS	32
MYSQL_CLIENT_SSL	2048
MYSQL_CLIENT_INTERACTIVE	1024
MYSQL_CLIENT_IGNORE_SPACE	256
MYSQLI_READ_DEFAULT_GROUP	5
MYSQLI_READ_DEFAULT_FILE	4
MYSQLI_OPT_CONNECT_TIMEOUT	0
MYSQLI_OPT_LOCAL_INFILE	8
MYSQLI_INIT_COMMAND	3
MYSQLI_OPT_SSL_VERIFY_SERVER_CERT	21
MYSQLI_CLIENT_SSL	2048
MYSQLI_CLIENT_COMPRESS	32
MYSQLI_CLIENT_INTERACTIVE	1024
MYSQLI_CLIENT_IGNORE_SPACE	256
MYSQLI_CLIENT_NO_SCHEMA	16
MYSQLI_CLIENT_FOUND_ROWS	2
MYSQLI_CLIENT_SSL_VERIFY_SERVER_CERT	1073741824
MYSQLI_STORE_RESULT	0
MYSQLI_USE_RESULT	1
MYSQLI_ASSOC	1
MYSQLI_NUM	2
MYSQLI_BOTH	3
MYSQLI_STMT_ATTR_UPDATE_MAX_LENGTH	0
MYSQLI_STMT_ATTR_CURSOR_TYPE	1
MYSQLI_CURSOR_TYPE_NO_CURSOR	0
MYSQLI_CURSOR_TYPE_READ_ONLY	1
MYSQLI_CURSOR_TYPE_FOR_UPDATE	2
MYSQLI_CURSOR_TYPE_SCROLLABLE	4
MYSQLI_STMT_ATTR_PREFETCH_ROWS	2
MYSQLI_NOT_NULL_FLAG	1
MYSQLI_PRI_KEY_FLAG	2
MYSQLI_UNIQUE_KEY_FLAG	4
MYSQLI_MULTIPLE_KEY_FLAG	8
MYSQLI_BLOB_FLAG	16
MYSQLI_UNSIGNED_FLAG	32
MYSQLI_ZEROFILL_FLAG	64
MYSQLI_AUTO_INCREMENT_FLAG	512
MYSQLI_TIMESTAMP_FLAG	1024
MYSQLI_SET_FLAG	2048
MYSQLI_NUM_FLAG	32768
MYSQLI_PART_KEY_FLAG	16384
MYSQLI_GROUP_FLAG	32768
MYSQLI_ENUM_FLAG	256
MYSQLI_BINARY_FLAG	128
MYSQLI_NO_DEFAULT_VALUE_FLAG	4096
MYSQLI_TYPE_DECIMAL	0
MYSQLI_TYPE_TINY	1
MYSQLI_TYPE_SHORT	2
MYSQLI_TYPE_LONG	3
MYSQLI_TYPE_FLOAT	4
MYSQLI_TYPE_DOUBLE	5
MYSQLI_TYPE_NULL	6
MYSQLI_TYPE_TIMESTAMP	7
MYSQLI_TYPE_LONGLONG	8
MYSQLI_TYPE_INT24	9
MYSQLI_TYPE_DATE	10
MYSQLI_TYPE_TIME	11
MYSQLI_TYPE_DATETIME	12
MYSQLI_TYPE_YEAR	13
MYSQLI_TYPE_NEWDATE	14
MYSQLI_TYPE_ENUM	247
MYSQLI_TYPE_SET	248
MYSQLI_TYPE_TINY_BLOB	249
MYSQLI_TYPE_MEDIUM_BLOB	250
MYSQLI_TYPE_LONG_BLOB	251
MYSQLI_TYPE_BLOB	252
MYSQLI_TYPE_VAR_STRING	253
MYSQLI_TYPE_STRING	254
MYSQLI_TYPE_CHAR	1
MYSQLI_TYPE_INTERVAL	247
MYSQLI_TYPE_GEOMETRY	255
MYSQLI_TYPE_NEWDECIMAL	246
MYSQLI_TYPE_BIT	16
MYSQLI_SET_CHARSET_NAME	7
MYSQLI_SET_CHARSET_DIR	6
MYSQLI_NO_DATA	100
MYSQLI_DATA_TRUNCATED	101
MYSQLI_REPORT_INDEX	4
MYSQLI_REPORT_ERROR	1
MYSQLI_REPORT_STRICT	2
MYSQLI_REPORT_ALL	255
MYSQLI_REPORT_OFF	0
MYSQLI_DEBUG_TRACE_ENABLED	0
MYSQLI_SERVER_QUERY_NO_GOOD_INDEX_USED	16
MYSQLI_SERVER_QUERY_NO_INDEX_USED	32
MYSQLI_SERVER_QUERY_WAS_SLOW	2048
MYSQLI_SERVER_PS_OUT_PARAMS	4096
MYSQLI_REFRESH_GRANT	1
MYSQLI_REFRESH_LOG	2
MYSQLI_REFRESH_TABLES	4
MYSQLI_REFRESH_HOSTS	8
MYSQLI_REFRESH_STATUS	16
MYSQLI_REFRESH_THREADS	32
MYSQLI_REFRESH_SLAVE	64
MYSQLI_REFRESH_MASTER	128
MYSQLI_TRANS_START_WITH_CONSISTENT_SNAPSHOT	1
MYSQLI_TRANS_START_READ_WRITE	2
MYSQLI_TRANS_START_READ_ONLY	4
MYSQLI_TRANS_COR_AND_CHAIN	1
MYSQLI_TRANS_COR_AND_NO_CHAIN	2
MYSQLI_TRANS_COR_RELEASE	4
MYSQLI_TRANS_COR_NO_RELEASE	8
READLINE_LIB	libedit
SID	CAKEPHP=hou8jjnjpslatq7dcilhc3kmn4

CakePHP Constants

Constant	Value
APP	/home/fomsite/repositories/fom1.0/app/
APP_DIR	app
APPLIBS	/home/fomsite/repositories/fom1.0/app/Lib/
CACHE	/home/fomsite/repositories/fom1.0/app/tmp/cache/
CAKE	/home/fomsite/repositories/fom1.0/lib/Cake/
CAKE_CORE_INCLUDE_PATH	/home/fomsite/repositories/fom1.0/lib
CORE_PATH	/home/fomsite/repositories/fom1.0/lib/
CAKE_VERSION	2.5.9
CSS	/home/fomsite/repositories/fom1.0/app/webroot/css/
CSS_URL	css/
DS	/
FULL_BASE_URL	http://ownage.fom.be
IMAGES	/home/fomsite/repositories/fom1.0/app/webroot/img/
IMAGES_URL	img/
JS	/home/fomsite/repositories/fom1.0/app/webroot/js/
JS_URL	js/
LOGS	/home/fomsite/repositories/fom1.0/app/tmp/logs/
ROOT	/home/fomsite/repositories/fom1.0
TESTS	/home/fomsite/repositories/fom1.0/app/Test/
TMP	/home/fomsite/repositories/fom1.0/app/tmp/
VENDORS	/home/fomsite/repositories/fom1.0/vendors/
WEBROOT_DIR	webroot
WWW_ROOT	/home/fomsite/repositories/fom1.0/app/webroot/

PHP Environment

Environment Variable	Value
Php Version	5.6.40-0+deb8u12
Redirect Script Url	/teams/view/10265
Redirect Script Uri	http://ownage.fom.be/teams/view/10265
Redirect Status	200
Script Url	/teams/view/10265
Script Uri	http://ownage.fom.be/teams/view/10265
Http Host	ownage.fom.be
Http X Real Ip	216.73.216.228
Http X Forwarded For	216.73.216.228
Http X Forwarded Proto	https
Http Connection	close
Http Accept	/
Http User Agent	Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Http Accept Encoding	gzip, br, zstd, deflate
Path	/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Server Signature
Server Software	Apache
Server Name	ownage.fom.be
Server Addr	192.168.111.30
Server Port	80
Remote Addr	192.168.111.11
Document Root	/home/fomsite/repositories/fom1.0/app/webroot
Request Scheme	http
Context Prefix
Context Document Root	/home/fomsite/repositories/fom1.0/app/webroot
Server Admin	dikkefoaf@fom.be
Script Filename	/home/fomsite/repositories/fom1.0/app/webroot/index.php
Remote Port	49864
Redirect Url	/teams/view/10265
Gateway Interface	CGI/1.1
Server Protocol	HTTP/1.0
Request Method	GET
Query String
Request Uri	/teams/view/10265
Script Name	/index.php
Php Self	/index.php
Request Time Float	1754398545.823
Request Time	1754398545

====

Include
+
Included Files

Include Paths
- 1/usr/share/php
- 2/usr/share/pear
- 3-> /home/fomsite/repositories/fom1.0/lib/Cake/
Included Files
- core(array)
  Behavior(array)
  0CORE/Model/Behavior/TreeBehavior.php
  1CORE/Model/Behavior/ContainableBehavior.php
  2CORE/Model/Behavior/AclBehavior.php
  Cache(array)
  0CORE/Cache/Engine/FileEngine.php
  1CORE/Cache/CacheEngine.php
  Component(array)
  0CORE/Controller/Component/SessionComponent.php
  1CORE/Controller/Component/AclComponent.php
  2CORE/Controller/Component/Acl/DbAcl.php
  3CORE/Controller/Component/Acl/AclInterface.php
  4CORE/Controller/Component/CookieComponent.php
  5CORE/Controller/Component/AuthComponent.php
  6CORE/Controller/Component/EmailComponent.php
  7CORE/Controller/Component/RequestHandlerComponent.php
  Config(array)
  0CORE/Config/routes.php
  1CORE/Config/config.php
  Configure(array)
  0CORE/Configure/PhpReader.php
  1CORE/Configure/ConfigReaderInterface.php
  Controller(array)
  0CORE/Controller/Component.php
  1CORE/Controller/ComponentCollection.php
  2CORE/Controller/Controller.php
  Datasource(array)
  0CORE/Model/Datasource/CakeSession.php
  1CORE/Model/Datasource/Database/Mysql.php
  2CORE/Model/Datasource/DboSource.php
  3CORE/Model/Datasource/DataSource.php
  Error(array)
  0CORE/Error/exceptions.php
  1CORE/Error/ErrorHandler.php
  I18n(array)
  0CORE/I18n/I18n.php
  1CORE/I18n/L10n.php
  Log(array)
  0CORE/Log/CakeLog.php
  1CORE/Log/LogEngineCollection.php
  2CORE/Log/Engine/FileLog.php
  3CORE/Log/Engine/BaseLog.php
  4CORE/Log/CakeLogInterface.php
  Model(array)
  0CORE/Model/Permission.php
  1CORE/Model/Model.php
  2CORE/Model/BehaviorCollection.php
  3CORE/Model/Aro.php
  4CORE/Model/AclNode.php
  5CORE/Model/Aco.php
  6CORE/Model/ModelBehavior.php
  7CORE/Model/ConnectionManager.php
  Network(array)
  0CORE/Network/CakeRequest.php
  1CORE/Network/CakeResponse.php
  Other(array)
  0CORE/bootstrap.php
  1CORE/basics.php
  2CORE/Core/App.php
  3CORE/Core/Configure.php
  4CORE/Core/CakePlugin.php
  5CORE/Event/CakeEventListener.php
  6CORE/Event/CakeEvent.php
  7CORE/Event/CakeEventManager.php
  8CORE/Core/Object.php
  Routing(array)
  0CORE/Routing/Dispatcher.php
  1CORE/Routing/Filter/AssetDispatcher.php
  2CORE/Routing/DispatcherFilter.php
  3CORE/Routing/Filter/CacheDispatcher.php
  4CORE/Routing/Router.php
  5CORE/Routing/Route/CakeRoute.php
  6CORE/Routing/Route/RedirectRoute.php
  7CORE/Routing/Route/PluginShortRoute.php
  Utility(array)
  0CORE/Utility/Hash.php
  1CORE/Utility/Inflector.php
  2CORE/Utility/ObjectCollection.php
  3CORE/Utility/Debugger.php
  4CORE/Utility/String.php
  5CORE/Utility/ClassRegistry.php
  6CORE/Utility/Sanitize.php
  View(array)
  0CORE/View/HelperCollection.php
- app(array)
  Behavior(array)
  0APP/Model/Behavior/SluggableBehavior.php
  Cache(array)
  0APP/Lib/Cache/Cache.php
  Component(array)
  0APP/Controller/Component/PaymentReceivedComponent.php
  1APP/Controller/Component/TicketCreateComponent.php
  2APP/Controller/Component/AutoLoginComponent.php
  Config(array)
  0APP/Config/core.php
  1APP/Config/bootstrap.php
  2APP/Config/routes.php
  3APP/Config/database.php
  Controller(array)
  0APP/Controller/TeamsController.php
  1APP/Controller/AppController.php
  Model(array)
  0APP/Model/AppModel.php
  1APP/Model/MenuItem.php
  2APP/Model/MenuSubItem.php
  3APP/Model/MenuLink.php
  4APP/Model/Content.php
  5APP/Model/Newspost.php
  6APP/Model/Config.php
  7APP/Model/Event.php
  8APP/Model/Order.php
  9APP/Model/Orderstate.php
  10APP/Model/User.php
  11APP/Model/PaymentProvider.php
  12APP/Model/Orderline.php
  13APP/Model/Payment.php
  14APP/Model/OrderLog.php
  15APP/Model/Team.php
  16APP/Model/Compo.php
  17APP/Model/Poule.php
  18APP/Model/Ticket.php
  19APP/Model/TicketState.php
  20APP/Model/Product.php
  21APP/Model/TicketType.php
  22APP/Model/Seat.php
  23APP/Model/Seatmap.php
  24APP/Model/War.php
  25APP/Model/Tag.php
  Other(array)
  0APP/webroot/index.php
  Routing(array)
  0APP/Routing/Filter/CacheLanguageDispatcher.php
- plugins(array)
  Acl(array)
  Config(array)
  0Acl/Config/bootstrap.php
  DebugKit(array)
  Component(array)
  0DebugKit/Controller/Component/ToolbarComponent.php
  Plugin(array)
  0DebugKit/Lib/DebugMemory.php
  1DebugKit/Lib/Panel/HistoryPanel.php
  2DebugKit/Lib/DebugPanel.php
  3DebugKit/Lib/Panel/SessionPanel.php
  4DebugKit/Lib/Panel/RequestPanel.php
  5DebugKit/Lib/Panel/SqlLogPanel.php
  6DebugKit/Lib/Panel/TimerPanel.php
  7DebugKit/Lib/Panel/LogPanel.php
  8DebugKit/Lib/Log/Engine/DebugKitLog.php
  9DebugKit/Lib/Panel/VariablesPanel.php
  10DebugKit/Lib/Panel/EnvironmentPanel.php
  11DebugKit/Lib/Panel/IncludePanel.php
  12DebugKit/Lib/DebugTimer.php
  Recaptcha(array)
  Config(array)
  0Recaptcha/Config/key.php
====

Poederbaas

Kyo

DeurneWest

Rupel

KM.

yookes

Request History

Session

Request

Cake Params

Post data

Query string

Cookie

Current Route

Sql Logs

default

Total Time: 37 ms Total Queries: 36 queries

Query Explain:

Memory

Timers

Logs

View Variables

App Constants

CakePHP Constants

PHP Environment

Included Files

Include Paths

Included Files

Total Time: 37 ms
Total Queries: 36 queries