Overhaul
Looks like this wiki has been neglected for quite a while. I'm going to be working on overhauling this wiki primarily targeting new players to the game. I am starting by updating the mech pages to contain useful information, then the maps, and setting the main sections to be: Mechs (current layout is confusing and bombards new users with mostly irrelevant information), Mechlab (a tutorial on how the mechlab works, includes Weapons, Equipment, Upgrades and Modules subcategories), Pilot Lab, Maps (isn't updated), Gameplay (the Mech Manual is salvageable) and Community Warfare (currently entirely missing). The site currently looks like it was something designed for closed beta users, but that time is long gone. It's often the first thing that new players search for when looking up the game now. Krivvan (talk) 10:10, 14 January 2015 (UTC)
- Dude, chill. Help is definitely appreciated, but there are other people here and you're making dramatic changes without discussion. Some of the stuff you mention here sounds good, like new info on maps, tutorials, etc. but the removal of the Template:Infobox BattleMech is really bad. Put it back. Also, if you're wondering why some mechs are missing, it's because I've been the only one adding mechs and I decided to add them as they become available for credits in the game, rather than MC. --Trifler500 (talk) 11:49, 14 January 2015 (UTC)
- I wasn't aware there was anyone left who edited this wiki or cared about it with the outdated info, missing information on quirks and CW, infoboxes that mess up on certain browsers covering the text and wrong information on mechs and maps. You can undo the changes if you wish, it'd be easier and less likely to step on toes if I started a new wiki anyways with a focus on gameplay info over lore and looking like a standard wiki. Krivvan (talk) 18:17, 14 January 2015 (UTC)
- @Trifler Krivvan has been working on some other community projects like the map API program, and any help here updating the place is welcomed. @Krivvan, I started this wiki back in close beta and I agree that it still looks like it. It still uses the old background and the color palette was sampled directly from the UI1.0 mechlab. Of course you can start a new wiki, but I gotta tell you from experience that trying to go it alone with a game that updates as often as MWO does is a huge time and effort drain. I think it would be better if you leveraged the work that's already been done and the few volunteers who do still contribute here to help you. The greatest resource of a wiki can have is people who are willing to put in the work to keep it updated. --AdamV2 (talk) 18:58, 14 January 2015 (UTC)
- No worries then. I've weighed adding quirks. So far, information on quirks seems like a futile effort since they're balancing them and thus they change every patch. Besides, they're easier to read within the game than most of the other stats. I'm not against adding them though. I just didn't see an effective way to maintain them. The main thing is there's no notification of quirk changes, so nobody would even know it needs to be updated, even if we have time. We definitely need help adding stuff. All I'm able to keep up with is adding mechs as they become available for credits. I put up the Operation Revival and Resistance pages, but I don't know how to make graphics like the person who made the Project Phoenix page did. I don't think simply deleting the Template:Infobox BattleMech is good though. Edit it or replace it with a new template with all the same info if you want, but simply deleting it removes a lot of good stuff. --Trifler500 (talk) 07:08, 15 January 2015 (UTC)
Map Hub and Map Pages
Hello, I intend to add pages for all the new maps and eventually update existing map pages. I started with HPG Manifold and will probably keep the same style for the remaining maps. In order for these sections to actually be useful for players, they will need an expanded strategy section for both solo and group play. I could use some help with the group strategy section as I mostly play solo. Once maps are more up to date, I will move on to whatever is most outdated. I'm not very familiar with wikitext but it seems simple enough. I'm good with graphics/photoshop and web languages (css/html/php/js) so if there are areas that need any of that, I can handle it. Currently I'd describe this wiki as "a lost cause" but if we can get it to "needs improvement", maybe people will be more willing to jump in and help. --K1ttykat (talk) 16:21, 21 February 2015 (UTC)
- Welcome and we appreciate the help! There are currently two template-related problems I don't know how to fix, since you mentioned you're good with web languages. Maybe you could figure out what's wrong with them:
- First, most of the 'mech pages list that the template has exceeded the maximum size, even though they're all the same size as always, and they seem to still be working. I don't know what's causing it.
- Second, a weird thing has started happening recently that was brought to my attention by the user RevancheRM. It appears that in some places on this wiki where the <references/> tag is used, it's automatically being turned into "UNIQ48f984eb77b76688-references-00000007-QINU?". It also displays that text on the page. You can see an example on the Command Console page. I can edit it to delete that weird text and type in a references tag and it displays fine in the preview, but it just changes into that weird text as soon as I save it. I checked in using a different browser to make sure it wasn't a browser problem and it happens in both Internet Explorer and Firefox. --Trifler500 (talk) 16:53, 21 February 2015 (UTC)
- UNIQ-QINU is a placeholder tag for when the parser gets confused, it seems to be from something going on with the semantic equipment template. I'd have to look around to see what happened but I removed the text at least. Because of the order in which it is parsed, there are a few situations where different tags are needed. UPDATE: I just wanted to make sure the previous version didn't work and it just did. A change to the extension or parser behind the scenes probably caused a problem and then it was fixed some time between now and when you tried to fix it. --K1ttykat (talk) 19:26, 21 February 2015 (UTC)
PQX생중계카지노福【ZQZ77.COM】바카라사이트
생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노생중계카지노づ바카라사이트づ카지노사이트づ온라인바카라づ온라인카지노づ아시안카지노