=MeRk= UK REALITY (Europe)

[NyteMyre]

1 "DO NOT RUSH FLAGS!.": Do not rush flags, especially at the start of a round. Clearing out flags then moving on is fine mid game but prolonged "camping" is not acceptable.

Since i wasn't allowed to ask this on the server....... WHY do you feel it is necessary to make this a rule? If one teams approach to a map is to rush objectives, then they should be allowed too.

Especially with Kashan (where i asked it). You put the infantry as fast as possible on the bunker flags before the armor arrives. Rantbox said we weren't allowed to go there because the flags weren't cappable yet.

[Brainlaag]

Since i wasn't allowed to ask this on the server....... WHY do you feel it is necessary to make this a rule? If one teams approach to a map is to rush objectives, then they should be allowed too.

Especially with Kashan (where i asked it). You put the infantry as fast as possible on the bunker flags before the armor arrives. Rantbox said we weren't allowed to go there because the flags weren't cappable yet.

To prevent weaker teams from getting steamrolled.

[=MeRk= BluFFeR]

Since i wasn't allowed to ask this on the server....... WHY do you feel it is necessary to make this a rule? If one teams approach to a map is to rush objectives, then they should be allowed too.

Especially with Kashan (where i asked it). You put the infantry as fast as possible on the bunker flags before the armor arrives. Rantbox said we weren't allowed to go there because the flags weren't cappable yet.

As Brainlaag said it prevents the weaker team from getting steamrolled, also it creates a front line between both forces to promote a better battle.
If we didnt have this rule it would completly open the server up to the "I want to get as many kills as possible and f**k everyone else while im doing" people.
It just ruins the rounds for everyone involved when people go looking for cheap kills at the start of the game.
Then more than likely the weaker team starts to rage quit from then on.

[Jevski]

Im a bit confused about this rule too. Yesterday on Dovre, 2nd to last flag was capped by germans. Flag was neutral, one german on their last flag was warned for rushing.
Later in game a russian was at a flag that was 2 flags behind rotation, and he was not warned.

Is it only allowed to be at a flag when its capable?

I understand that going ahead to the enemies 2nd or 3rd flag is a nono, and often leads to an unfair game, but moving ahead to the next flag that is about to be capable should be ok?

[Pronck]

I thought that after 15 minutes you could go anywhere except for the enemy mainbase...

[MasterX]

Different servers handle different rules. Respect them!

[Loller]

To clarify our rushing rule once and for all, its been under discussion amongst us as we do feel the public are unclear as to what we MeRk constitute rushing.

At the beginning of the round you may only "rush" to the middle flag of the map. It is not allowed to rush further than this. For example on Muttrah , US and MEC can go to the middle flag which is WCC but no further until the AAS order states that they can attack ECC or North City. The intent is to allow time for the teams to create front lines and for one team not to snowball a round too heavily at the beginning.

Once the beginning of the game is over and the midgame commences typically after 10-15 minutes of play teams must follow the AAS order, defending and attacking the marked flags , they can operate in areas around the map not in cap range for ambushes. Importantly though, we do allow flags to be "cleared" this means removing a Firebase or strategic asset if it is in the flag zone , however prolonged presence in that area will constitute not following the AAS order and incur warnings.

[NyteMyre]

Rushing flags is not automatically an advantage.
Your definition of "weaker" teams is vague.

I compare this rule a lot like the Call of Duty's "Don't camp" rule. It's a tactic and shouldn't be forbidden.

[=MeRk= BluFFeR]

Rushing flags is not automatically an advantage.
Your definition of "weaker" teams is vague.

I compare this rule a lot like the Call of Duty's "Don't camp" rule. It's a tactic and shouldn't be forbidden.

Well Sir in our world it is, and due to the fact that all the MeRk members agreed upon this to promote a fairer game for all the players on our server im affraid its going to have to stay.

And I also think that many other PR servers also operate this rule in different variations agreed so to be frank mate they must think that the rule has some presidence in PR too.

But everyone has their own opinion which is also fair game. Thankyou for your feedback it has been noted if the rule will ever change.

Regards


bluff

