Lex_

What are you not understanding about what I'm saying? You were temporarily muted and continued to cause problems whenever the time was up. I had absolutely nothing to do with inviting you to the GB channel. We were having a discussion about the Silo appeal.

I can guarantee that I was not involved with inviting you into the GB TS. I don't even remember that happening. I was on that night helping with staff on Silo's ban appeal as well as doing my own doc work for SSO. You were both chat muted and voice muted that day within reason. And the people who muted you weren't even in the channel with me, the only involvement Kendal had with your ban was issuing it. I haven't spoken to you much - never really did when you returned after the ban wipe. There was some banter but it wasn't a serious full-blown argument or conversation, and it wasn't even done close to you being rebanned either. I brought up the past for the sake of explaining the fact that I wasn't even there and could care less about it. You should stay banned for how you responded to the ban by repeatedly alting and for starting trouble multiple times after the ban wipe - including the instance of you essentially harassing me.

You said it yourself, you were on to defend Silo over his ban appeal. What conversation do you think I was having with Kendal? I never said anything to you, nor did I ever suggest you to join the Teamspeak. I may have been in the same channel as you at some point (but not at that time) but the intention wasn't to start any trouble, merely to listen to what people wanted to discuss with you because they invited you in. You joined, said something in OOC, an argument broke out and so you got muted. After a bit you got unmuted. You found me in-game (noting that I wasn't looking for you and was busy in a conversation) and proceeded to swallow your mic repeatedly saying "SHIT FACTION LEADER". You got voice muted, after a bit un-voice muted, then started to do it again swapping back and forth from "SHIT FACTION LEADER" to "WHAT YOU GONNA DO?". Having joined previously causing problems, staff felt that banning you for Toxicity, following what Garnet had stated was the response to repeat offenders who were unbanned during the ban wipe (a permanent ban, on thin ice), was warranted. I'm unsure of what your problem is with me considering I've legitimately done nothing. I wasn't even there when you had gotten banned as at that point Cramer was leading GB - and when I intitially heard about it happening I was on your side.

Can confirm that Topshot was in fact muted multiple times in different instances for starting trouble in OOC (and over voice). The few times that he did hop in-game, I had the problem that he'd come up to me and constantly barrade me with comments about how I "killed GB" and was a "shit faction leader" to a point of being borderline harrassment - similar to starting trouble with Jackal "jokingly" in OOC and on Teamspeak. I understand its a video game and I have the ability to mute topshot locally, as well as if it is that bad I could just disconnect, but the whole point of issuing mutes (both chat and voice) and even at most a Toxicity ban (which follows with what Garnet stated will happen to repeat offenders after the ban wipe) is to not interrupt other people who are actively trying to play the server and follow its rules. Mans literally followed me in-game anywhere I went when I was trying to have a serious, productive conversation with Kendal and a few other staff and community members in TS (my game is not set to mute when I tab out) Topshot, if I recall, was meant to be on the "do not unban" list that Garnet referred to when he did the most recent ban wipe - atleast that was what was stated by a few notable people. Not to mention that prior to the ban wipe, Topshot evaded his cheating ban with more than a few alts knowingly trying to hide his identity. -1.

@AwesomeAidan @eXg-Buddha @JimTrash Please lock this thread until staff can come to a conclusion. None of the replies, including from Acer himself, are helpful to your final decision. The evidence supplied is from before the tickrate was changed. It is entirely possible to fire off more than one AEK bullet in a single second. (600 RPM / 60 seconds = 10 bullets per second - potentially fluctuated by the tickrate even further up or down) Simply put, -1. The evidence provided isn't sufficient enough. We lack vital information like the position of Acer and the position of Foxx.

That knowledge helps Acer even more. If he wasn't tap firing, the bullets have a pretty wide spread after the first few shots - especially at a distance (less likely to be the case); if he was tap firing, then it's even more possible depending on where Foxx is standing. We can assume where Acer is, but we still don't see where Foxx is. This clip alone isn't enough evidence.

