Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by Usgu

  1. The Fandom journey continues. In 2020, a new joined platform will be created and all Gamepedia and Fandom wikis will be migrated over. Exciting times ahead. Read the full story here: https://community.fandom.com/wiki/User_blog:MisterWoodhouse/Our_first_update_on_the_new_platform
  2. On 12 December 2018 it was announced that Fandom, another popular wiki-site also known as Wikia, has bought Curse Media from its current owner Twitch. Curse Media owns Gamepedia, which is our host of the Squad Wiki. What does this mean for you? For the near future, nothing. Everything continues as usual. If you are a resident of the European Union and European Economic Area (EEA), the General Data Protection Regulation (GDPR) requires companies by law to ask for user consent before doing new stuff to your personal user data - in this case, handing your data and account over to Fandom and changing its use to their terms and conditions. You probably have already received an email or a pop-up on the Gamepedia websitse asking for your consent. If you give your consent, your data will be transfered to Fandom at some (still unknown) date and you can continue using Gamepedia as usual. If you do not give your consent, your user data and account will be deleted. You will have to create a new user. Your edits on the Squad Wiki will be attributed to "user deleted". If you live outside the EU, your personal user data will be moved to Fandom without asking you - because in your legal system there is no legal requirement to ask you for permission. What will happen in the long-term future to the Squad Wiki? Of course, it will continue to exist and prosper, but we don't know on which platform or under which conditions. No one knows today, even Gamepedia staff do not know. Fandom has 300,000 wikis, many of which overlap with Gamepedia’s 2,200 and there are plans for creating synergies. The first transfers of wikis from one site to another have already happened. But Gamepedia staff have assured us this will only happen after intensive discussion with the wiki community and the active wiki admins. The Gamepedia staff has always been very honest, kind and supportive and we can hope we will continue working with them. If all of this sounds familiar, it's probably because of recent memories when Twitch has bought Curse Media two years ago and you were asked to consent to the merging of your Twitch account with your Gamepedia account. Now, Twitch has sold Curse Media to Fandom. According to current information from Fandom, all your existing relationship with Twitch in connection with other Twitch Services are not impacted at all. If you want to know more about this: http://fandom.wikia.com/ https://en.wikipedia.org/wiki/Wikia Official statement and information by Curse Media http://community.wikia.com/wiki/User_blog:Brandon_Rhea/Fandom_and_Curse_Media_are_joining_forces https://kotaku.com/yesterday-just-two-years-after-twitch-acquired-curse-l-1831071841
  3. Devs Need Your Help! 4k in game screenshots

    The path to which screenshots are saved, has changed. This is the new path: %USERPROFILE%\AppData\Local\SquadGame\Saved\Screenshots\WindowsNoEditor Any moderator wants to update the first post with this new path?
  4. Yes, it's over. Took a bit longer than planed. Only the wiki search is broken right now, but Gamepedia is already working on a fix.
  5. The Squad Wiki will be read-only on Wednesday January 30th from 11am US Central Time until approx. 11pm. Gamepedia is migrating stuff over from Twitch/Amazon to Fandom.
  6. It's happening now. All users who have not given their consent, have been deleted and now look like e.g. "@DeletedUser481". There are lots of them. Fortunately, it's not too late to get your user back (however, this recovery process will not be available forever, do it as soon as possible). Here are the official instructions from Gamepedia: Any EU/EEA users who had not consented prior to these required GDPR activities may now reclaim their accounts: 1. Log out 2. Visit Gamepedia.com 3. Log in there 4. Use the rename credit here: https://www.gamepedia.com/account Your username will then trickle down to the wikis. User pages (owned by non-consenting users) and user profile fields (for non-consenting users) had to be erased to comply with GDPR (they cannot be recovered). Wiki points, contributions, and achievements are saved. If you still have issues after following those instructions, make a ticket by sending current username, old username, and account email to [email protected]
  7. Console Commands

  8. I have posted the following general steps on Discord before. These steps roughly outline how to implement Cargo to a new section of the wiki. Theoretically - we haven't actually done it ever before, so this is a first. I might also have missed a step or two, or got some order wrong, but I hope this gives a general idea of what needs doing. I'll repost them here for better and easier referencing. Decide on the data elements (and their data types) you want to store and present (this might include properties that are not necessarily displayed but also important) List all pages that use this data Decide which pages will "store" the data (usually those that have infoboxes and describe the item in question) and which pages will "display" the data (usually those with overview/summary tables of that data) Decide on the specific layout/presentation of the display tables that shows the data (there might be different scenarioes/presentations/layouts for the different target pages/purposes) Create the templates for the infoboxes; these infoboxes are used for data entry; these templates use Cargo scripts for storing the data Create one Lua script to display the Cargo data; using parameter this Lua script can be made to adjust the layout/presentation of its output - this way, we only need one Lua script instead of multiples Integrate all above in the existing wiki pages Enter all the data using the infoboxes on corresponding wiki pages (if we modifiy existing infobox templates, we might already have the data on the wiki pages)
  9. 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.
  10. Your continuous support is highly valued, @Nightstalker21.
  11. Guide: Map Versions

    Sweet! Good job. I know, the map pages on the wiki are terrible out of date. In fact, this is one of the primary areas we are working on. Maybe we could collaborate on this. Check out: https://squad.gamepedia.com/WP_-_Introduce_Cargo_to_Maps Still work-in-progress, but hopefully heading in the right direction. The more help we get, the better.
  12. New Website Launch

    Bloody browsers.
  13. New Website Launch

    Sweet! Looks ace! No ping on Discord on this? Seems news-worthy = ping-worthy. By the way, the links posted on the Official and Modding Discords to the current Wrench are broken. ^ @Gatzby I love the integration with the Squad Wiki! Makes me super happy.
  14. We are making some progress. Check out: https://squad.gamepedia.com/Learning_Cargo https://squad.gamepedia.com/WP_-_Introduce_Cargo_to_Maps
  15. Thanks for the feedback, guys.
  16. We will be redesigning all the map pages on the Squad Wiki and also make them database-driven using Cargo and Lua scripts. We want to know from you if, and why, the "respawn yes/no" for vehicle assets is important or not. You can also look at one example map: Belaya If you want to help us with the layout and design of the new pages, go to the Wiki Map design contest.
  17. The closed pre-alpha is on, guys. The official email with your Commander keys provides the link to the following Bug report form - a Google form: https://docs.google.com/forms/d/18F-BRzssPiospA_Ymq_iyLajBPlniHJeyx-kwRRJc50/viewform?c=0&w=1 Please report ALL bugs through that form, do not post them on the forum. The form looks like this. Make sure you enter all the mandatory information, otherwise it will not let you submit. Please make a realistic and objective assessment of the actual severity of the bug. You might ask, "Where can I find out about the build number?" Check the bottom, right-hand corner on the main screen of Squad. There you find the current build number. For example, we started into the first Commander weekend with build "dev-1566-4.8.0-SHIPPING". For the bug report it is enough to use the 4 digit number, for example 1566. The following weekends had the build numbers 1710 and 1776. (click image to enlarge) After submission, you'll get the following confirmation. Suggestions are posted via another form here: https://docs.google.com/forms/d/1MF-2RWV67KgmyBbOpvLpjsTb8Xlj32d9Kd0SvZxD4uk/viewform?c=0&w=1 Please note, this applies for the closed pre-alpha. We will see what Offworld does when we get to the closed alpha. Admins/moderators, please stick this thread. ------ old posts starts here - please ignore ------ Question: Once we are into the closed pre alpha, how should we report bugs to the devs? Here my ideas, thoughts and questions: Just create a new thread in the "feedback" forum? I didn't see a bug tracking database or something anywhere around.Should we spell the title in a specific way? I saw someone using stuff like "[bug][xxx]xxxx". I think we should do something like this.However, it must be easy to search for all bugs in the forum with one search agreed term, hence the title should contain a search term we can actually search for. For example searching for "[bug]" or "Bug" does not work, so it's no good. Maybe something like "Bug_Report: xxxx" works better.Also, we should put a useful description in the title, so it is easy to find threads that might have already reported the bug I wanted to report myself.The title must include the build version of Squad. Bugs might be gone or only exist in certain builds, hence the version number is very important. It could be at the beginning of the title, like in the PR bug forum.Will the devs (or moderators) provide a "known bug list" / Bug Index? (maybe in a locked and moderated thread in the forum?)Such a list would be useful and serve as an index, so we don't report the same bugs over and over.They could also put next to each line some sort of status to say if it is fixed already (and whether it will be available with the next build).Maybe we can also put a link to the first thread that reported the bug, so guys can read up on the detailed description to check if it is the same bug they were about to report.We should have unqiue numbers in front of every bug, like an unique identifier. Then it is easy to refer to a bug via its number. This number could just be an incremented number.The bugs could also be grouped under sections in a logical way, so similar bugs are grouped together.What essential information (besides a good description and maybe screenshots) should we provide? Is our system spec necessary/useful?We could use a template for a new bug report post, like PR did (see here).I think we need a sticky thread that explains how to report bugs, otherwise too many people do it in too many different and multiple ways (of course, we can't prevent that entirely (unless we use a database and enforce strict data entry).What we also can do while playing (once we ARE playing): chat to one of the devs ingame via text chat, if they are on the same server. If they are even in your squad, talk directly to them. Check with them if the bug you are seeing is new or not. If new, report it properly.I think this is a really important question, otherwise it will create too much effort for us and the devs (we would waste time reporting bugs over and over again, in ways that is not helping to fix the bug). If the devs can't do a bug index, maybe the moderators can. I think this would be really really helpful. I would also volunteer for this job. Let the community help make this pre-alpha a sucess. Maybe we can even maintain this index as the main starting point for the devs to work systematically through the bugs? By the way, if the devs and moderators need any other specific help during the pre-alpha, call out, we are ready to serve. Right, guys? MikeDude pointed out how PR is doing it (thanks, mate). Check out the bug forum of PR here and the bug forum procedure here. Has my question been covered elsewhere? I didn't find anything about it (Sir, yes, Sir, I did search for it in the forum). The forum rules don't say anything about bug reports either (maybe they should?). Edit 16.07.15, 1st: If I now search for "bug_report", it finds my thread. Good. Edit 16.07.15, 2nd: Refined some of my words and ideas. Edit 17.07.15, 1st: Added ideas by MikeDude (post here) - thanks, mate. Edit 17.07.15, 2nd: Check out what Lito said about bug tracking in a stream here. Edit 24.07.15: Added the final and official info on how to report bugs in the OP. Edit 28.07.15: Added screenshots of the Google forms and some hints on how to fill them out.
  18. Scoreboard - what does it mean

    Have a look at this, @GatorC210: https://squad.gamepedia.com/Score#Scoreboard_during_the_match
  19. We now have both Cargo and Scribunto enabled for the Squad Wiki. I have started experimenting with both of them. Check out our Cargo and Scribunto learning pages. I'll post another status update once I have more progress. We'll try to apply Cargo and Scribunto to the Maps pages first and see how this goes.
  20. July 2018 Recap

    Sweet. Cannot wait for v12.
  21. I'd like to give specific examples of what we are trying to achieve. Below are types of data we want to export from Squad's SDK and then import to the wiki and use it on the following pages/tables/data. Looking at these complex data types and our many tables and infoboxes, I am afraid this will become fairly complicated, so choosing the right tool to do the job is important. I am not sure if Cargo would be up for the job or we need something more powerful like Scribunto. Map data and images Map hi-res images with grids plus showing each layout (with flags and flag names; maybe also with vehicle spawns for BOTH teams) for each game mode, list factions per layout, list of assets per layout, list of flag names per layout, starting tickets for each team per layout). Example: https://squad.gamepedia.com/Gorodok Plenty more: https://squad.gamepedia.com/Maps See also https://squad.gamepedia.com/WP_-_Helpful_info_for_server_admins#Idea_1:_maps_overview_for_map_rotation Vehicle stats List of all vehicles, ideally which faction are using them. Example: https://squad.gamepedia.com/Vehicles Respawn timer, number of passengers, ticket costs, supply capacity, in the future: crewkit required "yes/no"). Example: https://squad.gamepedia.com/Category:Vehicle_infosheets Example: https://squad.gamepedia.com/Tickets#Assets_ticket_costs Weapon stats List of all weapons and their correct names. Example: https://squad.gamepedia.com/Weapons Which weapon is used by which faction and which kit. Not sure if that is easily possible to extract or even automatically generate on the wiki. Example: https://squad.gamepedia.com/British_Army#Kits_and_equipment Weapon magazine capacity. Example: https://squad.gamepedia.com/AK-74M. Plenty of weapons https://squad.gamepedia.com/Category:Weapons. Weapon magazine count and equipment count (e.g. bandages) per kit per faction. Example: https://squad.gamepedia.com/British_Army#Kits_and_equipment Weapon caliber for all weapons. Example: https://squad.gamepedia.com/AK-74M Deployable stats Constructions points for deployables. Example: https://squad.gamepedia.com/Sandbags. Plenty more: https://squad.gamepedia.com/Category:Deployables Kit stats Kit restriction per faction. Not sure if that is easily possible to extract or even automatically generate on the wiki. Example: https://squad.gamepedia.com/Kit_Role_Selection#Faction-based_kit_restrictions Game modes/general stats General ticket costs. Example: https://squad.gamepedia.com/Tickets#Common_ticket_costs Game mode specific ticket costs. Not sure if that is easily possible to extract or even automatically generate on the wiki. Example: https://squad.gamepedia.com/Advance_and_Secure#Mechanics Score. Example: https://squad.gamepedia.com/Score
  22. Also, very cool: http://en.gametactic.org/squad Ideally, we have one tool that could do it all (Map Viewer and interactive Tactical Board).
  23. 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.
  24. There is an amazing example of what has been achieved in PR: https://tournament.realitymod.com/mapviewer/ Everything generated automatically from the gamefiles and made available online. Magic! The original PR post about the mapviewer: https://www.realitymod.com/forum/showthread.php?t=139823 And the sources are here: https://github.com/realitymod/PRGallery
  25. I played it quite a bit, during Early Access and now since the release. It is as good as it promises to be. There could not be a better Descent successor. Multiplayer is also a lot of fun. Added link to Reddit AMA.