Forum Rules 07/06/2016Introduction The Squad Team reserves the right to edit, update, add and remove rules at any time. Applicable rules extend to the PM system. Your PMs are private, but the Squad Team may be informed about unacceptable PM content by the receiving party. Section I: Posting Rules §1 Show Respect This community can only work if we all respect each other. To that end, it is imperative that any time you engage with another user, either directly or indirectly, you show them respect with the content of your post. In particular refrain from flaming, insulting, abusing, taunting, racism, and other similar types of actions towards other forum users. §2 Attitude & Behavior Poor attitude and behavior are the most common ways a negative / unsafe environment is created and perpetuated. As such that kind of behavior will not be allowed on these forums. Please be mindful of this rule when posting personal positions and opinions regarding topics which could be considered contentious in nature. As a rule of thumb, keep your posts civil in nature, and refrain from making posts that are likely to incite arguments and create a negative environment. As a privately hosted web forum we reserve the right to maintain an environment that we are happy the majority of our players are comfortable with. §3 Swearing While we will not strictly moderate every little swear that occurs, please try to avoid excessive bad language. The moderation reserves the right to remove rants and unsuitable content at any time. §4 Illegal Topics
Prohibited topics include, but are not limited to: Piracy, drugs (including cannabis), pornography, religion, racism, sexism, homo/trans -phobic content, videos and images showing violent death or serious injury, ‘spam threads’, hacking & griefing (endorsement thereof), religion, politics, etc. Prohibition may be suspended for some threads if they are found to be suitable by the Moderation (such as scientific debate).
If there is doubt, the Moderation Team can decide whether a topic is considered illegal. §5 Attitude towards Squad and the Development Team
As per §1 and §2, keep in mind to be respectful and reasonable, not only towards all users of the forum, but also towards the Squad Team and towards any ideas and content and the game itself. Criticism is welcome, but if it is not constructive and/or if it is offensive, the Moderation may need to step in. Please refrain from posting if you are upset, angry or drunk, or you may be punished for things you wouldn’t have otherwise written, which is not in anyone's interest. §6 Language & Legibility
Please post only in English. Non-English content (including non-legible content) may be removed. If you see someone posting in another language because s/he apparently does not speak English, please report their post - if you can, you may reply in their language to explain their question, but please do translate their and your message so it can be reviewed by the Moderation. ‘Hiding’ insults in non-English posts will be punished harshly. Posts written largely in ‘leetspeak’ or full of spelling / grammatical errors may be treated like non-English content. This rule does not extend to PMs. §7 Forum structure & Search
Please ensure when posting a new thread, that the thread is located inside the correct forum section. Check all forum section titles to judge where your thread should belong. Threads created in the wrong forum section will be moved or deleted.
Before posting a new thread, please make use of the forum search to find older threads about the same topic. In doubt, it is recommended to rather post in an existing thread, unless that thread is years out of date. However, do not bump old threads without adding a new question / answer / insight that wasn’t in that thread before - use common sense. §8 Thread Titles
Please name your thread appropriately; the subject title should sum up / explain the content in the thread. If you fail to name your thread properly (such as ‘Hey!’ or ‘Check this out!’ or ‘Help!’), we will either rename or lock the topic. Repeated offense may lead to infractions. The practice of using CAPITALS only in your thread title is not allowed and will be edited or the thread will simply be deleted. Strange or abnormal Unicode characters should be excluded from thread titles for the sake of being distracting and unnecessary.
§9 Thread Capitalization
Please ensure that your post is not in all CAPITALS, as this is not allowed. Any threads posted in all caps will subsequently be removed from the forum. Repeated offenses may lead to infractions against your account. This practice is not approved or accepted here.
§10 Images in posts
When posting images, mind the following restrictions:
.gifs will be allowed and may be removed by Staff if deemed necessary.
Maximum size for images is 1280x1024.
Do not include more than ~1 large image per paragraph of text, unless in image collection / announcement threads. Link to further images.
Consider posting thumbnails. You may post a few more images per post if they are reasonably small, the details are for the Moderation to judge. §11 The use of BBCode
It is allowed to use the BBCode in your posts. Over usage is not allowed. You may use the Bold in a reasonable manner but not for the whole text body. You may use the size feature but in a limited reasonable manner. You may not use any of the additional fonts at all. Color may be used to high light a point but again, not for the whole text body. Moderators will be watching for misuse and will edit when required without giving notice. Continued disregard for this rule will result in Moderator action in the form of warnings. §12 Complaints of Server/Admin Abuse Reports of server/admin abuse will not be posted publicly. All reports concerning this type of behavior should be place in the appropriate sub-forum. http://forums.joinsquad.com/forum/241-report-server-admin-abuse/ All posts made outside of this area will be be removed. Section II: Reporting & Moderation §1 Reporting Posts
There is a Post Report system in place. If you notice a post that violates forum rules, simply use the exclamation mark icon below the users avatar image to send a report to the Moderation. We will then review this post. Your report will not be made public and cannot be linked to your person by anyone outside of the Squad Team. You will not be punished for using the Report system even if the report was false, unless you repeatedly abuse the system to spam it.
Do not ‘report’ posts by replying directly in public to them. In case of spambots, this prompts them to respond in turn, spamming the forum further. This also fuels flame wars and arguments. §2 Reporting Moderators
Moderators are subject to the same forum rules (and some additional rules / exceptions). If you think that a Moderator has treated you unfairly or is otherwise breaking forum rules, please PM the Lead Moderator or any Administrator. Do not accuse Moderators in public, the Squad Team will treat every complaint seriously and it is in our interest to discipline or remove Moderators who are known to break forum rules. §3 Respect Squad Team members and Moderators
Do not ignore or argue against Admin, Moderator or Dev instructions on the forum. If you have a complaint, as per §2, please inform the Team in private. You are expected to follow orders given by the Moderation, Administration and Development Team, and it is necessary for smooth running of the forum to respect their decisions. Being stubborn or ignoring warnings will lead to harsher punishments - however, we do not tolerate Moderator / Admin abuse of power / privileges, so do not hesitate to inform other Team members if you feel treated unfairly. §4 Bans and multiple accounts
If your account is temporarily or permanently banned, do NOT create another account. Bypassing a ban will result in further action, and a permanent ban of all of your accounts.
You are not allowed to have more than one account for any reason. If you share an internet connection with another user who has their own account, it might happen that this account is incorrectly identified as a secondary account - please get in touch with the Moderation or Administration to resolve such issues.
Search the Community: Showing results for tags 'mine'.
Found 4 results
XAHTEP39 posted a topic in Feedback & SuggestionsHello, comrades ! I know, that R-DEVs have too many works and I am sure, that R-DEVs have plans about AP-rifleman class (like a PR class). In this topic, I suggest to discuss realisation AP-rifleman kit for both conventional and unconventional factions and write my vision of AP-mines in SQUAD . Firstly, I note, there is Ottawa Treaty ("anti-AP-mines") , but many counties in "Ottawa" save AP-mine storage, moreover, some big countries don`t join to "Ottawa" (RF, USA, China, India, Pakistan, Iran, Egypt, Lybia, Syria...) Also it is important , that AP-mine is very simple construction and using, so the renewal of production can be fast, if it is necessary for armed conflict. There are three common types of AP-mine: 1) "press activation" , step foot directly on mine for blow up, hit only one person, very lightweight (<0,5 kg). 2) "tripwire" , touch wire near mine for blow up (basically, "tripwire-mines are bouncing-mine) , can hit several persons around, heavyweight (~2-5 kg). 3) "guided" , remote-operated by watcher which command blow up from cover (also can be "tripwire"), can hit sevearal persons in sector , enough lightweight (~1,5-2 kg). I) Unconventional factions (Militia, Taliban and for future Iraq, Syria, Africa, Gaza, Lebanon insurgents). AP-rifleman is a squad-limited kit (like a G3 kit / AKS-74 with optics / LAT kit ... ) , becouse AP-mine is essential part of ambushs - common tactics of unconventional faction. - "Press" mines: PMN-1 (weight=0,55 kg, minimum 3 min for "save-to-armed" mode after planting), PMN-2 (weight=0,4 kg, minimum 0,5 min for "save-to-armed" mode after planting) , it is VERY simple and wedespread mines, exported and copies produced in many coutries. - "Tripwire" mines: POMZ-2 (weight=2,3 kg, radius of guaranteed lethal~7 m, wire lenght=max 4 m, minimum 3 min for "save-to-armed" mode after planting) , POMZ-2M (weight=1,77 kg, radius of guaranteed lethal~6 m, wire lenght=max 4 m, minimum 3 min for "save-to-armed" mode after planting) - it is VERY simple and wedespread mine, copies (especially Yugoslavian) produced in many coutries , OZM-3 (bouncing, weight=3 kg, radius of guaranteed lethal~10 m, wire lenght=max 5 m, minimum 3 min for "save-to-armed" mode after planting) , OZM-4 (bouncing, weight=3 kg, radius of guaranteed lethal~14 m, wire lenght=max 10 m, minimum 3 min for "save-to-armed" mode after planting) . ... there are similar copies of OZM-3,4 AP-mines. - "Guided" mines: MON-50 (weight=2 kg, radius of guaranteed lethal~30 m, frag-sector=54 deg, minimum 50 sec for "save-to-armed" mode after planting). Note: can be "tripware" - wire lenght=40-65 m. II) Conventional factions AP-rifleman is a team-limited kit (like a HAT kit ... ) , 2 kits per full team , becouse ambushs is a not common tactics of conv. factions in SQUAD, mainly AP-mine should use for defence key-positions . a) RF - "Press" mines: PMN-3 (weight=0,6 kg, minimum 7 min for "save-to-armed" mode after planting, self-destruction after min 12 hours) , very rarely mine , because has simple electronics inside , PMN-4 (weight=0,3 kg, minimum 1 min for "save-to-armed" mode after planting) . - "Tripwire" mines: OZM-72 (bouncing, weight=5 kg, radius of guaranteed lethal=minimum 25 m, wire lenght=max 30 m, minimum 3 min for "save-to-armed" mode after planting) . - "Guided" mines: MON-50 (weight=2 kg, radius of guaranteed lethal~30 m, frag-sector=54 deg, minimum 50 sec for "save-to-armed" mode after planting). Note: can be "tripware". b) USA (for other future NATO-factions can be use US or self-produced mines) - "Press" mines: M14 (weight=0,1 kg, without timing "save-to-armed" mode after planting) , widespread mine, many copies and produced in many countries. - "Tripwire" mines: M16/M16A1/M16A2 (bouncing, weight=3,74 kg (A2=2,84 kg), radius of guaranteed lethal~20 m, wire lenght=max 10 m (in one side), without timing "save-to-armed" mode after planting ), also has "press" activation. - "Guided" mines: M18A1 "Claymore" (weight=1,59 kg, radius of guaranteed lethal~30 m, frag-sector~60 deg, without timing "save-to-armed" mode after planting). Note: can be "tripware". "Tripware" method for "Guided" mines (MOH-50/M18A1): It is necessary to discuss: - How much AP-mines and types of AP-mines can carry AP-riflemans (unconv./conv.) ? - How much the number of active AP-mines per one AP-rifleman? 5? 10? Various for different type? - Maybe be able to mix different types of AP-mines for one kit ? - Maybe std/alt AP-kits (like PR) for AP-riflemans with different types of mine? III) AT-mines for conventional factions Combat engineer (sapper) is a team-limited kit (like a HAT kit ... ) , 2 kits per full team , becouse ambushs is a not common tactics of conv. factions in SQUAD, mainly AT-mine should use for defence key-routes. RF : TM-62, US : M15 or M19, GB : Mk.7, GE : DM21. Only 1 mine would be to carry by sapper, becouse AT-mine is heavyweight (9-13 kg) , after planting AT-mine sapper need ammo-crate for reloading. Also sapper should to carry some (~5 items) lightweight (~200 g) distance explosives for blow up enemy (or friendly, if it is necessary) AP-mines or AT-mines. P.S. All names of mines in this post is canonical, so you can to find them in Wikipedia, for example. But I was guided by russian-language sapper-database, which contents many descriptions of many mines - http://saper.isnet.ru/index-mines.html
The title says it all. It would fit the faction much better than IED's (not saying they don't use them). And maybe increase the amount of active mines to 4, but leave INS at 3 (they still have those IED's) + Fingers crossed for AP-mines.
My suggestion included modular improvised explosives and the devices to initiate them. Opfor. Will be able to choose a loadout at a cache or bombfactory that includes the size and type of explosive, intiation device(pressureplates or command wire..). The power source will be bundled with the intitiation. the type of device can be placed through a command prompt in a doorway or window for example. when you are close to a door you can rig it with a 15lb charge and a pressure release switch. Or place a pressure plate in the doorway etc. Leaving a disturbed ground texture or a decal of your choosing.. a rug or maybe just a piece of cardboard. Situation would dictate. so if you bury 50lbs of charge in a roadway it will show as the decoy object you pick and you can run command wire to a hideout. I Do not really know how realistic the command wire could be modeled but if it is too complicated. have a set of wires run out of the ground and towards wherever the sapper places the intition device. So if it is found the blufor can notionally follow the line. bluefor. Blufor will have access to a vallon or other metaldetecting device, explosive charges and a toolset to disarm these devices when found and to assist his unit in a patrol. when moving and having the detector equiped he will sweep it left and right while watching his hud and listening for detection squeels. he can drop babypowder or use spraypaint to mark the safe path and mark possible ieds or where to avoid. this detector and units skillset will include a better knowledge of traps and ieds. So he will be able to use the detector on doorways,walls, debris,and windows in a searching prompt to try and detect a device. If found he can place a limited amount of charges or attempt to reveal the bomb and disarm it. Giving the blufor team intel on a cache or bombfactory. There is so much possible with this its hard to explain it all. Seeing how a vast majority of the fighting in a asymetrical battle depends on using these to balance the battle I would love to see attention to detail in this subject. I Apologize for my poor grammer and mispellings And if any of this has been brought up already. Please tell me any opinions and ask any questions. I personally spent 6 months as a minesweeper on minor ops in 2009 and 7 months as a explosive detection k9 handler in 2010 on a daily basis. Afghanistan both times. Ok guys. Fire away.
well this might be just me but from my experiences i have never felt mines and IEDs of their sort have been effective in PR as they would IRL. Mines and IEDs serve the purpose of area denial but this is hardly achievable in PR. there have been many times when i was an insurgent sapper waiting somewhere to trigger my mines for 15 minutes just to be killed while breaking cover for a second wondering why nothing ever comes my way. An idea i have that might make mines more viable as an area denial would be to give commanders the power to set mine fields. this would be an ability available only for insurgent commander. the insurgent commander would get a cool-down ability(30 mins?) which would allow him to lay down an IED field of specific kind (AP or AT) with a medium spacing between each and a set amount of IEDs. this would make area denial for insurgents a more viable tactic allowing easier ambush. in Addition it would relieve insurgent sappers from trying to lay mines every where just to be shot leaving 5 mines which would be never activated due to kit loss. and here comes the balancing part. The BLUFOR commander would get instead a cool-down ability (15~20 mins) which would basically detect mines at a certain radius. this ability would mark only mines which were in the radius and it would take around 2~5 mins to receive (mark) the intel. this might lead to the introduction of minesweeper role, making the breacher more viable (giving him a minesweeper as kit customization?), and/or making the engineer a more viable role and possibly a necessity for armor crews. this would also make gameplay a lot more tactical on both sides making insurgents consider ambush routes, and BLUFOR consider possible ambushes a more tactical approach to caches and a lot more communication on both sides with command making him more useful. i know there is a lot more balancing i haven't discussed but if i sat here to write them all i would miss my launch so i want to know what you guys think and what possible balancing should be applied.