The current video by itself is just not enough for me. Don't know what weapon Acer was using nor where Foxx was at in relation to Regret. You can't tell either one of those from the video. If there are any other clips (although I'd assume you'd post them already if that's the case), hoping you update the thread soon.

Description: Add console commands to support quickly saving and loading presets for your weapons as an alternative to automatically saving and loading attachments in CW 2.0. This addition is all clientside and doesn't affect any of the serverside code. Essentially you could create a bind that runs "cw_preset_save default" and "cw_preset_load default" to quickly save (if you edit your preset) and load on any CW weapon. Reasoning: This isn't too big of a change, but it isn't too important either. With the lowered tickrate, it's a bit harder to navigate the CW customization menu (unless you're using presets, in which its easier) Additional Information: Here's the Lua - place this at the end of cw_preset.lua, located in cw2/lua/cw/shared/ if CLIENT then concommand.Add("cw_preset_load", function(ply, cmd, args) if not args[1] or args[1] == "" then return end if not LocalPlayer():GetActiveWeapon().CW20Weapon then return end CustomizableWeaponry.preset.load(LocalPlayer():GetActiveWeapon(), args[1]) end, nil, "Load a preset. Must have a valid CW 2 weapon equipped.", FCVAR_SERVER_CANNOT_QUERY) concommand.Add("cw_preset_save", function(ply, cmd, args) if not args[1] or args[1] == "" then return end if not LocalPlayer():GetActiveWeapon().CW20Weapon then return end CustomizableWeaponry.preset.save(LocalPlayer():GetActiveWeapon(), args[1]) end, nil, "Save a preset. Must have a valid CW 2 weapon equipped.", FCVAR_SERVER_CANNOT_QUERY) end

Don't think you understand what crouch jumping looks like. -1. Pretty clearly crouch jumped more than once. Whether or not you were being fired at for the initial and last crouch jumps, you were jumping into an area where you should expect to engage in combat.

You'd be surprised the amount of people I caught in just one war. The only issue is that there are (or were) varying definitions on crouch jump and what specifically isn't allowed with it. Staff and players seemed alright when I was watching. And there are quite a few places on objectives where you can view from underneath, especially on the way to objectives.

-1. You bring up a good reason for creating this suggestion but lack a proper solution. You're essentially saying: "we don't like how vehicles work, change them" without explaining what you want changed and how you/the community wants it to change. Reminder that the limitations with vehicles are based on both server and client performance - vehicles can cause major drops in your FPS depending on how many are able to be rendered, so limiting how many vehicles are on the map at a single time and moving is a must. I don't know what the vehicles were like all the way back then. 10 minutes would work for the respawn time. There isn't a way to fix the hitboxes with vehicles as far as I can tell since it likely just checks if the vehicle took damage and applies it to the driver. But I do, obviously, agree that vehicles need a rework.

All of the rules that I had included (such as the "no raiding debriefs or spawn rooms" and "requiring a briefing prior to raid") are important to new players. If a PVT masses during a raid because they don't know they can't kill people inside of a briefing building or spawn room, it is on them and not the officer for not explaining the rules. The current language on claims does not say that you need to specify if your claim is KOS. This is the only change. I did not include the "initial claim, 10 second warning" for the "staff enforcement" reason. There are many cases where specifics and further explaining is something that should be done when handling rules and is entirely necesary to keep an up-to-date list of rules in a single thread for all players to read.

Short description: The following suggestion calls for an edit on the official MilitaryRP rules page, available here. The changes include the removal of no longer enforced and useless rules, edits to existing rules on the basis of more specific or more general language, and the inclusion of a few newer rules as decided by the community and the current staff team. Reasoning: Having all of the rules clarified with easy-to-understand, specific but broad language will explain unwritten rules and community habits to new community members, and will keep the rules page short and clean but up-to-date and accurate. Before I get into the full list of rules, I want to address the lack of language involved with claims. Nowhere is it stated that to enforce a KOS on your claim, it needs to be addressed in your advert that your claim is "KOS to [insert here]". I would like to suggest not making it a requirement (if it actually is one as per Garnet/Gildarts/Kendal) as it should be implied that a claim would be KOS to those who aren't wanted or shouldn't be on the claim. ** is a category, * is a sub-category, and % is bold text %It is your responsibility to read and abide by our server rules as failure to do so may result in a form of punishment% %These rules are up to staff and community interpretation and are subject to change at any time% **GENERAL RULES** - Do not RDM (Random Deathmatch): Shooting or killing players without a proper reason. - Do not break NLR (New Life Rule): You may not return to the location of your death for 5 minutes outside of war, or use information from your previous life. - Do not FailRP: A general term applied to anything that may not be realistic in a roleplayed Military scenario. Some examples include bhopping during war or swapping jobs to avoid being kidnapped. - No vigilantism: If somebody is breaking a rule, report them by using /report or the forums and let staff handle it. Do not take it into your own hands. - No impersonation: Using the name of another player, new or old, to hurt their reputation or act like them. - No spamming: Spamming is the use of any chat (text or voice) to send bulk unwanted messages or for the purpose of interrupting. - Be respectful in all Out Of Character chats - this is not limited to in-game. Includes staff chat, adverts and other platforms. No racist or derogatory terms. - You may not use /job to create your own faction or to set yourself apart from other people (unless it is meant for war, raids, or sims). You may only use and join factions available in the F4 menu. **CHAT RULES** - Advert chat may only be used to deliver important in-character information or server announcements, such as raids, kidnaps, claims, and anything staff related. - Comms chat is an in-character form of communication. Unless otherwise stated, only your teammates can view and use information present in comms. - You may only post links to GarnetGaming forums or a faction's Google documents in chat. Other links are prohibited and may be considered advertising. **RULES OF ENGAGEMENT** - Do not shoot other players unless war is active, participating in a raid, participating in a kidnap, or enforcing a claimed area. You may never fire upon teammates unless it is for combat simulations or enforcing your claim. - You may kill any enemy that has an explosive device in their hand if they are outside of their own base, regardless of the war status. **WAR RULES** - %Pre-cap:% All players must be within their respective base walls (or otherwise defined) 2 minutes before a war begins. Players outside of their base within the 2 minutes until war will be respawned and warned. - %Objective exclusion:% If the player count before a war begins is sub 80 players, the players leading war for each side may communicate to exclude other objectives during the upcoming war. - %Basecamp:% Do not shoot players within or on their base walls during a war. - You may not enter the enemy base during a war. [NEW] - You may not place mines before war unless they are planted on an objective's cap point. This means you may not place mines %before war% on the path to an objective from one side. [NEW] **FACTION RULES** - %Self promotion:% Do not appoint yourself to a rank that you have not earned - If you have been promoted to a General's position, you may appoint officers to a general rank so long as there is availability and sound reasoning. - All junior officer/warrant officer ranks will have a minimum of 5 days (inclusive) between promotions. - All officer ranks will have a minimum of 7 days (inclusive) between promotions. - When a player comes off reserves, they must wait an additional two weeks alongside their promotion cooldown to be promoted to the next rank. - Demoting a player in your faction requires valid reasoning, both in-character and out-of-character being acceptable. Third party platforms and applications are not acceptable reasons for demotion. - An officer can deny the right to tryout to any player for any reason. A player can pass a tryout and not be given access to the faction for any reason - as long as it is followed with logical and sound reasoning. - Faction leaders may not be biased against a player for any reason, ie. race, sex, age, and so on. All members of their faction must be treated equally. **OFFICER RULES** - Officers must have a minimum of 100 hours playtime on the server (/playtime) [NEW] *Raiding* - An O-1 or higher can host a raid on the enemy base. The raid must be adverted before it begins. Attackers have one life, while defenders have unlimited. - To host a raid, you must host a briefing prior to the raid inside of your base. [NEW] - All players within the base (aside from teammates) can be killed. Intentional spawn camp is not allowed. - The cooldown for a raid per nation is 10 minutes. Raids must not exceed 5 minutes in length. - You may not kill players inside of their briefing halls or spawn rooms. [NEW] *Kidnapping* - An O-1 or higher accompanied by two other players may kidnap an enemy player who is alone and outside of the vision of their friendlies. - You may only hold a kidnapped player for 15 minutes unless both parties come to an agreement. - If you are being kidnapped, you may not fire back on those kidnapping you. - Any player can counter your kidnap via advert if they had witnessed you actively kidnapping a player within 15 seconds of their kidnapping. *Raid rescue* - An officer may call a raid rescue via advert to rescue a member of their faction (ie. Green Beret rescuing another Green Beret) who has been kidnapped. - You must know that they are kidnapped through roleplay. - You can only call a raid rescue if they are being held outside of the enemy base. *Claims* - A faction may only have one claim at a time. Claiming another location overwrites the previous claim unless falsed. [NEW] - You may claim an area of the map that is not already claimed. You may not claim your entire base. You may not claim any location in the enemy base. - The location must be identifiable by other players. - Claiming a location for a tryout overrules any existing claim of the same location if the purpose of the existing claim is for something other than tryouts. [NEW] - You may enforce your claim by killing a player after giving them a warning to leave. You must wait 10 seconds after your initial claim before enforcing your KOS. [NEW] - A faction has their claim until they abandon the claim via advert. This means that you will own the claim between wars unless it is claimed by another faction or you abandon it. **MISCELLANEOUS RULES** - Receiving 5 warns within a 30-day period will result in a one week NITRP (No Intent To Roleplay) ban. [NEW] - The altering of any GarnetGaming-related document without permission is to be considered sabotage. Will result in a one week ban. - Loopholing any of the rules present is prohibited and will be met with a punishment at the discretion of the responding staff. [NEW] - Do not misuse the report system. The /report command is there to effectively and quickly communicate with staff in the event that a player has broken a rule. Here is the final thing formatted. It is your responsibility to read and abide by our server rules as failure to do so may result in a form of punishment These rules are up to staff and community interpretation and are subject to change at any time GENERAL RULES - Do not RDM (Random Deathmatch): Shooting or killing players without a proper reason. - Do not break NLR (New Life Rule): You may not return to the location of your death for 5 minutes outside of war, or use information from your previous life. - Do not FailRP: A general term applied to anything that may not be realistic in a roleplayed Military scenario. Some examples include bhopping during war or swapping jobs to avoid being kidnapped. - No vigilantism: If somebody is breaking a rule, report them by using /report or the forums and let staff handle it. Do not take it into your own hands. - No impersonation: Using the name of another player, new or old, to hurt their reputation or act like them. - No spamming: Spamming is the use of any chat (text or voice) to send bulk unwanted messages or for the purpose of interrupting. - Be respectful in all Out Of Character chats - this is not limited to in-game. Includes staff chat, adverts and other platforms. No racist or derogatory terms. - You may not use /job to create your own faction or to set yourself apart from other people (unless it is meant for war, raids, or sims). You may only use and join factions available in the F4 menu. CHAT RULES - Advert chat may only be used to deliver important in-character information or server announcements, such as raids, kidnaps, claims, and anything staff related. - Comms chat is an in-character form of communication. Unless otherwise stated, only your teammates can view and use information present in comms. - You may only post links to GarnetGaming forums or a faction's Google documents in chat. Other links are prohibited and may be considered advertising. RULES OF ENGAGEMENT - Do not shoot other players unless war is active, participating in a raid, participating in a kidnap, or enforcing a claimed area. You may never fire upon teammates unless it is for combat simulations or enforcing your claim. - You may kill any enemy that has an explosive device in their hand if they are outside of their own base, regardless of the war status. WAR RULES - Pre-cap: All players must be within their respective base walls (or otherwise defined) 2 minutes before a war begins. Players outside of their base within the 2 minutes until war will be respawned and warned. - Objective exclusion: If the player count before a war begins is sub 80 players, the players leading war for each side may communicate to exclude other objectives during the upcoming war. - Basecamp: Do not shoot players within or on their base walls during a war. - You may not enter the enemy base during a war. - You may not place mines before war unless they are planted on an objective's cap point. This means you may not place mines %before war% on the path to an objective from one side. FACTION RULES - Self promotion: Do not appoint yourself to a rank that you have not earned - If you have been promoted to a General's position, you may appoint officers to a general rank so long as there is availability and sound reasoning. - All junior officer/warrant officer ranks will have a minimum of 5 days (inclusive) between promotions. - All officer ranks will have a minimum of 7 days (inclusive) between promotions. - When a player comes off reserves, they must wait an additional two weeks alongside their promotion cooldown to be promoted to the next rank. - Demoting a player in your faction requires valid reasoning, both in-character and out-of-character being acceptable. Third party platforms and applications are not acceptable reasons for demotion. - An officer can deny the right to tryout to any player for any reason. A player can pass a tryout and not be given access to the faction for any reason - as long as it is followed with logical and sound reasoning. - Faction leaders may not be biased against a player for any reason, ie. race, sex, age, and so on. All members of their faction must be treated equally. OFFICER RULES - Officers must have a minimum of 100 hours playtime on the server (/playtime) Raiding - An O-1 or higher can host a raid on the enemy base. The raid must be adverted before it begins. Attackers have one life, while defenders have unlimited. - To host a raid, you must host a briefing prior to the raid inside of your base. - All players within the base (aside from teammates) can be killed. Intentional spawn camp is not allowed. - The cooldown for a raid per nation is 10 minutes. Raids must not exceed 5 minutes in length. - You may not kill players inside of their briefing halls or spawn rooms. Kidnapping - An O-1 or higher accompanied by two other players may kidnap an enemy player who is alone and outside of the vision of their friendlies. - You may only hold a kidnapped player for 15 minutes unless both parties come to an agreement. - If you are being kidnapped, you may not fire back on those kidnapping you. - Any player can counter your kidnap via advert if they had witnessed you actively kidnapping a player within 15 seconds of their kidnapping. Raid rescue - An officer may call a raid rescue via advert to rescue a member of their faction (ie. Green Beret rescuing another Green Beret) who has been kidnapped. - You must know that they are kidnapped through roleplay. - You can only call a raid rescue if they are being held outside of the enemy base. Claims - A faction may only have one claim at a time. Claiming another location overwrites the previous claim unless falsed. - You may claim an area of the map that is not already claimed. You may not claim your entire base. You may not claim any location in the enemy base. - The location must be identifiable by other players. - Claiming a location for a tryout overrules any existing claim of the same location if the purpose of the existing claim is for something other than tryouts. - You may enforce your claim by killing a player after giving them a warning to leave. You must wait 10 seconds after your initial claim before enforcing your KOS. - A faction has their claim until they abandon the claim via advert. This means that you will own the claim between wars unless it is claimed by another faction or you abandon it. MISCELLANEOUS RULES - Receiving 5 warns within a 30-day period will result in a one week NITRP (No Intent To Roleplay) ban. [NEW] - The altering of any GarnetGaming-related document without permission is to be considered sabotage. Will result in a one week ban. - Loopholing any of the rules present is prohibited and will be met with a punishment at the discretion of the responding staff. [NEW] - Do not misuse the report system. The /report command is there to effectively and quickly communicate with staff in the event that a player has broken a rule.

I believe its the same vehicle selection we had on Delta. I can take a look here in a minute to see what options we get for RU and US to be sure, though. Thanks for the update Garnet. Although it was mostly just tedious optimizations and fixes, watching you map over this weekend was a nice experience. Rarely get to see somebody mapping in action and all. Here are the vehicle choices: RU has a car and a truck while US gets the Humvee https://imgur.com/a/oiIX7Tf

I agree with Koulit here that what you've mentioned at the end there is not the cause of less Russian recruits. People will inherently join the country they know more about, especially if that is the place they currently reside. The bigger problem isn't that the US is getting new people, it's that RU aren't active all of the time and often times don't return on a consistent basis (it's a videogame) I'd be down to participate in this meeting but there isn't much more we could do. There just isn't an imbalance on the rosters to justify spawning as Russian recruit and it comes down to getting people to return day to day.

+1. Conway hasn't been here for a lot of my time on GG, but I know that he's put tons of work and effort into Army and as a previous staff member. Conway has the experience necessary that would benefit the server. Although, as an honest side note, Conway has some tendencies to push for a result in favor of his opinion, I don't feel that that would get in the way as him as staff on MRP considering he is TeamSpeak Guardian and the only Forum Moderator and is very well capable of being unbiased.

In-game name: SSO COL Alex Endroff Previous names: Torch, Fier, Tower, Overlord Age: 18 SteamID: STEAM_0:0:1138414 Warns: 0 Timezone: EST Playtime: | SSO COL Alex Endroff has played for 1624:26:05. TeamSpeak / Microphone: Yes, to both. Record Garry's Mod videos: Yes-ish. I use ReLive and sometimes it just isn't reliable, and OBS is laggy as hell. Referrals: Kendal/Milton, Koulit, Joe Budden, Conway Past experiences as staff: Canadian's Turf - 2015 to 2019. Highest rank as superadmin. I have since resigned from the position although I still have access to do things. GarnetGaming MilitaryRP - 2018, trialmoderator, and 2019 moderator. How do you plan on benefiting the server? The answer you see here might be similar to the one in my previous application. I have experience in a manager position back when I was actually responsible for Canadian's Turf. Those responsibilities ranged from staff management (we didn't do applications and had unanimous votes to give people moderator) to content on the server. I've used on D3A in my previous two times as a staff member. I have an understanding of the tools that staff actively use in resolving sits, reports, and appeals. I've helped more than a few times in previous appeals and reports (such as more recently the Silo ban appeal) using my experience as a superadmin on CT. I'm an unbiased third-party when it comes to anything staff related and tons of active time on my hands to use putting that into the server in various areas. Previous applications: September 2018 (Accepted) March 2019 (Denied) July 2019 (Accepted) Previous bans: None. How much time do you have for this role: Plenty

Special Operations Force Sily Spetsial'nykh Operatsii What: Mandatory meeting about the current status and upcoming changes to the faction. When: January 31st, 2020. 10pm Eastern Time. Where: SSO TS Channel All active duty SSO members are required to attend this meeting. If you are unable to make it, please let me know via forums DM or on Discord. Reserves are not welcome to attend this meeting without special permission from me prior. [ @Shibe @Apowwo @Jpop @Shrood @Landon @Whiskeyy @spired @WeirdChamp @Ting ]

He starts aiming directly at me through the wall the second he starts walking and ADS'ing. He doesn't fix his aim whenever I'm in clear line of sight - just takes a second before shooting, which I'm going to assume is to swap to semi-auto as if he knew he had enough time to do so. That hesitation isn't him fixing his aim, he didn't even move whatsoever when he stopped. And as Viva said, he has other clips but because it was late he only uploaded that one.

He's legit pre-aiming and "tracing" my head through the wall while walking at the start of the door (I was not there when he had died). Not only that but the risk and confidence of using semi-auto and two shotting me that close range isn't too well. The first shot is understandable, but the second shot not so much. As @Viva said, there are more clips if needed. -1 to the appeal.

As I said, another topic for another day. This suggestion is in regards to how exceedingly powerful the Mosin and Orsis are considering you can use them while on a 300hp class, or use them alongside a med-kit and/or nades (Prestige, Defender, and their equivalents) And what I'm calling for isn't "buffing" the base snipers, it's making them consistent depending on their "tier" as a class - like how MARSOC is the equivalent to GRU in terms of their classes, it's the same way with Rangers and Vega (except Rangers have a medic class while Vega have an LMG). And aside from their differences and inconsistencies in damage, the stats for each of those weapons are still pretty good. The server has an insane sniper meta and people are calling for maps that allow for more CQC, but don't want to change how their weapons work because "they paid $20 for it."

The weapons that you can buy off of the store are extra pieces of equipment that go with your loadout. They are not meant to replace any of the base weapons for classes and this assumption that they better be good is rather toxic. This is the same logic that was applied by people when the AEK was suggested to be nerfed. Even if you didn't change the weapon to something more fitting, the usability of these weapons is going to go down when it comes to their stats. And the problem isn't that the base snipers are under-performing; they're more powerful than any of the ones you can buy on the store but rarely get used because why give up a med-kit or grenades to use a sniper when you can easily just have both (I could go on and on about this, but that's another topic for another day). Balancing is balancing and nothing on the server is final, have some sort of understanding with that instead of seeming so entitled to a weapon or class that you paid money for. +1. I agree with replacing the Orsis with the SR-338 and that there are other things to balance out the Mosin (like replacing the ACOG with Short Dot). With all of that in mind, I think the base snipers for MARSOC, GRU, Rangers, and Vega should have more consistent damage (Vega SV-98 does 100 base iirc while the GRU Mosin does 125 base).

-1. I still don't believe that you are ready to join the staff team as a moderator. You are very immature, often times carrying around some major grudges, and do not work well with others in general. As far as the application goes, you are below the minimum age required to apply [lacking any note of who gave you permission to apply at the time of writing this], and your answer to the essay question is a situation/plan that doesn't require you to be staff (or an officer), as well as goes against what staff should be doing (moderating). Your whole hook for your application is calling for roleplay, which as appealing as it might be, is not your job as a moderator to handle, and it definitely isn't something that I could see you doing since you lack a plan of action in that regard. Sorry if you see that as a brutal response, but you did ask for feedback. Do what you want with what I've shared, but I think you should wait a few months before reapplying (or until you are able to meet the minimum age requirements).

When Delta had released, this was the way that it was meant to be handled. The tunnels counted as in base (when it comes to the opposite nation running in or basecamp) but would still be considered pre-capping before war. I'm not sure why that ever stopped getting enforced or if it had gotten changed, but now it is back to the way that it was originally - the decision being based on how far out each of the tunnels go relative to the objectives and other base.

This is my last reply on this thread because of the forum rules but I wanted to reply what you've just said. The numbers are not unbalanced. This idea that "RU outnumbers US" or "Marines outnumbers Army" is entirely false (and the same goes for US outnumbers RU in all reality). What classifies somebody as an active member? What classifies a "faction" as an "active faction?" The rosters are pretty well-balanced, and that isn't even including people who play but don't want to get promoted, or people who have just joined. Stop promoting the idea that you need some sort of supplement and advantage over one faction, or that your faction is inherently better based around statistics that aren't even being measured properly. All of this thread is just talk - it isn't a set in stone plan by Garnet, nor is it a witchhunt against Marines and its recent past. You can argue your case, but simply saying and calling out "Army is inactive, Marines are better" is not helping you whatsoever and having it come from your leader especially is unprofessional. The screenshot you had shared really doesn't mean anything. We don't see the population of the server in comparison and it is only one portion of an ever-complex set of server stats [considering people play at different times, on different days, not even minding the individuality of each player and their schedule for said day].