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 'roles'.
Found 11 results
Recommendation: Analyze this suggestion from a more holistic perspective. (Updated) I believe I may have a solution that would optimize the game a bit further and would definitely be more enjoyable for everyone. A) Multiple Spawn Areas: Preferably three(varies on maps & game-modes) - I suggest having an Optional: Aerial-Support base being able to be destroyed, disabled or Capturable. Main base: logistics, transport For: Squad leaders, Infantry Offensive Vehicle Base = t72, stryker, 30mm For: Crewman Kit, Engineer kit Aerial-support main-base = helicopter, drones, air-strikes. For: Commander roles, and Helicopter Pilot roles. B) Settings/System Requirements: I believe that very few actually use the motion blur so I think we should remove that and the low settings while keeping only the medium to epic settings. I also believe that we should update Requirements by replacing the "Minimum Requirement" with our current "Recommended Requirement'. Settings: Remove All Low settings and Cinematic Shadow = Medium, High, and Epic only. Remove: Distance Shadow Foliage = Medium, High, and Epic only. Remove: All Low Settings System Requirements: Ram Must be: 16gb Ram or higher GPU Must be: GTX 970 or higher CPU Must be: i5-2550k or higher C) Game-play: Ticket bleed changes Troops: Commanders cost = 8 ticket bleed Squad Leaders cost = 4 tickets bleed Normal Infantry cost = 1 ticket bleed Vehicles: Logistics, Transport cost = 15 tickets bleed Small artillery Vics cost = 20 tickets bleed Medium artillery Vics cost = 25 ticket bleed Heavy Battle Tanks cost = 30 tickets bleed Aerial(Helicopter) cost = 30 tickets bleed Deployable/Flags: Radios cost = 30 tickets bleed Captured objectives = 40 tickets bleed I would love to hear some feedback from the community as well, let me know what you think about these suggestions. Will you guys enjoy this more, will it be worse, and please be specific as to why you would disagree/agree. Thanks.
The reason I mention this is because I play Project Reality as well, the father of Squad, and a good indication of where the game is heading. In PR there are dedicated roles, this brings another dimension to game play, I know we are still in Alpha but is it time to introduce class based roles. In PR there are dedicated roles for things like drivers, tank crew, pilots, logistics, and people are 100% focused on those roles. Want to fly a helo? then you need the pilots class, no other person can fly the helo. People set up squads pre-round and name them as such. APC Transport INF - Infantry Armour Air Combat Helo There is also an aspect to gameplay that we don't quite have as yet, engine warming, and turrets and gunners cannot fire for a good while. In fact many vehicles do not spawn in for about 10 mins into the game. Some will agree on this and so won't but it has kept PR alive all these years and the community has a brilliant way of enforcing it's self. Transport for example.. these guys drop inf off on battlefield then drive back to main base and wait for more inf who need a life, same goes for transport helos, this is brilliant and very immersive especially when you see the helos coming back to the aircraft carrier to pick more troops up. Dedicated driver roles for squad could mean no need to ask for squad leaders to give, small pre set squad size of say 4 for drivers. //Thoughts? .. PS Devs >> We need an aircraft carrier map, rhibs will do for now, small boats to get to shore before helo implementation. -- PPS Devs >> Or an airport and ability to enter hangers and planes.. USMC .. Marines >>
AH_Viper posted a topic in Feedback & SuggestionsAs a semi regular squad leader, and a fairly active participant in any game, the main issues that I commonly find is that I've got no quick reference to the role of my other squad members. As I find less and less time to play with my clan mates jumping into a random game every now and then is the most I can do. Trying to remember everyone names and roles is next to impossible when you combine it with ever changing squad members as people come and go, and others switching around to get the kit they finally want. Not everyone has a established background with using comms so understanding garbled situation reports can come a lot easier when you know it's your sniper that you sent on a reccy that's calling out enemy positions rather than the medic standing next to you. Also, more often than not, I end up referring to the roles rather than the names of the players. It just makes more sense to be calling out "sniper, move to this position" as if the role changes between team members and quickly jotted down notes of who's who become out of date - so it would be good to know that it's my sniper responding when they say confirm, rather than someone just having a bit of fun. A classic example is "Jim" being a sniper and I spend a good couple of minutes sending one way commands to "Jim" - only for him to have left 10 minutes ago. Having the role icon next to the player name when they talk on voice comms would let everyone in the squad understand who's sending what. Additionally, having this information at the bottom of the map view would be a nice touch I think. Just a wee 9 box overview of the squad members and their roles so that when I open the map I can quickly see that I've only got one medic rather than two, or that "Jim" has become the medic rather than the sniper. (A wee mockup: http://i.imgur.com/Rn461qZ.png- I think this is needed here as, next to the actual first person view, this is probably the thing I spend the most of the time looking at) I love Squad reliance on communications to understand a lot about what's going on, but to me the reason this works in real life is because of the inferred knowledge about your team mates. I can rely on Jim not suddenly becoming a medic in real life and I can also assume that I'll recognise the voice of my medic when he's near by because he's become like a brother to me. In Squad, that rapport doesn't exist and I genuinely feel some allowances need to be made to cope with the lack of inherit knowledge about the make up of your squad.
I have been on the forums for quite some time, lurking and reading the posts, but never decided to jump in until now. I have played pr for about 8 years, so I am comfortable with the idea of the game, but for better or for worse, don't let that judge your opinion of the idea or interface. I have a suggestion for the way roles would work, and also a suggestion for the UI. (I also found a great location on google earth that should be made into a map! ;D) Here is what it would look like when you load in.. You would be brought to the screen with the squad tab open. From there, similar to pr, you would have a listing of squads. The difference is that these squads have extensions associated with them. This exact example obviously is more applicable to conventional forces and in this case NATO hence the APP6 NATO-Icons. It can be abstracted to other factions though... So say you wanted to create a squad that was anti-armor. When you create the squad, you would be able to pick an extension. In this case below you are creating an anti-armor squad. Now lets say you are a player joining the Heavy AT (HAT) squad and selecting the extension kit. you would have your load out, and then the specialty item.. (I realize this might have to be different for "sniper") If you did not join a squad, your selection would be: Allowing a squad to have a single extension, in addition to being more accurate from a fidelity standpoint, has many benefits that will improve the game play once assets are involved. 1 squad wont have your AA, AT, and sniper kit. Commander role won't be just used to call in area attack. The commander can find assets on the map and position them. (The commander trying to tell a lone wolf with a HAT to go somewhere had a .001% chance of working) A common saying of squad leaders in pr was "Take whatever kit you want, just don't take a sniper or engineer kit". Well this would prevent people from joining a squad and taking kits. an important point would be that you could also use this for claiming assets such as tanks.. First one to claim the extension gets the asset. No more petty arguments about who created the first tank sq.. there could be a vote for extension removal as well. If someone is doing such a bad job that enough of the team votes them out they lose the extension An important point would be that you aren't stuck with your squad extension either... Say you are a rifleman squad and you know armor is heading your way. The SL would go to a crate/fob and be able to change the extension there. Then, a squad member would be eligible for that role... Overall I think this could drastically help keep squads together and keep lonewolfing with specialty kits down. lastly, you'll notice on the map that I have different icons.... The squad leader icon would be their respective extension i.e.: This would allow you to identify which asset is where (assuming the rest of the squad isn't derping around elsewhere)... I saw a trend in some of the map designs going toward stuff like a visible radius around the cap points, and pointers indicating which way players are looking. I think that greatly takes away from a big aspect of the game -that being "communication" The more your map reveals, the less impact communication has on a team's success... Let me explain that: You hear a firefight North of you and you look on the map.. If you see the squad above you all looking east, its pretty easy to guess which way the enemy is.. If you don't have that information you would have to communicate with the group above you to figure out what the situation is. If you are unable to communicate with them, then you will go into the area with a disadvantage... That also goes for cap points. The above cap markers are also APP6 NATO (friendly, neutral, enemy) and the path is indicated with a white line. I think perhaps just having the radius indicated in meters beneath the cap point is plenty of information. I don't like the idea of "mark the very edge of that cap ring and lets sit there".
Hey, Offworld Last night I was having a discussion with some clan mates about specialized squads and how to implement them in to the game. At the moment, people name their squads with an objective in mind (most of the time) i.e. STEALTH, FAST ATTACK, RECON, etc. Well, I have an idea that would let squad leaders specialize the overall role of the squad just has players have the discretion to pick roles with in the squad. First, let me say that this could be implemented wayyyyy down the road when more content enters the game. That said, It be kind of neat if squad leaders could chose a squad roll such as "Special Forces," and this would dictate the kind of weapons and gear that is accessible to the squad members...stuff like silenced weapons, and specialized sniper rifles and what not. Of course you would have to limit this in the same way you limit the amount of players using certain weapons and gear like SAWs, M203s, and Sniper Rifles. For example, you can only have one squad of SF, two squads of assault, and one squad of...idk say, some sort of mechanized infantry. I also think it be a good idea to limit the number of squad members based on the type of squad it is. For example, an SF squad could have a max squad of 4 or 5, or what ever you deiced is appropriate. My buddies thought this was forum worthy, and they asked me to post it here. So I did hahaha. Thanks for taking the time to read. [2.FJg] P01NT_MAN
Hi all, here is a proposal for handling the access to the special roles in a squad: special kits should be locked in a squad and only the squadleader should be able to assign them to specific squad members. Like the squad leader right clicks a squad member in the squad menu and assigns him the role "marksman". The reason for this proposa: like in PR, people join a squad, taking the marksman kit and leave the squad then (in PR most took sniper, HAT and so on). For which roles this could be done is another question (i think on beginning only rifleman and medic should be unlocked, but lets see what you guys write). Cheers Dude
It would be great to put ranks in Squad. They shouldn't be so sofisticated like in Battlefield or COD. Just ranks like 1st, 2nd sergeant, captain, officer etc. With level one you could use all weapons but you couldnt be a squad leader or commader (if you create this role,it would be legendary). So that we dont have noobs in high roles. And maybe orientations like army and one for armored vehicles etc. You could swich branches when ever you want but you could "specialize" in only one so that evryone can see it. You really shouldnt put air vehicles because it would be really overcrowded. And if you put vechiles , you need to adept maps so that vechiles can drive normaly. And it would be also great to put mines and mortars in game. And I almost forgot, you should make more types of squads, like support, reacon, fire-team, and normal one. And it could be of course more than one of one type in the team. Wouldnt be great if we are going to have Squad like this. What you, Players and Developers, think about this. I know that you have at least year or two to even start working on anything from this list but if you could put anything from this in the game I would really appriciate it. Sorry for bad language. :)
I propose a new kit/role/class mechanic for Squad that i fell may work well, and be much better than the current BF2 Project Reality system. The current kit system for PR is certain "spawnable" kits for players they can always use (ex. SL, Rifleman, AR, Medic ect.), while others are "limited" (ex. LAT, Grenadier, ect.), as well all other "requestable" kits are "limited" (HAT, AA, MG, Marksman, Sniper etc.) and once somebody dies with the "limited" kit, they lose that kit unless they go back and pick it up. The new system i propose is a "persistent role" system, were if you die, you do not lose that kit, but the kit does not drop onto the ground. Example, you chose a Machine Gunner kit BEFORE you spawn, you will keep that kit until you deselect that particular kit. You do not drop the kit, you do not lose the kit and no one else will be able to steal it from you. With this, i am also asking why is the grenadier and marksman limited? most modern military's employ grenadiers widely, especially the US Still same "first-come-first-serve" system of kits, and still limited in numbers per kit.Adds new dynamic for squads as staying alive is much more valuable, as if the medics die, no one will be able to be revived, if the AR/MG goes down, you can not just pick it up and lay down fire, if the LAT/HAT goes down the squad will not have Anti-Armor abilities etc.More realistic to real world applications as soldiers like snipers, marksmans, medics, etc. are specifically trained in their respective role.No issue with stealing kits or enemies using enemy kits, as kits do not drop when the player dies.What do you guys think? any suggestions, comments or concerns, i know it is not perfect, but it could work well if fleshed out.
I'm about to clock out for the night, but before I do, here is an idea that I had that is relevant to the "10-Squads" thread here, but is perhaps too much of a tangent. This is an idea for how a Commander might manage assets, and could solve as well as create a lot of problems. The idea is that all assets are done by assignment. There could be "bidding" on assets in a pre-round operation, or Squad Leaders could handle the assessment of their squad's capabilities, and then communicate those to the commander. The idea here is that the Commander has a visual pallete of options that he can use to organize assets. He can drag and drop assets into squads, and from there the Squad Leader dictates roles in a similar manner. Squads would/could likely be renamed to clarify the intended "operation" and assist in organization. This would essentially solve a lot of the "stealing the Logi" problems, because being in a "Logi" role would flag your character and allow you to drive a logi that is parked at base. (I think out in the field they should be unlocked etc). I'll leave that locked unlocked thing for another discussion, but the point is, this could be a system that solves a lot of asset, role, and organizational problems in an intuitive manner.