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 'modding 2.0'.

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 2 results

  1. Modding 2.0, Update #2

    Hey Squaddies! It’s time for another update on Modding 2.0! (You can find the last one here if you missed it.) If all goes well, the next update will be installed via Steam. Seeing as a lot of development has happened since our last post, let’s hear from Zak Strange, modding developer extraordinaire. ENGINE UPGRADE As you guys heard in the Next Phase article, Squad has been undergoing a massive engine upgrade upgrading 5 versions (Almost 2 years of engine revisions! Hello UE 4.21!). This effects modding massively, as a few major engines changes occurred requiring the changes to the way we download files from Steam. PAK files, the basic format for modding files, had to be completely rewritten for the mod cooking process. Mods from engine version 4.16 were completely broken by the update and can not be used in 4.21. Because of that, we had to prepare an additional fix that stops old mods from being loaded anymore. All of these issues, including some we’re not quite ready to reveal yet, turned this into a much larger project than we anticipated — there has been a TON of required tweaking and modifying a to the Modding 2.0 code to make it compliant with the updated engine. COOKING MODS (AGAIN) Cooking is the process of taking your modification content in Editor and turning it into a format that we can load in the version of the game that you load on Steam. With 4.21 (and just because it needed to be) the cooking process for mods was completely redone. With the rewrite came a few things: PAK files are all now HASH’d so you can’t join a server with a different version of the mod than the server is running. Because of the way mods are distributed, there can be issues Steam pushing patches, and running a different version of the mod than the server is running can easily cause crashes. Not only that, but PAK files are also now all compressed! We turned this on for one version of the SDK, and it seemed to work well with no issues. (Besides the cooking process taking longer.) Testing shows that most mods are 40-60% smaller with compression implemented. Another change is that mods don’t require versions depending on the platform configuration anymore. In layman’s terms, Windows and WindowsServer are the now the same thing from the mod’s perspective, so you will only have one set of PAK files instead of two. Unless… Mods can now be cooked for Linux as well. Although there is some additional configuration required, this is very easy for modders to set up on their development PCs. Pre-Cook, we check if the Cross-Compile toolchain is installed and if it is we can cook for Linux as well. THREADING Sometime in the middle of Modding 2.0 development, I realized that it would make much more sense if all of the modding operations happened alongside the game on another thread. So, I went about doing just that. With the threading came the (much needed) rewrite of the uploader and the downloader. The Steam Uploader is way better now; no longer will you get an “Unknown error has occurred.” We have a new uploading process where we are able to get back much better debug info than before. The whole Editor also does not “hang” when you are uploading to the Steam Workshop anymore! Additionally, the Downloader can now be invoked at any time during the game process with minimal impact on performance — all downloading work is done on this thread which then sends a notification back to the main thread once the mod is ready to use. The main thread will then do one small operation to refresh the map list for one frame. All of this threading work was done to make Modding 2.0 integrate seamlessly into Squad with minimal impact on the player experience. QUALITY OF LIFE We’ve been listening to your feedback and we know that there are a few things you want exposed to make your modding lives easier. With the release of the Alpha 13 SDK, we have some things coming for you. SteamID exposure BanPlayer and KickPlayer function exposed Setup the SQProjectileSpawner with an automated weapon blueprint, interfaces, customizable collision volumes, and various settings to allow mortar fire, arcing pre-set animated turrets, seek and destroy turrets, ammo control and line of sight control. Exposed Healing function and Health SQCameraManager Boolean variable added for ignoring the map start camera Added IsReloading to WeaponAnimInstance for possible use in modding Added bIsWeaponFiring to weapon anim instance for possible use in modding Special thanks to Renn and KaB for implementing these changes. They’ve been a huge help in getting Modding 2.0 built! SIGNOFF Thanks, Zak! Still looking for more information on Modding 2.0? Don’t forget to check out the Modding 2.0 Q&A we did a few months back. Until next time, we’ll see you on the custom server list.
  2. Modding 2.0 Q&A

    Hey soldiers! We had a hot minute to sit down with Modding developer Zak “StrangeZak” Strange and get some of your Squad SDK and Modding 2.0 questions answered. With features like in-game downloading, smaller file sizes, and self-updating, it’s sure to see some of your favorite mods popping up on even more servers. Let’s jump right in! MODDING 2.0 Q&A Romagnolo: From a player’s perspective, what are the necessary steps to join a server with a custom map? Does it download in-game or do I have to be sent somewhere else to download the map? Is it planned to be all automated? Thanks and keep it up! StrangeZak: With Modding 2.0, all mods download 100% in-game now. There’s no reason to go into the Steam client, find the mod in the Workshop, then download the mod, *then* find a server anymore. When you click on a Modded Server a box will pop up (if you don’t have the mod installed) that will provide a brief summary of the mod, its rating on Steam, and then a prompt to begin downloading. Once all mods are downloaded, you will then join the server queue. Anonymous: What limits are there to downloading a mod on server join? (Layers only? Up to maps using base assets? Or including total conversions even?) StrangeZak: There are no limits at the moment. Any mod can be downloaded in-game. A curious bloke: Would you be willing to partner with modders in order to bring content like maps, assets, and fractions to Squad quicker? StrangeZak: We’ve already done a bit of that and, of course, we want to do more. For example, look at Skorpo, Al Basrah, Assi’s scope, Axton’s grass shaders, and others. There’s some amazing talent in the modding community and we’d love to continue supporting it. Kiefer: Are you seeing results on the efforts to allow in-game downloads of map layers/mods? Will this allow for automatic downloads of required mods on server join (or per map change)? StrangeZak: Yep! Fortunately, things on all fronts are working well. Players will be able to download modifications 100% in-game now and you will not need to restart the client when the mod is downloaded. Kiefer: How will this download system interact with Steam Workshop mods/subscriptions? StrangeZak: When you start a mod download in-game (after accepting the prompt, of course!), it will do two things: First, it will subscribe you to the mod so you don’t miss out on future updates. Second, it will instantly start the download via Steam instead of waiting for another app to finish, which is Steam’s usual behavior. After you launch the game, it will now check for mod updates so you’re always good to go — something that doesn’t happen via the Workshop method previously employed. If any mod is out of date, the client will then update it for you, and you can get back to gaming. DanielNL: Why does Epic Games have to analyze every new Squad SDK version before it can be released to the public? StrangeZak: First and foremost, they just aren’t going to distribute something they aren’t sure that works. The engine is their baby, after all. Next up, they also need chunk out the 90gb+ SDK out to their CDN — there’s a lot of people downloading the updates! Ultimately, they’re responsible for making sure the content is okay to distribute and then doing so, and that presents its own challenges. Colsey: Will audio mods be able to be implemented without requiring the server/everyone to be running the mod at the same time? Will overrides be doable? As in, replacing an existing audio asset with a new one while sharing the same name? StrangeZak: Unfortunately, overrides will not be possible in modding 2.0. I’ve looked into them, but they would just extend modding 2.0’s development lifecycle to take much longer. Something to investigate in the future. (No no, not three weeks — go enjoy your holidays.) (B) Antol: Will Modding 2.0 bring cross-modding to Squad? For example, will it be possible to run a few different mods at one time? If not, are there plans for that? StrangeZak: This is already possible, but it does require you to have the source to the mod that you will reference. There’s not really a better we can do this right now since there’s no way to reference an already PAK’d modification. Slor: Will Modding 2.0 expose more things to modders? For example: Camera, projectile trace, health, etc. StrangeZak: Isn’t this all already exposed? Think we had to modify all of that stuff with SquadBR and it worked fine. (Editor’s note: Let us know if you’ve found a bug!) granQ: Will the content for maps be “frozen” (considering paths) now and available for our custom maps or should copy them to our own maps? What is the recommendation? StrangeZak: Content on Squad is never frozen, especially with the effort of pushing for 1.0 launch next year. Lots and lots of stuff will be changing over the next year. My recommendation is that you always copy the content to your own mod to keep it safe. Backups are always your friend! ArminStudios: Would it be similar to joining a Garry’s Mod server, as an example? What I mean in the sense is that instead of having to download the mods prior to joining a server, you’ll be able to join normally, but you’ll be downloading the mod in the process. Is that going to be the case? StrangeZak: We tried doing this method, where you only need the mod downloaded that’s running on the server. Unfortunately, it just did not work with how Squad switches maps. There’s no actual disconnect where you don’t have a map loaded, and we would need that to download and mount a mod before you load into the next map. The options were players would have to sit through the longer loading screen every time, or will the game remembers and keeps the servers mods installed to the client, so only the initial connection is the longer wait. Mods are downloaded once, you will not need to redownload all mods everytime you connect to the server. Also, connection times aren’t nearly as long with Modding 2.0 as mod size has decreased significantly. ArminStudios: Would there be a message that states this to a player wishing to join a modded server, informing them with details of what to expect? StrangeZak: Yep, we don’t auto-download it, per se. You still need to accept the prompt that shows you all the details on the mod, which provides the summary from their workshop page, the rating, a screenshot, and the mod name. Stanley / [FLV] BlackGaming [GER]: Is it easier to modding in 2.0 for newbies? StrangeZak: Not really, not much has changed from the modders side. (Editor’s Note: There are some really great resources on the wiki, as well as the Modding Discord server though. We all start somewhere!) Beefie: Will whitelisted servers make it into 2.0? Also, will players be able to join servers and download the mods without having to be subscribed to the mod? StrangeZak: Yep, we will be providing some sort of an approval process for mods that wish to be whitelisted. We’re still working out the details and requirements, which may vary from project to project. We store all these mods on our “master server” and, once approved, your mod will instantly be moved into the whitelisted section of the server browser with no work from you needed. We’re looking forward to seeing more mods getting some playtime. Beefie: Will blueprint exposal continue to be done by request? Or will that become a thing of the past with modding 2.0? StrangeZak: Yep, we can do another round of requests before Modding 2.0 is released. Beefie: Will mods continue to get exposal through The Wrench? What about players who do not read The Wrench? StrangeZak: Yes, of course. =) (Editor’s Note: You’ll have to pry The Wrench from my cold, dead hands! We love modders. Getting more content into Steam is an option too!) Reptio: If a gameplay mechanic, such as dragging, was to be properly enough coded in as a mod would there be a possibility of it making it into the game? Or would the accepted mods still stick to being maps and factions, etc? StrangeZak: Honestly, probably not. Almost all of the major mechanics in Squad right now are written in C++ for performance reasons, and with Modding you only get Blueprint access. (For obvious reasons). Reptio: Will it be possible to mod in completely new animations from scratch? StrangeZak: This is already possible! Check out the Canadian Forces model; they just use our rig and skeleton (I think), and modeled a new soldier! And there you have it, Squaddies. We’re sending Zak off for some beauty sleep now — there’s a lot to do in the new year! A huge thank you to everyone who submitted a question. None of this would be possible without you and the stellar Squad modding community! OFFWORLD OUT.