Jump to content
  • Announcements

    • Merlin

      Forum Rules   07/06/2016

      Introduction   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 'objective'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • OWI Official
    • Announcements
    • Progress Updates
    • Frequently Asked Questions (FAQ)
    • The Official Squad User Manual
    • Development Tutorials
  • International
    • Supported Languages
  • Game
    • General Discussion
    • Questions
    • Feedback & Suggestions
    • Media
    • User Created Guides
  • Support
    • Software Support
    • Hardware Tech Support
    • Website Feedback
    • Bug Report Form
  • The Community
    • Introductions / New Players
    • Teams & Clans
    • Events & Leagues
    • Wiki Development
    • Modding
  • Game Servers
    • Game Server Info & Support
    • Game Server Feedback
  • Off Topic
    • Off-Topic Discussion

Found 4 results


    TEAM Tags: N/A TEAM Name: DANGER CLOSE GAMING TEAM Website: Danger Close Gaming Current Games: SQUAD Voice COMMS: TeamSpeak 3 Recruiting: Yes (Visit our website for further details...) Age Req'd: 20+ Minimum Console: PC TEAM Info: We are a US based, Casual - PC Online Gaming Community with a slogan, "ONE TEAM, ONE MISSION". We are not a clan, but a TEAM of gamer's from various genres that play First Person Shooter (FPS) with a common goal of, "Playing the Objective..." and we're looking for active players to expand our operations in, SQUAD. Our Community is based on TEAM work, Communication, F.U.N. (FIGHT As Team, UTILIZE Your Assets, NEVER Give Up) being Pro-active on our server's, Forum and TeamSpeak 3 (main voice COMMS). We'll provide a server for each of the games we play, do our best to keep games active and add new one's as they evolve to maintain a good balance of interest, but it takes TEAM work from active players to make this happen. The BEST part, "it cost you nothing..." to be part of something GREAT! WifeyBiscuit
  2. Hello! I think it's confusing trying to find a teammates on the map if you don't know which green dot he's. What about adding names of mates on the map? Also when I try to explain to my squad which objective should be defended or attacked I have problem saying the name of the objective i'm talking about because I don't remember it. What about a short name of the objective on the map? Easier and clear comunications Bye!
  3. Dynamic AAS routes were introduced into PR a while back and have made a big difference in keeping the game from getting monotonous. Having a wide open map with every objective up for grabs all the time made for horrible chaos. There was no cap order at all so it broke the game and was too confusing. Consequently, AAS was changed to have fixed routes which also got boring because everyone knew exactly what would happen every single time. Devs were pestered to change objectives or received complains because of changes to them. Dynamic AAS let randomness break up the monotony of fixed AAS routes. So far so good. I'd like to suggest a bit of an adaption, where the teams get to choose where they want to go, but always end up meeting in the middle. Teams that follow the west side of the map, will meet up halfway along the west. Teams that chose opposite sides of the maps are directed choose among objectives that lead them towards meeting up with the other team -- all automatically. Teams choose the objective they want by capping it. However, if squads went to different objectives, the first one capped will cancel the others. I've made an amateur slideshow that gives readers the general idea. What a sample team would see as they start capturing objectives. Remember that the enemy team's location influences where the next new objectives will be.
  4. So i just had this idea while taking a dump, and those are always the best right? It goes in the same direction as the emergent objectives recently suggested by Valmont, just not as far, it's still about capping flags. First of all, to illustrate the idea, admire my leet paint skills: For those of you who don't know PR, this is how the current AAS(Advance And Secure)v4 system works: There are different flag routes for each layer of a map, in my example called Alpha, Bravo and Charlie. At the start of a round the server picks one of those at random and that' where the fight will be. Before that we had AASv3 which had more randomness: The server would pick one flag at random from each group denoted by numbers in my example. This would turn out a bit weird sometimes, for example the route could be, from BLUFORs perspective: first cap 1Charlie, then 2Alpha, then 3Charlie. This could generate very large distances between successive objectives which made the gameplay a bit incoherent at times, and so it was replaced by AASv4. My idea now is this: 1. Let the players decide which objectives they want to go for. 2. Let that decision influence the next objectve, or rather the next set of objectives to choose from. 3. Don't let the teams see what the opponents have chosen and capped until they "meet in the middle", i.e. common objectives emerge, which one team has to attack and the other is defending. So for example Blufor would choose to secure 1Alpha first, which when completed gives them the choice to go for 2Alpha or 2Bravo next, but not 2Charlie because it's too far away. The next objective after that would probably be dependent on what Opfor have been up to in the meantime. I haven't fleshed this idea out fully yet; there are several possibilities of what could happen next: Say that Opfor has been going for 3Bravo, but Blufor was faster to secure 1Alpha. This means that Opfor can't choose 2Charlie any more, and by now everyone knows what the opponent was up to. Now the question is what flag in the middle will be fought over next, which team gets to decide that? We could leave both possibilities, i.e. 2Alpha and 2Bravo in the example, open for both teams, and select whichever is secured first by a team, automatically invalidating the other one. Or, say Opfor secures 2Bravo quickly but despite being in the same group of objectives, they both remain in play, and the attack/defend battle emerges may emerge between them. Another question is who on a team gets to actually make the decisions? This would probably need a commander role, but it doesn't have to be just a click on the map, ordering "We're going for that one!". Rather, you could also have different parts of the team try to achieve multiple possible objectives at once and when one or more of them has been achieved, i.e. flag(s) capped, the CO decides to commit to one of them, opening up the next set of objectives. Since you can't see what objectives the opposing team has committed to (until the strings of flags somehow meets in the middle), rushing one of their first objectives seems pointless. There is the possibility for new kinds of strategies though: Lets say, referring to the picture again, that Blufor rather want the fight to happen on the northwestern half of the map. They have faster choppers or whatever and insert into 3Charlie and hold off Opfor before they can secure it, in order to block that part of the sequence of objectives. Now Opfor has to make a choice: Let's say another Opfor Squad has secured 3Alpha. Now their CO can decide to commit to that route, giving Blufor the fight in the Area they wanted. Or, he can not commit yet and order more troops to help attack and secure 3Charlie. ...which leads me to another idea on the fly: Areas that have been secured but not committed to (either by CO or the mechanic of meeting in the middle) turn "neutral" again when there are no more troops present. Again in the example, Opfor could decide to abandon 3Alpha, or to leave the troops there but don't commit to the objective yet, just in case they can't flush out Blufor at 3Charlie. So, that's it, feel free to build upon it or take it apart.