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 'wiki'.
Found 6 results
This forum thread documents the activities related Wiki Task #009 as listed on the Community portal. Read this post on how this task was created. You will find important information in that post - please read it before continuing here. Aim: Create external tool which extracts specific data from Squad's game files. See Wiki Task #008 on what data we are talking about. Integrate the tool in such way that its data output can be imported into the "source" from Wiki Task #008, quickly and easily with no or only little manual effort. Get official approval from the devs before starting on this task. Open points: Who will do this task? Volunteers? Action Plan: (will be added as needed) Assigned wiki editors: (will be added as needed) History: 2017-07-15: Idea was documented in this thread. 2017-06-24: Idea was proposed by Sneaky on Discord.
This forum thread documents the activities related Wiki Task #008 as listed on the Community portal. Recently, Sneaky and NoOriginality got into a discussion over at Discord #wiki. Two ideas came out of the discussion: Instead of maintaining numerical game values on the wiki pages manually (e.g. weapon statistics or ticket/score counts), we should store that data centrally in one file/place and use that central data to display it on the wiki pages with some automatic mechanism. This way we only have to maintain one source of data and all pages will automatically (magically!) be updated. This is particularly useful for translations, as values no longer would have to be updated separately on all translated pages. This idea has become Wiki Task #008 (see full list of all wiki tasks on the Community Portal). An additional idea came up: We should automatically pull as much of this game data/stats from Squad game files with some tool (aka "data mining") instead of manually deducing it in-game. This way we can quickly and accurately update the statistics and data on the wiki every time a new patch comes out. Of course, this idea goes well with the first idea and would be a natural second step. To deal with these two ideas one at a time, this second idea has become Wiki Task #009 - read more about it in this thread. Both ideas are not entirely new; we had internally discussed them with the devs in the past (they liked the idea!) and we considered it a future possiblity. Maybe now is the right time to start this little project. Organisating work on the wiki: As wiki editors we have several tools at our disposal to coordinate and communicate our work on the wiki. These tools are particularly necessary/useful for tasks that are complex, involve multiple people, affect many wiki pages or the fundamental structure of the wiki, or take considerable time to complete. The Community Portal is the number one hub for all editorial things. Start here. It has a list of tasks and to-dos and shows all communication channels we have available. It's a bit out of date, but we can use it more if wiki editors will use and follow it too. For complex tasks, it's useful to use the forum for documentation and coordination (this is why I created this thread here). We can describe what we aim to do and we can document and share important progress and insights here. We can also have complex discussions here which would get a total mess on Discord. The orginal poster just needs to moderate the discussions and keep the first post up-to-date with all relevant information. For complex tasks I also strongly recommend to write up the aim and action plan (and maybe an open point list). It helps the person doing the task to think everything through before he starts. If a team of people works on the task, having an aim and plan is a necessity to coordinate the work of each member. Also, all of this communicates the activities to all wiki editors and the community. Who knows, maybe someone will offer their expert help for a specific step. Aim: Describe what you want to achieve. Give a good and thorough description. Action plan: Think about all the things that need to be done, then bring it into a logical and chronological order. Make notes of what is important to remember when you are doing these steps. When you write the first draft of the action plan, it's ok if it's not 100% perfect and has missing steps or lacks details. You can add to the plan as you go along. In the early Wiki days, we started this Google document to list all the wiki pages and to coordinate and track progress. Initially, we used this document to complete the transfer of the text from the Squad User Manual to the wiki, but we can use this spreadsheet for other tasks and management, too. It's very useful to keep track and have an overview of what needs doing and what has been completed, page by page. We can add as many new columns to this spreadsheet as we need. We can also create additional Google documents if we need them (please let me add them, don't just share your own Google documents). Anyone can view the document. I will only give write permission to wiki editors assigned to specific tasks. Discord should be the main tool for direct communication and close cooordination. If we really do this task, we will probably kick it off with a voice meeting on Discord to discuss everything with the assigned wiki editors (as I did for Wiki Task #006 - sadly, this task was never completed). Recent changes is an excellet way to check what has happened on the wiki recently. Alternatively, you can also check the change history of an individual page (example: Community portal history). There is also a comparison function that lets you see the differences between the current page and older revisions - very useful! This shows you why it's so important and useful to always enter a "summary" when you do an edit of a page. We should use the wiki itself as much as possible for any of these tasks, too. MediaWiki provides useful tools. For example, you can mark a page as "stub" (and other categories) and it will be automatically be listed as a page that needs work done (see Wiki Maintenance and Stubs). This way we can also mark pages for editors to work on. We can add a description of what needs doing in the page itsef or the discussion page of the page. We can create additional "management and collaboration tools" if we need them. But for now, lets try to use the tools described above. Volunteers: But most importantly, for task this big, it needs someone (or multiple people) to take up the assignment and start working on it. I don't have the time to do neither of these two tasks, so unless someone from the community picks it up, it will not get done. Aim for Wiki Task #008: Create/add automatic mechanism to the wiki to achieve the following: Manage all numerical game values centrally in one place or file on the wiki ("the source"). Wiki pages pull data from the source in order to display it on a page. When we update the data in the source, all pages will automatically get updated. We no longer have to edit the pages individually to update the data on each page. We should try to use existing mechanism/scrips/wiki modules/wiki add-ons - no need to reinvent the wheel. We should keep in mind Wiki Task #009 as we want to integrate both together. Our solution has to work with our Gamepedia MediaWiki. We cannot install whatever modules or add-ons or scripts we want, we need to coordinate with Gamepedia staff what is available or what could be added. Open points: Who will do this task? Volunteers? Do we want to do this for numerical values only? We should list specific data examples and pages to see where we would apply this mechanism and what types of data are we talking about. Action Plan: Just as a suggestion and starting point for discussion, let me outline how we could approach this task. 1) Phase 1: Preparation 1.1) Research: How could it be done? How have other MediaWikis done it? Lets compile a list of what we can find on this. I can also talk to the Gamepedia staff to seek their advice; also, I am direct communication with all the other wiki admins at Gamepedia - I can also poke them. 1.2) Evaluation: Which of our wiki pages would we use this mechanism on (lets list them all up)? And what types of data would we use (lets list them all up)? 1.3) Design: Decide on how we implement it. Maybe it makes sense to use templates. 2) Phase 2: Implementation. 2.1) Do what is necessary to implement it. Probably test it first with a few test pages, then roll out for all relevant wiki pages (English pages first, translations later). 2.2) Maybe it will be necessary to standarising some of the wiki pages. We should probably making more use of templates, too. (See also Wiki Task #006: Weapon pages) 3) Phase 3: Wrap up 3.1) Documenting how wiki editors need to use this mechanism. Document the mechanism itself too, in case it needs maintenance. 3.2) Discuss with the devs a process by which they could provide us the latest data after a new patch has come out so we can quickly update the source. 3.3) Proceed with Wiki Task #009. Assigned wiki editors: (will be added once we have found volunteers) History: 2017-07-15: Idea was documented in this thread. 2017-06-24: Idea was proposed by Sneaky on Discord.
This forum thread coordinates activities related to the weapon pages on the Squad Wiki. This task is listed as Wiki Task #006 on the Community portal. A lot of the coordination and communication among the wiki editors happens on Discord (there is a dedicated wiki channel for text and voice) and the Community portal, so make sure to check those out too. However, a focused and structured discussion is probably done most effectively on the forums, hence the creation of this thread. More to follow shortly...
In order to more closely link the forum to the wiki and keep more community members informed (and involved), I will be posting Wiki related news and request in this forum thread here. You will also find a similar "news" section in the Community portal of the wiki. On the same wiki page, you also find a Wiki Task list. This list attempts to help coordinate and focus the attention to of the wiki editors on what needs to be worked on in the wiki. We need you! In case you thought the wiki is all done and finished, reconsider. Lots of content is still missing. Also, Squad, the game is changing and evolving. Without updating the info on the wiki, the wiki will soon be obsolete. After an initial boom of activities and contributions on the wiki after the first announcement back in May 2016, editing has dried up alomst compleletey. The wiki need your help, Squad community! Please remember, the wiki is for you, the users (and many of you have asked for a wiki). But the wiki also needs you, the users, to run it. It does not run itself or by only one person. It needs the community to support it fully, otherwise it will die. Hit that "edit" button on pages where you can make a contribution. Check out the wiki task list and see where you can help out. If you have questions or ideas or are unsure about something, send me a direct message on Discord. More news to follow soon...
Background You've read the official news: the official Squad wiki has arrived and Squad's PDF-based user manual will retire and transfer its content to the wiki. Because of this, there will be no more updates coming out for the user manual and version 1.1 will remain the last and final version of the user manual. In the transitionary period between now and until the wiki is firmly established, the manual and its translations will continue to fulfill their purpose of guiding new players into the game. The life of the manual has been eventful. Its creation started in July 2015 during the early days of the Closed Pre-Alpha. After first publication in September it has seen two updates for each following month. For the Steam Early Access the manual was completely reworked and re-published in December, followed by another update in February. The manual's forum thread has accummulated over 50,000 views and over 250 replies, the manual was translated into 7 languages and another 8 languages were being worked on. The translation team consisted of well over 30 people, both individuals and organized Squad communitites. I want to express my sincere gratitude to my dedicated translators - you did an amazing job and made a huge contribution to the worldwide Squad community - thank you. I do hope this is not a final goodbye but your contributions continue on the wiki and in other Squad community activities. Anyone interested in working on translations can do so on the wiki now. The wiki fully supports multiple languages. If you are interested, head over to the Translation portal to find out more. Right now though the focus will be on initial content creation in English. But once solid content is available on the wiki, translations will become a huge focus again. Now it's time to hand over the content of the user manual to the community. The outline and content of the manual will be a good starting point to populate the wiki. There is little point in having and maintaining both, a comprehensive wiki and an user manual. It would be hard to draw a dividing line between both and keeping them separate; overlap would invite contractions and create duplicated effort. Also it's too much trouble for the readers to go to two resources to find what they are looking for. Of course, an user manual has its advantages and we will have to see if we will overcome the challenges that a wiki and a community-driving editorial brings. First, we have to transfer and recreate the base content in the wiki. A huge undertaking which no indiviual can do alone - I am certainly not up to it. The community has to accept responsibility of the content and take action to make it happen. Secondly, when future Squad builds are released, content needs to be updated consistently across the entire wiki - no small task either. Of course, the wiki is much more than just the description of the basic gameplay. I am looking forward to seeing what the community will bring to the wiki. A wiki has a lot of strength and potential. To utlize that, the community has drive the wiki and make it an integral part and daily tool of itself. Task: Porting the manual to the wiki Everyone interested in contributing to the wiki, especially with the porting of the user manual to the wiki, go to the Community portal, you main starting point and information hub for all wiki editors. If you are new to a wiki, check out the Wiki Help pages. In order to collaborate on the porting of the manual, you will need the following data and information: The English user manual version 1.1 (PDF or OpenOffice document) All images used in the manual as JPEG files. Please rename the files appropriately before uploading them to the wiki. Also, feel free to create new images if you see it necessary, I just wanted to provide the entire content of the user manual that could be used as interim placeholders for the time being. Wiki Style Guide - the style guide contains only a few rules at the moment and is far from completion. Nevertheless, have a look. Also, as we go along with the wiki, we should add to the style guide in order to ensure all editors produce consistent work and we reduce unnecessary rework. And here are some of the steps and considerations relevant to the porting process: For almost all headlines and sections from the user manual, the corresponding wiki pages have already been created. The pages should have been marked as "Stubs". A page stays a "stub" until all work on it has been completely finished. If a page is missing, create it, but please make sure it does not already exist. When you create a new page, please check the Wiki Style Guide to make sure you comply to established conventions. Check for list of stubs or look at the complete list of all pages. Pick a page of your choice from that list and work on its completion. It doesn't matter with which page you start - start with those you fancy working on most. Focus on the manual's chapter 5 as this is the core part of the gameplay that really needs to move to the wiki. Some other bits and pieces of the manual can also be moved to the wiki but are less urgent, and some parts from the manual are not needed at all on the wiki. It's up for the community to decide what else is needed and what isn't. As a starting point you can first copy over the plain text from the manual to the corresponding wiki page (note: copy & paste from the OpenOffice document is easier than from the PDF). Don't take the content from the manual as set in stone. Feel free to improve it, split up content differently than in the manual, or completely rewrite it from scratch. Once the text is finalized, don't forget to add lots of cross-reference links to relevant wiki pages. Every time you mention an important gameplay term, you should link to its page on the wiki. Also add formatting, tables and images to finish off the page. At the end don't forget to proof read it for spelling, syntax, completeness and comprehensibility. Even if you feel you are not knowledgable enough about Squad to contribute to this process, you can still help. Just duplicate the manual to the wiki page is still better than having nothing on the wiki at all. On many of the pre-created pages you will find some hints given from me or other editors. These hints are called "WIKI_TASK" (you can also search the wiki for this keyword to find all wiki task descriptions). These descriptions are intended to make your life as editor easier. Please remove the WIKI_TASK from the page when the task is finished (but not beforehand!) or add more hints to the description for fellow editors. Also make use of the Discussion pages to coordinate and collaborate with other editors. The beauty of the wiki is its collaborative aspect - make use of it. Don't take anything on the wiki as set in stone. If you thing something is missing or off, click that "edit" button and change or create it. The wiki and its content is by you and for you. The wiki is completely new to your community. We have to learn how to use it and how to work together on it. Please help integrate the wiki to the community and make it work for all of us. Besides the porting of the manual to the wiki, there's plenty of other content that needs creating. Feel free to work on other pages than the manual port, too. If you are unsure or need help, check the communication tools for the wiki community and the Wiki Help for help. Any questions, thoughts or suggestions about porting the manual to the wiki? Post them in this thread. Lets get to it. See you on the wiki. Your daily edits will bring a smile to my face. Lets see who's able to beat me on WikiPoints first. P.S.: Many thanks to all those early helpers that have already started on the wiki over the last few weeks. Most notably ZiGreen, DoctorSnailer, ComedyInK, Switcher05 and SpamazoR. Tip: I strongly recommend the use of browser add-ons for advertisment blockers if you work on the wiki. Otherwise the ads will slow down your entire browser if you have multiple tabs open. For Firefox, I use Adblock Plus.
Hi Squaddies , Welcome to the wiki section "The Squad reference written and maintained by the players. Please feel free to contribute by creating new articles or expanding on existing ones" The Squad wiki Do you remember your first time with the game? Let's improve the community knowledge together Everybody can help the wiki to grow, to be simple and full of specific informations that only a wiki can have! Q: What is a Wiki? A: "A wiki is a website which allows collaborative modification of its content and structure directly from the web browser" - Wikipedia Q: How do I register an account? A: You can follow this link and register you account! Q: Can everybody contribute? A: Literally everybody can contribute, it's a wiki! Built for and by the players! Q: I have never edited a wiki page, how can I do that? A: Don't worry, there are plenty of tutorials on it around the web, starting from here http://squad.gamepedia.com/Wiki_Quick_Start Q: From where do I start to edit pages? A: Check out the Community portal on the Wiki http://squad.gamepedia.com/Squad_Wiki:Community_portal, there are wiki tasks waiting for you! Q: I really do need some help! A: Join us on Discord, in the #wiki channel and ask for help, don't be afraid! a wiki contributor, Doctor Snailer