View Full Version : Base Rape/UCB Attack My views
Im talking about Kashan 32/64
Ok so you in a Frogfoot you waited 20 mins for it, Lovely getting excited about owning loads of armor so your on the runway just about to take off and a jet rips you apart with a Mg >.<!!!
In my opinion i think all baserape of anysort should be stoped like No enemy fire into the Airstrip atall (like the area of sandbags) untill the Aircraft/Armor/Light Armor/Vehicles ETC has left the Sandbagged area.
This is just my opinion on kashan 32/64 for other maps going into a UCB and destroying a Command post or destroying all there assets Tanks ETC
is A Ok
So in a world were i got my own way the server messege would be,
No Attack on the Main base (Sandbagged Area) unless the flag is capped Failure to follow this rule will result in a KICK (Kashan Desert 32/64 ONLY)
Attack on a uncappable base is allowed to destroy the enemy assets (Non Kashan Desert Map)YES i know that the runway can be destroyed (Well maybe we could allow for the enemys runway to be destroyed) BUT if you ingage on a target then the same rules apply?
meh i dont know i just think that waiting for a A10 to spawn for 20 mins then it gets destroyed and they time it so when it spawns again there ready to pounce on you kinda ruins the whole reality, Thing and i know that there are multiple MG and SAM inplacements in the main base area but we all know no one sits in there for 4 hours defending the base, Plus the flag is seperate from the air base for a reason which also means the Command post will not be in the airstrip.
anyway that my opinion let me hear your views
Viglen
I sort of agree, but taking down the runway and anything on it I think should be allowed. But only that, no taking out vehicles such as tanks or anything else in the base. After all, the runway is destructable for a reason, and anyone who lands should really have someone cover them.
I'll be online from tea-time ish I think. I'd like to discuss this, and some other things too.
In fact - I'll throw one into the ring now - Street.
I really think we should remove this map now. I saw the logs from last night, and the server seems to have emptied once Street came on, despite being full for the previous maps.
I know it's potentially a good server filler, but we have more regulars now (there's been a someone von something hanging about I've noticed!) so I really think we can fill the server without it. Removing it will mean the maps can cycle nicely without manual intervention to avoid Street.
Sadist_Cain
25-11-07, 12:56
ahhh how I'll miss street, ah well hopefully extraction will return and I can satisfy my close quarter defence there.
Previously I've been all for allowing bombings of the base, jets on tarmac etc. however the current standard of AA just dosn't cut it to be able to destroy an enemy bomber (maybe it will in 0.7)
as for other maps, going behind enemy lines and destroying assets is a vital part of war, however it is very annoying when you're on the attack, only to discover that the enemy has slipped behind your lines, and trashed your base. True that is reality, but also in reality that squad wouldnt survive to respawn and retaliate once being discovered and shot.
Yet again... HOWEVER for example flast night me and viglen went as a pair and snuk onto the enemy airfield at daqing, we shot a man, so they knew we were coming, and nearly got C4 on their chopper before being taken out.
To me that was a legitimate covert op but as we had more than 50% of tickets, the enemy was fairly concentrated where we were (hence making life difficult).
I can't be bothered to phrase a server message exactly but something along the lines of allowing the destruction of enemy assets with C4 and runway bombings once your team has over half of the flags. A-10 destruction is not allowed until it is in motion
there is a hatched area on the runway where the A-10 is parked until take off, perhaps no destruction of aircraft in spawn locations or summin.
It is easy to just say NO BASERAPE ALLOWED but that seems too easy, but do we have another option? cos as I'm sure youll agree, I have just had a rather long, complicated banter there, diffcult to put in a server message
tis that difficult task of keeping fun, realism and origionality on the server
SargeBanner
25-11-07, 13:20
+1 for allowing the RUNWAY AND AA to be attacked
A10 in hatched area if manned is destroyable ?
Plus i have an idea to keep bases on lockdown
1. At southern end of US base (otherside of sandbags) place:
Mobile AA x1
Humvee .50 cal x2
Possibly one AA infantry x1
2. Have one F16 circle airstrip, for cover.
3. Once second F16 has spawned, man the A10 and park the F16 in front IF SAFE TO DO SO
4. F16 takes off, followed by A10
Perfect =D
Sarge
Sadist_Cain
25-11-07, 13:43
I wish we could completely allowed baserape, the chance to go into damage control, fixing the AA, calling the F16 in for a CAP... or the base is attacked scramble the jets etc etc etc. unfortunately the occaisions when the server is manned enough, has some of us in there to keep squads in order etc. it wouldnt be possible.
hence why we're here working out a comprimise...
WOW a whole post stating the obvious :cool: Thats me on form :D
commando-101
25-11-07, 18:54
Watever is decided it has to be simple - it will never suit everyone.
I think for simplicity only spec ops should be allowed to attack uncaps/mains.
My thinking is as infantry they can do a little damage but are easily contained once discovered - not like an A 10!
It will keep some elements of realism but will generally be a lot harder to 'baserape'
Maps where the main cannot be entered will effectively mean no spec ops attack.
There should be a rule however that air are allowed to press home an attack if the bandit runs for home - someit like 'attack of recovering aircraft & runways allowed'.
As far as I know, infantry, land vehicles and helicopters cannot enter the base due to the "Dome of death". Only planes can enter.
commando-101
25-11-07, 19:13
some maps do - some maps don't - thats what makes it hard to have a generic rule m8
Each team on Karshan should devlop the skill so called "No-Fly Zone", F-16/Mig should patrol the airfield.
This works with anything you want to cover, all you need to do is fly, either formatiot or alone, you need to determine the area you want to defend, like a Tank group, just fly around in circles around them or fly around in a box. You wont get much planes/helis attacking you (and your airfield) and making it totally shutdown and/or being destoryed.
Sadist_Cain
26-11-07, 04:15
Exactly, but at the same time, I like the safety of base, seems that with the recent server activity we'd have enough people to jump on AA and defend incoming aircraft needing repairs... then again....
As commando rightly says, we need a generic rule that stamps out any nastiness, maybe we should have a list of the rules clearly visible on the mainpage? like a small notebook style thing always on. because the rules will never be clear for each map, thats why we need our loyal T&T members :D to be making sure everyone is understanding in what needs to happen.
Personally I thought tonights Kashan round was beautiful, everyone on each side was effectivly adminning the server (I think taking some of the load off Epoch to handle everything whilest flying at the same time) and as kashan is very diffcult to effectivly run for team play I think we did rather well, (how many squads did we unlock? :P)
http://en.wikipedia.org/wiki/Rules_of_engagement Seems the military have the same issue, not too restrictive, not too loose lol
AND remember the 7 P's Prior Planning and Preparation Prevents a Pretty Poor Performance try and memorize it go on :)
Hoooow about Making it sound cool for folks aswell I know its daft but instead of having RULES *puts on suit* Rules Of Engagement R.O.E. That way we can have the
T&T Field
R.O.E Manual
"All Enemy Aircraft May Cross Over Base Boundaries While Engaged In Combat"
"Spawn Kill/Rape NOT Allowed, Spec Ops May only Destroy FIXED Enemy Assets Within Enemy Base While Their Team Is On Defence (Ticket Bleed)"
"Recon Fly-Over On Enemy Bases Under STRICT R.O.E One Pass Attacking Ground/Air Targets Prohibited"
"Aircraft R.O.E For Ground Targets On Uncap Flags: Do NOT fire Unless Fired Upon"
"For A Full List Of Our Rules Please Briefly Check The R.O.E Manual On TacTeam.org"
An idea for a server message ^^^
On the full list of rules we can explain the following (change as anyone sees fit)...
Tacteam Rules of Engagement
Project Reality Campaign
The T&T R.O.E field manual intends to maximise the effectiveness of military hardware within the Combat Theatre Of Operations. However Due to the changing climate of warfare, this manual is subject to immediate change
Hostile Airspace/behind enemy lines: T&T Defines hostile airspace as enemy bases and uncap flags.
Spawnkilling: T&T regards Spawnkilling as the act of lying in wait at either a spawn point, or inside the enemy base for an enemy to spawn and then killing them. With no reason or benefit to your team or squad. Such an act is a wasteful use of rescources
Multiservice Procedures For Joint Tac Team Air Operations Center (JTTAC) and Tac Team Air and Missile Defense (TTAMD) Coordination
Allied aircraft are authorized to pursue engaged hostile aircraft in combat inside enemy airspace (this includes calling in Aerial reinforcements from within international airspace).
If within hostile airspace allied aircraft must retreat immediately to international airspace pending:
Destruction of the Origional Target Aircraft
Accidental destrcution of a non hostile, non-target unit
Loss of visual contact with target aircraftClose Strike Support aircraft are prohibited to mobilize bombing missions with intent to destroy any Airbourne, Fixed or Mobile assets within hostile airspace.
Strike aircraft may be granted access inside hostile airspace by a T&T officer for emergency air support. providing the following R.O.E are met:
The target must be of hostile intent towards troops on the foreward line of operations (FLET)
The target must be in a position whereby A. A strike through hostile airspace is neccessary and justifiable B. The targets position threatens the security of allied forces on the FLET C. The targets locations threatens ABSOLUTE minimal collateral damage to enemy assets.Recon flyovers of enemy facilities within hostile airspace are authorized. Recon Pilots must follow R.O.E To retreat to international airspace upon being engaged by the enemy.
Recon Pilots are NOT permitted to engage in or return fire to enemy targets within hostile airspace
When engaged in combat over enemy airspace pilots must change their R.O.E for ground targets; Do NOT Fire Unless Fired Upon.
CAP (Combat Air Patrols) Are only authorized within international airspace
It is worth noting that the team must coordinate to establish an effective defense plan on the TTAMD against incoming fighters whenever an aircraft returns to base for repairs/ammo
Tac Team Covert Special Operations
Combat Procedures For Hostile Environment Deployment
Primary R.O.E: Retreat If Fired Upon
Spec Ops Are only authorized to covertly deploy within enemy bases and uncap flags as an emergency measure in case of ticket bleed
Spec Ops Primary role is one of reconnaissanc, and asset destruction
Spec Ops Are authorized to destroy the following fixed enemy assets
TOW missle
Command Post
Firebase/Bunker
Fixed AA
Destructible Buildings
Bunkers, Barbed Wire etc.
BridgesWOW! ok im really done, if you hate it ah well. I got carried away and had fun :D I hope this idea works to solve the problem of having an interesting set of server rules, I havnt seen much like that on other servers, quite easy to follow I think, I asked my dad about R.O.E manuals and had a lil browse on some on the net. Wanna know what you guys think? :P
Wow fucking hell cain rofl
Now the problem is fitting all that in the server messege
*SPAM ALERT SPAM ALERT* LOL
but on a serious note.
We should put it on the website make it a .txt file or a simple html written page
I.E www.tacteam.org/rules.txt (http://www.tacteam.org/rules.txt) and the text would contain
T&T Field
R.O.E Manual
"All Enemy Aircraft May Cross Over Base Boundaries While Engaged In Combat"
"Spawn Kill/Rape NOT Allowed, Spec Ops May only Destroy FIXED Enemy Assets Within Enemy Base While Their Team Is On Defence (Ticket Bleed)"
"Recon Fly-Over On Enemy Bases Under STRICT R.O.E One Pass Attacking Ground/Air Targets Prohibited"
"Aircraft R.O.E For Ground Targets On Uncap Flags: Do NOT fire Unless Fired Upon"
"For A Full List Of Our Rules Please Briefly Check The R.O.E Manual On TacTeam.org"
An idea for a server message ^^^
On the full list of rules we can explain the following (change as anyone sees fit)...
Tacteam Rules of Engagement
Project Reality Campaign
The T&T R.O.E field manual intends to maximise the effectiveness of military hardware within the Combat Theatre Of Operations. However Due to the changing climate of warfare, this manual is subject to immediate change
Hostile Airspace/behind enemy lines: T&T Defines hostile airspace as enemy bases and uncap flags.
Spawnkilling: T&T regards Spawnkilling as the act of lying in wait at either a spawn point, or inside the enemy base for an enemy to spawn and then killing them. With no reason or benefit to your team or squad. Such an act is a wasteful use of rescources
Multiservice Procedures For Joint Tac Team Air Operations Center (JTTAC) and Tac Team Air and Missile Defense (TTAMD) Coordination
Allied aircraft are authorized to pursue engaged hostile aircraft in combat inside enemy airspace (this includes calling in Aerial reinforcements from within international airspace).
If within hostile airspace allied aircraft must retreat immediately to international airspace pending:
Destruction of the Origional Target Aircraft
Accidental destrcution of a non hostile, non-target unit
Loss of visual contact with target aircraftClose Strike Support aircraft are prohibited to mobilize bombing missions with intent to destroy any Airbourne, Fixed or Mobile assets within hostile airspace.
Strike aircraft may be granted access inside hostile airspace by a T&T officer for emergency air support. providing the following R.O.E are met:
The target must be of hostile intent towards troops on the foreward line of operations (FLET)
The target must be in a position whereby A. A strike through hostile airspace is neccessary and justifiable B. The targets position threatens the security of allied forces on the FLET C. The targets locations threatens ABSOLUTE minimal collateral damage to enemy assets.Recon flyovers of enemy facilities within hostile airspace are authorized. Recon Pilots must follow R.O.E To retreat to international airspace upon being engaged by the enemy.
Recon Pilots are NOT permitted to engage in or return fire to enemy targets within hostile airspace
When engaged in combat over enemy airspace pilots must change their R.O.E for ground targets; Do NOT Fire Unless Fired Upon.
CAP (Combat Air Patrols) Are only authorized within international airspace
It is worth noting that the team must coordinate to establish an effective defense plan on the TTAMD against incoming fighters whenever an aircraft returns to base for repairs/ammo
Tac Team Covert Special Operations
Combat Procedures For Hostile Environment Deployment
Primary R.O.E: Retreat If Fired Upon
Spec Ops Are only authorized to covertly deploy within enemy bases and uncap flags as an emergency measure in case of ticket bleed
Spec Ops Primary role is one of reconnaissanc, and asset destruction
Spec Ops Are authorized to destroy the following fixed enemy assets
TOW missle
Command Post
Firebase/Bunker
Fixed AA
Destructible Buildings
Bunkers, Barbed Wire etc.
Bridges
or like i said a basic html page, But the other thing is the punishment i think if someone goes against the rules its a KICK the reasoning would say FAILURE TO FOLLOW R.O.E CHECK WWW.TACTEAM.ORG/RULES.TXT
if they proceed to go against the rules a 1 WEEK BAN should be issued
commando-101
26-11-07, 09:20
freakin nice bit of work & I think a sound concept.
Make it much simpler to have one message that says 'see website for server rules'
I think our regulars will soon become familiar & would prolly put newcomers right themselves-as well as T&T members.
Additional benefit would be more hits on the site.
I'll read the posts above when I get more time (or retire). However, I've always tried to avoid a "see website for server rules" approach, since I've always tried to minimise the number of rules we apply.
I don't want us to become one of those servers where everything you do is subject to a rule. The basics (like queue jumping, base attack etc) can be spammed thru server messaging (I'm gonna work on tidying this up later this week if I get a chance, to make it less intrusive). I avoid mentioning TK in rules, since that's common sense and doesn't need mentioning.
That said, more hits on the webby would be great, so perhaps we can knock something up. Maybe not a lis tof rules, but more an 'ethos' ......
I'll be online tomorrow night hopefully, so we can look into sorting something.
We are not T&G, i repeat we are NOT T&G now say it to yourselves wan meeeelion times with your pinky against your bottom lip.
Good posts, but my beard grew by the time i'd finished it.
How ever, i do like the in game menu :D
Sadist_Cain
26-11-07, 13:17
noooo What I mean is using the server messages above the ROE bit, theres only 5 of them that sorts out the idea I think that gets the message across and theeeen, the biiiiiiiiiiiiiiiig list of rules can be on the website.
This way we have the server messages letting people know that run home attacks are allowed and that spec ops are allowed to destroy things on the back foot, those in combat who go into enemy airspace, get shot by AA and return fire anyone who complains we can give an easy "he is allowed to return fire if fired upon"
If WIMP (Whiney Incompetant Meaningless Person:D) dosn't like the idea he can then go on the website and learn of our R.O.E and some small occaisions where he is permitted to return fire thus giving him the feeling of knowing a lil more of whats going on.
I've tried to combine the server messages to add curiousity to the main rules, also tried making it so that rules cant really be broken easily (if i see a server message that says Base/ Spawn rape NOT allowed, I get nervous to go towards the base, perhaps if a few of our regulars look at the R.O.E and then they in turn can tell WIMPs about Run home rules etc or just "piss off and look on the website n00b!" as I'm sure some uber leet will
I know what you're getting at matey, and i agree partly, but we do have to be careful about slapping too many ROE's up or we're going to end up like a certain server you all moan about.
Having a few, basic "guidelines" is fine as long as people follow them providing we don't end up to be seen as nazi admin kicking and slating every tom dick and harry for breaking them.
Sadist_Cain
26-11-07, 14:37
We don't have to use them strictly, just as guidelines, at the end of the day whoever is T&T in the server will have the final say if someone starts bitching, if we have those 5 server guidelines up then thats good enough, if the folk want summin to exactly stress to them what the idea is then they can read our rules... They just look so pretty :) what with bullet points n' the underlining and such:p
Mostly I'm just trying to clear up any short fucking around with chasing planes home, "waah i shot my AA at him and he shot back" well duh m8ey thats what happens" tbh the big list is mainly just padding so that looks groovey (oh go on it has a goovey vibe :D)
Short version: allowed to chase jets home, return fire if fired upon, but run away. Use spec ops to blow up enemy assets anywhere when youre losing. dont spawnkill and don't be a dick
But I can't give the above a title of: Multiservice Procedures For Joint Tac Team Air Operations Center (JTTAC) and Tac Team Air and Missile Defense (TTAMD) Coordination
we either need to have some way to establish what exactly is spawnkilling and baserape, and what is tactical warfare along with the pursuit of hostile aircraft, I like the idea of working in Do Not Fire Unless Fired Upon rule, as that is something that is followed a lot by the military. however if we cant figure out how were going to explain to people the difference between being a spawnkilling twat and a Covert Op then well just have to give up and go for No Base attack or spawn kills, end of...
Last thing I want is a RULE listing like TG: There will be NO...
There will be NO...
Not allowed...
etc etc
Hence why I went down the line of Rules Of Engagement instead, H-AT sniping can still be plentiful :D just want those who briefly visit to understand the idea that maybe if a tank is stupid enough to fire at you as he rolls outta main base hes allowed to be taken down, that dosnt involve strip bombing the entire runway and destroying all sircraft that wasnt engaging you.
Dam I have spare time
So basically, if you chase an enemy helo or plane to their base, they are free game.
Can't argue with that.
However, wonted destrcution of vehicles as they sit there at the base isn't allowed.
Cool.
commando-101
26-11-07, 15:12
Like the short version mate.
We are only having this discussion because the server is v popular!:D
A position no doubt TG found themselves in as well.
Short is better - longer is bad
Rules of Engagement.
1/. Point.
2/. Shoot.
Not necessarily in that order. :D
Can you set a long spawn time for anyone killed in an uncappable base?
Or if a plane on the ground is bombed make the bomber blow up in mid air with a 30 minute spawn time?
How about that red hatching that eats you if you go off the map?Could that be used for enemies in friendly bases?
Sadist_Cain
26-11-07, 16:40
So basically, if you chase an enemy helo or plane to their base, they are free game.
Can't argue with that.
However, wonted destrcution of vehicles as they sit there at the base isn't allowed.
Cool.
Exxxactly, that way you can imagine the frantic run home to base while shouting "shiiiiiiiiiittttt!!! hes behind me someone get on AA!"
That woulda been fun because I noticed some fellows starting to bug out from chasing us as we got close to north village :S or near the oil fields as they realise were running for base
As for the R.O.E I didnt mean it as a huge long list of rules as in "oi you did, you check to see that the bloke you shot at was doing this that etc etc
I was just trying to make rules sound less like rules and more like an operations manual. for example this lil bit here>>>>
Multiservice Procedures For Joint Tac Team Air Operations Center (JTTAC) and Tac Team Air and Missile Defense (TTAMD) Coordination
Allied aircraft are authorized to pursue engaged hostile aircraft in combat inside enemy airspace (this includes calling in Aerial reinforcements from within international airspace).
If within hostile airspace allied aircraft must retreat immediately to international airspace pending:
Destruction of the Origional Target Aircraft
Accidental destrcution of a non hostile, non-target unit
Loss of visual contact with target aircraftClose Strike Support aircraft are prohibited to mobilize bombing missions with intent to destroy any Airbourne, Fixed or Mobile assets within hostile airspace.
Strike aircraft may be granted access inside hostile airspace by a T&T officer for emergency air support. providing the following R.O.E are met:
The target must be of hostile intent towards troops on the foreward line of operations (FLET)
The target must be in a position whereby A. A strike through hostile airspace is neccessary and justifiable B. The targets position threatens the security of allied forces on the FLET C. The targets locations threatens ABSOLUTE minimal collateral damage to enemy assets
Now I know you look at that and think Argh! restriction! break it down and all I'm really saying is It's ok to chase a jet that you are fighting back to his base, if you cant see the jet any more piss off out of their base (simple common sense, if youve lost him you arent in combat any more, so dont sit there flying around the enemy base waiting for him) if youve destroyed him, then get out of the enemy base (obviously that counts as base camping) and if youve accidently blown something up that you shouldnt of inside the enemy base bug out, you know that wasnt your target so stop.
Second bit, again common sense can determine whether it is fair to take a shot at the tank rolling up towards the first MEC flag at main base (kashan example from there I think he can hit that radio tower, cant he?) if the tank is just rolling uphill then is that a fair target? however if that tank has shot and destroyed two of your humvees or is shooting/shot down aircraft, do you believe it is fair for an aircraft to breach enemy airspace over the FLET in order to take out said target? Personally of course I believe so
That took a hell of a lotta explaination, hence why I wrote it all as an R.O.E manual designed to enforce common sense gaming, I believe that is difficult to break these R.O.E without deliberate intention e.g unprovoked bombing run on main bases or waiting in enemy base with no clear intention besides spawn killing.
I don't mind at all if you guys think theyre too much armyness :P I just dont want you thinking I was trying to set in stone solid boundaries on the server, as you know thats impossible, tis war baby :P
Bare minimum on the server messages but it might satisfy the lil geeks like me to have a thing on the main site just to clarify what is fair game when youre chasing an enemy into hostile airspace, theres a lot of variables to consider, and I for one don't wanna spend time explaining the server rules to everyone who asks, itd be nice to just say to those lacking common sense "check the webby youll see EXACTLY what we mean" instead of a quick explaination knocked up there on the spot
Exxxactly, that way you can imagine the frantic run home to base while shouting "shiiiiiiiiiittttt!!! hes behind me someone get on AA!"
That woulda been fun because I noticed some fellows starting to bug out from chasing us as we got close to north village :S or near the oil fields as they realise were running for base
As for the R.O.E I didnt mean it as a huge long list of rules as in "oi you did, you check to see that the bloke you shot at was doing this that etc etc
I was just trying to make rules sound less like rules and more like an operations manual. for example this lil bit here>>>>
Now I know you look at that and think Argh! restriction! break it down and all I'm really saying is It's ok to chase a jet that you are fighting back to his base, if you cant see the jet any more piss off out of their base (simple common sense, if youve lost him you arent in combat any more, so dont sit there flying around the enemy base waiting for him) if youve destroyed him, then get out of the enemy base (obviously that counts as base camping) and if youve accidently blown something up that you shouldnt of inside the enemy base bug out, you know that wasnt your target so stop.
Second bit, again common sense can determine whether it is fair to take a shot at the tank rolling up towards the first MEC flag at main base (kashan example from there I think he can hit that radio tower, cant he?) if the tank is just rolling uphill then is that a fair target? however if that tank has shot and destroyed two of your humvees or is shooting/shot down aircraft, do you believe it is fair for an aircraft to breach enemy airspace over the FLET in order to take out said target? Personally of course I believe so
That took a hell of a lotta explaination, hence why I wrote it all as an R.O.E manual designed to enforce common sense gaming, I believe that is difficult to break these R.O.E without deliberate intention e.g unprovoked bombing run on main bases or waiting in enemy base with no clear intention besides spawn killing.
I don't mind at all if you guys think theyre too much armyness :P I just dont want you thinking I was trying to set in stone solid boundaries on the server, as you know thats impossible, tis war baby :P
Bare minimum on the server messages but it might satisfy the lil geeks like me to have a thing on the main site just to clarify what is fair game when youre chasing an enemy into hostile airspace, theres a lot of variables to consider, and I for one don't wanna spend time explaining the server rules to everyone who asks, itd be nice to just say to those lacking common sense "check the webby youll see EXACTLY what we mean" instead of a quick explaination knocked up there on the spot
Ehhhhh, we kind of get the poing Sadist_Cain, WE GET IT ALREADY.
Oh i forgot to ask you before you blew yourself up in my avater, How did it feel?
Can we drop the rules discussion for the moment please? I'm not likely to be around for a few days, and I don't want to get out of sync with the discussion.
well I have to agree,its so annoying when they attackk u before u even came outta spawn, with tank or plane, whats the point of continuing playing if they gonna kill u once u spawn.
in POE2 one some maps, you will automaticly get kick once u kill someone on enemy base. I think we need that scrip here. you have like 4 tanks, 2 aa, 2 apc. camping the main flag, while they dont have any other flags cept 1 or 2, and then u got thier plane shooting u too,
specialy when they use the mig29 to kill ground units with its AIM missiles
wooly-back-jack
27-11-07, 21:34
how about a server slogan of "Keep it cheerful NOT cheap" should cover it all :D
Lol wooly.
I really don't like 'conditional' rules .....
If this then that else the other.
If we did that, we wouldn't need a list of rules - we'd need a fecking flowchart!
Agreed we need to inform our guests. Rules on the server should be informative, but brief. We're playing remember, not revising. A more expanded rulebase on the website is a good idea, but needs to be bullet points, not a rewrite of the Bill of Rights.
Sadist_Cain
28-11-07, 12:47
okies but just know I wasn't trying to do a bill of rights. I was trying to avoid a list of DO NOT like on some other servers, so thats why I took the R.O.E manuals I think one was from bosnia and the other was the Iraq R.O.E.
so that it has that army effect to try to get soldiers in battle to follow R.O.E instead of getting kids on a game to play by the rules.
Sadist_Cain
28-11-07, 18:32
Dam, wont let me edit my last post. What I mean to say is we play a reality combat sim, why don't we at least have the rules phrased more like they are in a genuine field manual?
vBulletin® v3.8.3, Copyright ©2000-2012, Jelsoft Enterprises Ltd.