Forum Rules 07/06/2016
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 'mechanic'.
Found 4 results
The suggested features list (in order of importance); 1 - Reverse prone (ie, lay on your back) 2- Prone rolling (belly down to belly up) 3 - Weapon resting 4 - Emergency reloads 5 - Staged reloads 6 - Sprint dive and/or sliding The explanation: 1 - Reverse Prone (lay on your back) Being able to lay on one's back side is tactically advantageous in certain situations. It's a good way to get out of the way of bullets or team members in a jiffy, or get low while putting a bullet in that tango that just ran around the corner into your face. Being able to roll from belly down to a belly up position means you can check your six and stay low to the ground. 2 - Prone rolling Obviously in full combat gear with a pack, rolling around like Solid Snake isn't feasible. However, being able to roll halfway or 3/4 means a soldier has room to look between his feet (6 o' clock) or to the side (3/9 o' clock) without having to reorient his entire body in an awkward shuffle or magical rotation. Even when wearing a pack, one could still roll onto their bum faster than getting up into a crouch. 3 - Weapon resting We all understand that running a kilometer and steady aim do not go together. That's why rifles have had such long forends or "handguards"; A soldier rests his rifle. This is why shooting in the prone is so stable. If you see a boulder, window sill, tree or other stable surface then you rest your weapon in order to get a good shot. Muscles alone aren't that great at holding a bead on a 200 meter speck. 4 - Emergency reloads If you're in trouble and out of ammo, it might save your butt to just drop that empty mag on the ground and focus on getting more bullets on target. Any ammo left in that mag is left behind, but thirty rounds is ten times more than three (and you might need that extra ammo to survive this encounter). 5 - Staged reloads Remember that time you had to cancel a reload animation (right at the last moment) to knife some fool, only to return to a replay of that reload you just nearly completed? If you drop your rifle mag then need to quickly draw your secondary, your rifle shouldn't have a magazine still in it when you return to your reload. One step of the reloading process was already complete, but the single animation sequence has to complete in order for the reload to complete. I propose a much more convoluted, complicated, sophisticated, technically complex system of staged reload animations for small arms in Squad. Not just for "realism", but tactical depth and quality of life. 6 - Sprint diving and/or sliding Being able to slide or dive into cover is a great way to get low and get to cover quickly. It's also fun and really cool. Thanks for reading! Hope we see some of these features in the future.
Due to the use of the unreal 4 engine I'm assuming that this feature would be possible (all be it very hard work). I'm putting across the idea that damage to certain body parts would have consequences e.g a bullet to the upper arm effecting the accuracy of your fire, bullet to the leg effecting movement speed etc. This is a rough diagram, again this is all open to discussion. Depending on how this concept is received I may compile a list of effects for each body part. (I'd like to note that I am unsure of how the bandages work in this game (whether more than one is needed to prevent blood loss like in PR) so bare with me). I do not currently own the game due to my computer blowing up on me recently. I have however played Project Reality for about 4 years running so I assume I have at least a low level understanding of the mechanics in the game.
I already posted this up before but it was in a thread about the August updates and such but decide to create its own thread so we could all discuss this idea or others. I already got a reply from "Motherdear" which can be found here: http://forums.joinsquad.com/topic/4233-august-2015-pax-prime-report/?p=74463 But i would like it if we the community could discuss or come up with an idea or 2 for some new FOB mechanics. "Firebase spawning now stops when more than 1 enemy soldier is in cap radius or the FOB is 75% captured. Clear out the FOB of enemies and spawning will resume" I personally believe that this needs to be changed to atleast 3 enemy soldiers OR if it was to stay at 2 or more enemy players then change the FOB mechanic to something like this. I know people will say well dont build you fob on a flag (its only the for example) and such and most dont but at the same time you could just have 2 guys on the VERY edge laying in a bush capping it, if it was set up like this then it would atleast allow for the team to defend their fob without them being on it already. At the moment you'll see alot of FOBs being built with structures around them to block off that compound and ladders being built to leave it. Yet outside of this compound you still have to run abit of a distance till you leave the FOB zone. Now you could say that people should be smart and build structures on the edge of the zone and such but i personally think why should you have to build right on the very edge on something to defend it. If you use the example below youll see the red and blue circle, red is the building radius like how it is now but the blue is the capping radius. If it was created like this then building a fob within a structure of blocking access to a FOB would allow better defense as the enemy side would have to breach your building radius before they even started capping. So if they were to start capping then you could only blame lack of defense or not building far enough from the FOB cap zone. how this could work for Squad leaders is when a FOB is placed in the top left it starts of one colour (cap) and when you leave the capping zone it changes to a different colour so you know you should build this far out so they cant get into / onto the FOB. Im not saying you cant build in the cap zone, i think you should be able to build where ever you please within the FOB radius but a smart tactic would be to build outside of the cap radius allowing better defense. I know the whole building FOBs will change when you need to actually bring the supplies in but even then i feel that this idea could work but may need to be expanded on a little better. (Hopefully this makes abit of sense) Looking forward to hearing ideas and such as all this is an IDEA! -
First i know its Pre-Alpha and every can change and second i haven't access now, so i can only discussion with the puplic media content. If you are close to a enemy FOB, a magical state bar appear in the upper left corner. Isn't it critical ? because you can detect a enemy FOB without vision ... maybe its possible to make the FOB state bar invisible? Is that a placeholder for the overrun and C4 mechanic or do you have any other plans i the future ? btw. the search funktion need min. 4 letter to work so i cant search for FOB sorry for a eventually double post.