Mods and Modding
I'm thinking that perhaps Mods and Modding should be two seperate pages. Modding is creating mods, so that page should be about development, whereas the page Mods should be a list of mods available for the game... I'm just going to go ahead and make the switch, but by all means switch it back if you think it's a bad move.
What we need to work out...
- Where are the Game.AdviserSay values defined?
Anyone have any tips on modding PA on a Mac? Looks like the launch wrapper won't read a pre-extracted /data/ folder and a rar'd or compressed /data/ folder isn't correctly read by the launcher's extractor --184.108.40.206 09:47, 5 November 2012 (UTC)
I'm having the same problem. It'd be great if there was some feedback on this.--220.127.116.11 21:08, 14 November 2012 (UTC)
Organize Information Into Table?
The recent edits on this article have added many sections into the article (thus expanding the table of contents and adding unnecessary horizontal lines). It may be better to place all of the coding information into a table. It should display the information more cleanly, and remove the unwanted white-spacing created by the section headers. Thoughts? Please discuss.
- The format I chose was merely to apply a structure ready for code samples. Many functions will turn out to have more than one implementation, from previous API wikis I have produced in the past the best eventual course of action would to have each as a separate page entirely so browsing it made simpler. --- HughAJWood - MS SharePoint MCITP MCPD MCSE MCP & JS Evangelist @HughAJWood (Twitter) (talk) 09:58, 11 December 2013 (UTC)
- I have added my proposed layout to Objective.SetFlags(bool hideOnMap, bool hideOnTodoList), this gives a structure to the definition of all functions, I do think that these should be elevated to their own pages eventually for ease of navigation, however until complete it may be wise to keep in one page then move to seperate pages. Thoughts? --- HughAJWood - MS SharePoint MCITP MCPD MCSE MCP & JS Evangelist @HughAJWood (Twitter) (talk) 17:37, 11 December 2013 (UTC)
- Initially, I thought it would have been good to keep everything as organized and clean as possible to make for easy referencing on one page. However, if you feel there is enough information on each piece of code that merits its own page, then by all means go ahead with it. I can agree that the structure you presented on the "setflags" code would do good on a separate page. Thanks!
- -- RGeezy911 (Hello) 18:31, 11 December 2013 (UTC)
- I think by the time I have filled out code samples for each component then even the simple ones are just over a screen in size and merit a page. I will finish all the samples and then move them to separate pages. I was thinking about structuring modding into the 4 categories Graphical, Language, Grant and Scenario. The code samples can sit in a Game,Objective,Trigger structure under Scenario. The top level can house a simpler table design as per MSDN design lending to a clean structure that can support multiple code versions.--- HughAJWood - MS SharePoint MCITP MCPD MCSE MCP & JS Evangelist @HughAJWood (Twitter) (talk) 19:33, 11 December 2013 (UTC)
Is there anywhere I can go to get some real information on how to make a mod, like a tutorial or something? Listing a bunch of method names with vague descriptions of what they do isn't exactly a "How To"