Talk:Advanced Warfare Center (LW2)
Some of the perks Info fields seem to be from LW1. For example, Kill Zone refers to Squadsight and Long Watch. Is this a Wiki issue or is there an actual copy/paste issue in LW2 itself? --Yenreb (talk) 03:47, 11 February 2017 (UTC)
- The Info was copied straight out of the LW2 Localization files. THe Info is the text you see when you click on the yellow info button ingame. --Mavoc (talk) 05:37, 14 February 2017 (UTC)
Many perks are restricted by class or by other perks, as configured in a file listed on this thread (http://www.pavonisinteractive.com/phpBB3/viewtopic.php?p=32721#p32721). I'd be happy to transcribe/provide this data but I'm not sure the best way to format it. Maybe a table listing which ranks the perk can appear as (rather than listing the perk in two or three columns) and how they're restricted? --Yenreb (talk) 18:37, 13 February 2017 (UTC)
- Version 1.2 is going to do quite a bit of revamping of that system by removing the class restrictions and only using other perks as restrictions. It would be best to wait to see what those changes look like. --Mavoc (talk) 05:37, 14 February 2017 (UTC)
- I started working working on a (Python) parser that will read the config files and be able to spit-out "data" templates (templates whose sole purpose will be to hold the related data for a thingy) and/or JSON, which could then be uploaded to the wiki. Then it's just a matter of adding missing information. More info here. Please, please chime-in with your two cents if I've missed something. Also knowing exactly which file holds what data would be handy. Some of it is strewn all over. (I'll put it on GitHub once I have something that actually works to some degree. :p )
- Bad news: The entire thing is in limbo until Joshua gets back to me about getting access to the site's CSS (that'll be necessary to build templates that actually display the data without pulling all of my hair out, and/or any poor sod who helps me doing the same) and whether or not he'll install Scribunto, which is definitely the preferred solution since parser functions are confusing, and a disaster in terms of syntax.
- Good news: Outputting the data is the easy part, it's parsing that is the hard part. So I can keep working on the hard part in the meantime.
- Anyway, point is, I'm hoping to have a solution for the "where to put the data" issue soon(ish). Gotta study for a C++ midterm though so might not make much progress this week. --Tvol (talk) 09:48, 26 February 2017 (UTC)