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 'march recap'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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 1 result

  1. Hey Squaddies! The text you’re about to read is the minutes of a meeting hosted by Offworld Industries to gather community feedback. Roundtable events are based on the most recent Recap and we’d recommend reading that first. Please note that the text represents a dialogue between the community and developers, not a planning document. OWI Attendees included Axton, StrangeZak, Fuzzhead, and the host, Nordic. Note: OP refers to Original Poster, someone from the community. Text in Italics represents responses from OWI members, or general overview text sourced from us -- not the community. Attempts to preserve the discussion as it happened between topics and questions have been made. [Introductions, Rules, and Format. Contact Nordic for further information on participation.] Localized vehicle damage model. Part of the point is to increase gameplay depth, especially for APC/IFVs. Increasing their desire to work with infantry and the rest of the team. Also, they are large, very cool vehicles, so standing next to them during a fight is awesome. The values will continue to be tweaked, as this is just the first iteration of the model. Community wants: A visible model in firing range (Being worked on. Thanks Chuc! \o/) Yep, there are lots of AT options. Ammo capacities may change with balance, including the availability of ammo on vehicles. (Not likely to be in v11, but maybe v12.) One-shot kills are not desirable. (One-shot disabling may be a different story.) Ammo Changes to the way ammo is available in the field are coming, including stashing some on vehicles. Man-portable ammo. (Planned, but likely not for v11.) Resupplying in the field should probably enough for one person, but still in testing/design. (For example, 75 points would be one LAT, or 3 rifleman, etc.) Will there ever be ammo bearer role/kit? Maybe. Inventory customization potential post-1.0. (e.g. Opting for no grenades in favor of more ammunition.) Adding more kits is delicate, since other ones may become unused in your Squad. It does make for more specialized decisions though. It would definitely have to be fun to be implemented. Interlude It was agreed by all that it would be helpful to have a larger picture, a bigger sense of the high-level plan for Squad. It’s difficult to discuss some changes, as they are so linked to everything else. (e.g., ticket bleed.) Heck yeah it is! We're looking at a couple options to expose more planning and more feedback options, such as Trello. Vehicle gameplay We expect vehicle gameplay to shift across the next couple of patches, as more armor and anti-armor options are introduced. Additionally, the updated damage model is going to impact vehicle gameplay. Ideally, the shirt will go more toward a "thinking person's game," with increased emphasis on working with vehicles as a team. Make communication between vehicle and infantry more rewarding, and easier. Less dying/ self-sacrifice. Vehicles lose their purpose too easily, especially Logistics. Try to promote more thoughtful gameplay, more risk versus reward. TOWs will be a huge threat. Emphasize vehicles working together. Two vehicles together should be way more effective as a team than solo. Still too prone to flipping. Q: How do you feel about adding manual transmission? Automatic is bad for hilly maps. Mapping and design question. We have some of the steepest roads in the world in Squad, more so than actual roads in New Zealand. A US or Ural truck would go at walking speed, if it moved at all. Bumping up the torque would effectively make them mountain climbers up to 90 degrees. Zooooom! OP: Offroad mode (shift) doesn’t work very well right now. Noted. AAS Ticket Changes Changes to the AAS system are coming, starting in Alpha 11. It’s likely we will move towards "Static" AAS and Random AAS, as well as trying more experimental layers, but they will require testing and feedback. A lot of dynamics of the game will be changing in the next couple patches. Values may need to change, and we plan on working with the community to do so. Teams will now lose tickets when they lose a flag. Currently: +20 tickets for capturing a flag, -40 ticket for losing a flag. +20 for capturing a neutral flag. Ticket loss will be increased in v11. It will also be standardized. The values are standardized for simplicity; nobody wants to have to memorize a wiki for each flag. Squad has a transparency issue with tickets in general. Bleed is confusing, being somewhat of a background element. *Especially* for new players. The numbers are not set in stone. Some experiments with bleed time and values are being examined too. If feedback (yours and ours!) is poor, we will revert those changes. If you’d like to be involved in testing changes, reaching out to Fuzzhead might help. Bleed changes are small -- they’re not going to revolutionize AAS, but they might help you see different parts of the map and think about them differently. They aren’t expected to be a panacea. We’re still keeping an eye on the overrun changes made to FOBs. Community: Focus on tickets can turn into spreadsheet simulators, taking some of the magic out. All of these AT changes might impact AAS in unknown ways. Please be considerate of the balance between attackers and defenders, especially in terms of pacing. HUD elements for ticket changes would be nice, maybe on the map. But don’t overload the UI, please. (Fuzzhead: Squad may have too much HUD. It’s good, but there’s a lot there when you don’t need it.) Mercy Bleed OP: Does Mercy Bleed actually do anything for the community? Is it harmful? Where does the feedback come from? A: It seems to incentivize continuing attack, especially in the first five minutes. OP: Players may not be incentivized to attack over defend when bleed is active, especially with super FOBs. A: While it may not change the mentality of the average player that isn’t reading the forums, etc, this would be a change that’s going to impact player behavior. It’s a choice on map basis: part of it to get large, unused portions of the map involved. People mentioned they were never fighting in many areas of maps. OP: “We do see on general servers, a lack of motivation, or a give up mentality, when the center point is captured.” User example: It seems slightly punishing, forcing players to take all of the flags instead of setting up a solid defense with more than half the map. Different user counter-example: One of the best ways to play AAS right now, especially if you capture Papanov, is to turtle and not fire another shot for the round. You don’t attack them because you don’t have to. That sucks; it’s boring. Q: “Why should I leave the first flag super fob?” The enemy has +20 tickets for every neutral flag, they know where you’re at, and you should expect mortars and armor very soon. Someone will always want to push. We can think up a hundred scenarios, but we won’t know for sure until we test it. Admin Tools We’re aware of the frustration server administrators have with the tools and hope to improve upon them in the future. We run into them too, especially during playtest. However, they are not the top priority right now but will receive some attention. Better admin UI being looked at, for example, you may be able to ban someone from a radial menu or the scoreboard. Replay functionality is currently buggy. It can be used, but take care when skipping forward; turrets will disappear, soldiers do some weird stuff. Improvements are being made Community would love: MOTD (maybe on the loading screen, or during the queue, or a specific tab) Maybe similar to Counter-Strike HTML options -- something that allows it to be recalled when necessary. Warning messages directly to a player, before kicks/bans Visible admin indicators (optional) Improved chat logging Idle/AFK kick RCON Team management tools: move players to squads, etc. Force join squad timer. (There are problems here with locked or full squads, players that don’t want to squad lead, etc.) Access for modders and modding, please Many functions could already be made as a mod. Zak is willing to assist people working on them, but be aware that it requires a custom server. Mod support is still under continuing development too. Q: Will there be more licensing/guideline enforcement? That’s a director-level decision, but we expect some changes. Stay tuned. Patches/Optimization In the wake of getting to v10, we’re definitely aware we need to work a little harder on our patch scheduling and transparency. Currently, there are several programmers dedicated to optimization. They’re using the tests as opportunities to collect performance profiles, hunt fixes, and eke out more FPS. Further, we’re developing tests to focus explicitly on optimization. Community: Faster patches with less fixes is a-okay. (“Patch bugs asap! We don’t mind!”) Large patch size is still a concern, especially with small fixes. (i.e., you have to download another 30 gigs.) Latency feels increased. Can’t tell if it’s server issues or other. Some community members confirm some server performance boosts in 10.2. Fuzzhead: One thing can hold performance back. You may not notice the changes until we find that one thing that’s causing problems, even if other items have been optimized. I think we’re getting close. Gameplay Some of the upcoming changes include prone to stand speed adjustments, addressing gun wobble, examining sway (Yep, the m4 needed love.), recoil patterns, as well as changes to ADS timing. We’re also aware of the slight desync between first and third person views and will be tightening that up. Hopefully, this will increase responsiveness in hitting your target, especially when your target is peeking around corners. Q: Prone to stand is changing. Does stand to prone change? A: Maybe. It’s something we’re considering based on real world behavior, even among the developers. Most people WILL throw themselves down real fast… even in paintball.) The desynch between 1st and 3rd person: 3rd person view is sped up a little over it. Side effect: latency has you showing up a little sooner, but the speed compensates. If you’ve never noticed it, you should notice it even less now. It’s often a trade-off between looking a little silly and playing how people expect it. Leaning movement: Try walking while you lean. It’s hard. Especially with a weapon. Your feet don't move the same way. But we understand it’s a game too. Fuzzhead would limit crouched movement and movement while leaning would be slow. This is a preference, not an edict. Fine-tuning is an on-going process, especially looking forward to vehicles. Community: Leaning could limit stamina regen. Fuzzhead would like to see less restrictions on logistic trucks. May not happen, because of the obvious issues, but the benefits may outweigh it. Additional admin tools could help with this. Because Squad’s audience is bigger, we have to be aware that new or toxic players can impact things like this. Making sure small squads are still viable is important, especially for specialization. Occasionally mirrors real life too. FOBs and Spawns Q: FOB changes? What’s the ideal version? Are you happy with spawning now? Fuzzhead: Oh no, it’s going to change. The drasticness of the changes is up for debate. Definitely, it’s not in its final form. Rally points definitely need a pass. A hard overhaul to how they work and their relationship to the pacing of the game. There’s a fine balance; you want a game that is accessible and squad leaders have this ability to keep their squads together, having fun, in the action. Too much reliance on rally points creates a game more about placing spawn points. The overrun mechanic on the FOB is subtle, but it changed the pacing a lot. We have to be careful when changing spawn mechanics, even small changes. We have lots of feedback coming in for spawning. We have our own takes. And there’s a lot of ways to go; Fuzzhead would like to trial a couple of them. the PR system (rally expires in x seconds, can’t place again until y.) might not work for Squad. A wave spawning system for RP’s, e.g. every 90-second rolling wave, the whole squad can spawn on RP, keeping them together. However, it doesn’t impact pacing, it would change squad movement. Incentives could be introduced to reduce spawn time, for example. (Community: Remember, nobody likes waiting.) Fuzzhead understands the limitations of rally points may have been implemented as temporary measures to adjust the pacing of rallies. Needs to be re-examined, as it feels outdated. Fuzzhead would really like to try some changes in testing, especially to see how it impacts pacing. It could add some depth, opens up more roles for people, and increases the importance of logistics. Game Mode Intent First flag is always neutral on Invasion. We know… it’s not ideal, may change. If you’re seeing back caps lost in other ways, it may be a bug -- tell us. =) Some Invasion flags had issues in the v9 -> v10 merge. Many issues (e.g., loss of flag lock) were caught, but some did get through, especially on older maps with more layers. They will get looked at though; we’ve learned from our mistakes there. Respawn resources have been tossed around as an idea, but generally seems pretty “gamey” and silly. It could have merit if it worked, though. (e.g., If a rally had no reloading capabilities, you’d need a supply truck with ammo, or more respawn, etc.) AAS isn’t necessarily the right mode for irregular forces, and we'd like to showcase them more/make them more fun. Q: What’s the motivation for game modes? We need more content! Is AAS supposed to be the primary, one-trick pony? Random AAS will likely be a topic for the next roundtable. AAS was the primary mode for PR, because it was easy to modify. It was a good start for Squad, but isn’t necessarily the “flagship.” Like Fortnite experimented with modes, one game mode may rise organically. The problem right now is the other game modes haven’t gotten as much polish, but that will be changing. Smaller, shorter seeding game modes to get people into servers might be an example. You might not want a two hour AAS session mid-week, so offering other options is important. Additionally, we've previewed the territory control mode, and briefly discussed the potential for Fog of War mechanics, especially in Random AAS. Crewman Kit Beef up the driver capabilities a bit, give them a periscope. Every APC, IFV, tank, and helicopter will have a Crewman kit requirement. As a squad leader, you may need to have a crewman, or it may be allowed to drive as a SL, work as “vehicle commander” setting points, etc. The first iteration of the Crewman Kit may not have any special toys, other than meeting the requirements for driving some vehicles. More abilities are still up for discussion. We’d really love to see more combined arms, especially when 50v50 platoon-scale combat is an option. Closing Thoughts A big thank you to everyone that took time to join us for the roundtable. We look forward to seeing you again after the next Recap! Your feedback is invaluable to us and we're looking forward to building a better Squad with your help! And yeah, we're working on improving the roundtable format too.
×