![]() |
||||||||||||||||||||||||||
|
RM vs DTR [Recurring combat event] - War of attrition | May 14th, 8PM UTC - Printable Version +- Discovery Gaming Community (https://discoverygc.com/forums) +-- Forum: Discovery General (https://discoverygc.com/forums/forumdisplay.php?fid=3) +--- Forum: Server Events (https://discoverygc.com/forums/forumdisplay.php?fid=411) +---- Forum: Community (https://discoverygc.com/forums/forumdisplay.php?fid=28) +---- Thread: RM vs DTR [Recurring combat event] - War of attrition | May 14th, 8PM UTC (/showthread.php?tid=196530) |
||||||||||||||||||||||||||
RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 2nd, 6PM UTC - LuckyOne - 04-02-2023 Put me up as fighter reserve for RM - Hans.Zweihander RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 2nd, 6PM UTC - Gabriel - 04-02-2023 RNC-Bayern Tirpiz RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 2nd, 6PM UTC - BobMacaroni - 04-02-2023 late but if there are any upcoming needs for any slots for balances whatsoever, I can be reserve RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 2nd, 6PM UTC - Sarwar - 04-02-2023 Allende Corsair BC RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 2nd, 6PM UTC - Fab - 04-03-2023 Nice event that worked out in the end, but the delays and miscommunication is giving me headaches, so, I propose: 1. cut the initially available slots by half. 2. second/extra slots for a ship class will only be available if the prior ('first') slot has already been filled by both sides. For example, a team can only register a second cruiser if both teams have a cruiser. a team can not register two cruisers if the other side has no cruisers, and so on. 3. Players can register to a ship class that has already been taken, but will only have their participation guaranteed if the other side also manages to fill the same extra slot: Player A and B sign up for the dreadnought slot on team 1, while player X signs up for team 2's dreadnought slot. Player A gets the slot for signing up first, player B is put on stand-by until another player signs up for the dreadnought slot for team 2. Player A and X are confirmed, Player B requires a Player Z to register for the slot on team 2 so both B and Z can be confirmed. 4. forum registration ends one hour before the event. after forum registration ends, the teams can start looking for reserves to fill slots without an equivalent pair (not slots that are empty on both sides). they have one hour to do so. team leaders are required to post on the forums their selected reserves with ship name and ship class. Players that are already registered can no longer switch sides or ship class past the registration period. players without a pair at the start of the event (e.g. a player that is flying a bomber, but the other side has no confirmed bombers) will be withdrawn from the event. exception: confirmed ships that do not show up for the event will be regarded as present for this rule. If 'A' and 'B' are both registered bombers for their respective teams after the registration period and 'B' does not shows up, 'A' can participate. If there weren't any confirmed ships on the other side (Empty slot on forums), 'A' can not participate. example 1: Team 1 has a cruiser while Team 2 has none. Team 2 must find a reserve to pair with Team 1's cruiser. Team 2 finds a reserve, both cruisers can now participate. example 2: Team 1 has a battleship, Team 2 has none. Team 2 does not manages to find a battleship reserve in time. Team 1's battleship is withdrawn from the event. example 3: Team 1 has a bomber, Team 2 has a bomber. Team 2's bomber, properly registered and accounted for the event, does not shows up. Team 1's bomber can still participate. RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 2nd, 6PM UTC - Barrier - 04-04-2023 These are solid suggestions. However, I really did consider stuff like this at an earlier point and concluded that this prevents too many people from joining for not much gain. Yes it's quite challenging to organize last-moment ship class changes and people suddenly leaving or joining. But I think this is an unavoidable part of scheduling events, mainly because people's schedules change last-moment and a lot of people don't use the forums. The main thing for me is to achieve three things: maximize the number of people per event, make sure that the event starts close to the agreed-upon time, and that everyone who registered for the event gets to participate. I do admit that based on the logs, the last one started quite a bit later, so I will set a hard rule about that. But otherwise these things are expected and are solvable with some mild headaches on my part and a good bit of help from people like @vladimir26 o7. I think if these ever reach the point of having too many people registering, then we can consider applying more restrictions. RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 2nd, 6PM UTC - Barrier - 04-04-2023
The Kaiserliche Rheinwehr suffers a crushing defeat on DTR's home turf. Sign-ups are now open for the next event, which is happening on Saturday, Apr 8th, at 6PM UTC. RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 8th, 6PM UTC - Peter. - 04-04-2023 Prefer: Bomber - DTR-Carlos_Juan Can switch to fighter, if someone reaches out and really wants the bomber slot. RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 8th, 6PM UTC - Fab - 04-07-2023 I will confirm my participation 2 or so hours before the start of the event because of the holidays. RE: RM vs DTR [Recurring combat event] - War of attrition (Munich) | Apr 8th, 6PM UTC - Venemon - 04-08-2023 Schleife - RM BC |