[ElshanF]

Merkies know what they're on about. Good rule. However this "can't operate flag" will bring in moments you haven't thought about. But hopefully you'll have a solution for when one problem occurs. There's always that one unexpected moment.

[=MeRk= BluFFeR]

Agreed Elshan there will always be something, that can't be helped but ATM it is working, the matches are getting closer and closer example 9 tickets to spare for IDF last night on beruit, that never happens Russians always get rolled.
Also we are finding a lot more chatting and coordination going on in mumble, there has to be to win since there is no more cheap kills happening at the start of the round which destroys the oppositions chances from the beginning.

[Frontliner]

What about specialized squads such as Recon and Tank Hunters? Do tanks and APCs have to follow the caporder as well(because I have seen people not doing it)?

[Tommygun]

I did notice after a server crash the MERK server starts real quick meaning (I think) its a soft reboot or just a game server restart. Do you think it would be different if the whole server was rebooted properly ie a real power cycle of sorts?

[=MeRk= BluFFeR]

What about specialized squads such as Recon and Tank Hunters? Do tanks and APCs have to follow the caporder as well(because I have seen people not doing it)?

Thats the loop hole Elshan mentioned, As long as they dont rush at the start to get the cheap kills then there isnt really a issue, After 10 mins or so when the game gets into its swing they can operate around the map but not allowed to camp the uncaps,they can role in to clear out and move on but not allowed prolong camping.
We dont want to limit where people can go in the map, its nice to have it free range and the entire map open to be explored but up to a certain point concerning the uncaps.
Recon and Tank Hunters cap operate around the map again as long as there is no rush at the start and they are not sat on a uncap they can operate where they want.

Like I said before we are just trying to make the MeRk server a fairer place to play for everyone on it. The closer the score is at round end the better the round has been for everyone.

[=MeRk= BluFFeR]

I did notice after a server crash the MERK server starts real quick meaning (I think) its a soft reboot or just a game server restart. Do you think it would be different if the whole server was rebooted properly ie a real power cycle of sorts?

Dont really understand what you want to know mate, server stability? Or just the reboot speed?

[Tommygun]

What I was wondering was....would a full restart of the server (powercycle/on off/ full reboot) not be better than a software restart of the game server software?

[brezmans]

Not to hijack your thread here, MeRK gentlemen, just replying as a server host myself.

Tommygun: every server in PR is restarted through a reboot of the PR game server software itself. Windows servers use .bat files or FireDaemon for this, *nix server use a custom script that kills the process and starts the server back up.

This seems to work nicely in most cases, there are exceptions where after one crash, the server seems to enter a sort of crash loop where it will crash two or three times in a row before becoming stable again, but this is rather rare.

The most obvious disadvantage is that a full reboot of the entire serverbox would cause a longer downtime for the server, usually resulting in an empty server since most players are impatient. Coupled with this is that most clans also run their teamspeak and a variety of other services on their servers, so a full reboot is not always an option.

Tl;dr: yes a full reboot might in some cases be better, but this has yet to be proven, the downsides outweigh the advantages imho at this moment.

Hope I didn't step on any toes by replying here!

[Tit4Tat]

Agreed Elshan there will always be something, that can't be helped but ATM it is working, the matches are getting closer and closer example 9 tickets to spare for IDF last night on beruit, that never happens Russians always get rolled.
Also we are finding a lot more chatting and coordination going on in mumble, there has to be to win since there is no more cheap kills happening at the start of the round which destroys the oppositions chances from the beginning.

Yeah, that's because i was on the ruskie side.........no joke.


On a side note, IDF not being able/allowed to rush Factory (dam right) gave the Russians a chance to bring the fight to the city, resulting in a very good Beruit match for both sides.


Good rule.

[=MeRk= BluFFeR]

@ brezmans No toes stood on at all mate I appreciate your time explaining Thankyou Sir

@ Smurf Thankyou for your feedback mate, I was on IDF It was indeed a quality game,so many firefights and scraps going on over the capable flags it was officially how PR was meant to be played in my eyes.

[=MeRk= BluFFeR]

The MeRk Training server is now back up with extra maps