StrategyWiki talk:Achievements project

Achievement progress
I recently created the "Portal cameras" template for Portal, as you work towards the achievement in quantifiable steps throughout the game. I just thought; is this applicable to other games, and if so, why isn't it a standard template? I propose we create a "Achievement progress" template based off it, and use that instead. -- 08:39, 14 October 2007 (CDT)
 * I've gone ahead and made changes, but I decided to just add parameters to achievement instead of creating a new template. The changes are on its documentation page. -- 12:22, 17 October 2007 (CDT)

Template without gamerscore
Some steam games (audiosurf, PAA) have achievements without gamerscore and 1 steam game (TF2) has some XBLA achievements and some plain ones. Could we get an achievement template without the gamerscore column? Kadir 03:20, 23 June 2008 (CDT)
 * What's PAA? If they don't give points, what do they give? I don't think the  symbol is that specific that it can't be used for other systems, but we could potentially create our own "achievement score" image (anyone feel like taking that one?) -- Prod (Talk) 00:48, 24 June 2008 (CDT)
 * I've added a nog parameter to Achievements Header, which (when passed a non-empty value such as "1") will remove the column. --DrBob (talk) 16:05, 25 June 2008 (CDT)
 * Can't actually remember what PAA was, but it's probably a game. Steam achievements don't give anything, they're just there. Thanks for the nog parameter! Kadir 20:46, 25 June 2008 (CDT)
 * PAA = Penny Arcade Adventures. GarrettTalk 21:01, 25 June 2008 (CDT)

Achievements table, image categorization
Hi, I changed the image and description columns on the achievement tables to unsortable, since pictures don't sort and sorting by description probably won't do anything helpful. I just saw on the main page that achievement images are to only get the Achievement images category, but why is this? If they're associated with a specific game, why wouldn't they be in that game's image category as well? I think I've actually added guide-specific categories to achievement images before, so I'll have to dig around and find them if they need to be changed back. - najzere T 08:17, 14 March 2009 (UTC)
 * Guide-specific sounds reasonable to me. -- Prod (Talk) 20:44, 14 March 2009 (UTC)

Trophy images category
Should the project page be updated to include the Trophy images category? Currently it says only Achievement images category should be used, and I'm unclear on whether that's just because it was written without trophy images in mind, or if trophy images were intended to be included in the broader Achievement images category. — najzere T 18:34, 15 August 2009 (UTC)
 * Trophy's are exclusive to the PS3 right? I think a separate category is better, because it's more specific. Or rather, it's more exclusive. I know this article was written prior to or during the release of trophies. Most likely details were excluded because not enough information was known at the time. Wikipedia lists that trophies were released in July 2008, so perhaps there was a huge time lapse (the project was started in April 2007). -- 23:21, 15 August 2009 (UTC)

ToC naming
Are PlayStation trophies titled "Trophy" or "trophy" in games? On ToCs right now the standard is to name pages with achievements and trophies as "Achievements and Trophies", but if trophy isn't capitalized, then it's against our page naming conventions ("Achievements and trophies" would be more appropriate). — najzere T 05:53, 30 August 2009 (UTC)
 * It looks like you are correct; The official documentation always refers to it in lowercase unless it is part of the name of a trademark or menu option. Unless someone comes along with a counter-argument I guess I will get onto renaming these at some point. GarrettTalk 20:37, 30 August 2009 (UTC)

Achievement template lite
Apprentice Fortune Hunter Apprentice Fortune Hunter I'd like to use the achievement progress function of the achievement template, but the sidebars are too big. Does anyone know if a lot of games could use a pared down version of the template? The page in question was Uncharted 2 - A Rock and a Hard Place. The three templates were already causing whitespace on my screen (1440px), and I still had to add two more. It's made even harder that the template only floats right, so you can't move it around at all if it would look better on the left. On the right is a mock up of a "progress achievement" template, or at least the parts of the normal template that I want to use. Could more games use a similar, smaller style template? I don't want to make a whole other template for just one game, but if this is common, it might make sense to. Or make the existing template more customizable. — najzere T 06:56, 19 October 2009 (UTC)


 * I've updated the main template to allow float/width parameters (after testing it on my wiki.) I still think the template is on the large side, since it tries fitting a rounded rectangle around a rectangle, as in Portal/Chamber 04.  For the game in question, I don't recommend placing all three achievements in separate boxes, but rather show all three treasures in a single box; it's compact and probably would have the same effect.
 * I actually prefer it without the option to float. Images go left/right just for the sake of layout.  I think having it always show up on one side in a consistent location across guides is helpful.  What is the purpose of the width parameter?  If this is just to save whitespace on some pages, I don't think it's worth breaking from current ad-hoc sizing standards. -- Prod (Talk) 05:41, 21 October 2009 (UTC)
 * Sure, let's standardize it to the right. If actual issues arise with its placement we can change it later. The optional width parameter helps standardize the placement of the achievement image to the left side of the title/words, like the default image shown in the example at the start of this discussion, it could also be useful for adjusting white space. I have never seen the achievement template used next to itself multiple times (see the addition above), but I like how it looks. I don't think we need to modify the template to allow for multiple achievements within one box. Also, if there is a width parameter, there should also be a font size parameter to help scale things. -- 06:13, 21 October 2009 (UTC)
 * Just realized that this has come up before. As far as the specific guide goes, I like Sigma's idea to consolidate all the treasures from one page into a single achievement template (not multiple achievements in one template mind you, just all the treasures on the page building up to the achievement), and I think I'll start incorporating that. The template is distinctive enough as it is that consistent placement on the right doesn't seem very important to me. I already have enough of a struggle with control selector only being on the right; I'm afraid the whole site's becoming lopsided. :P The template is unnecessarily large due to the rounded edges, so maybe we could scale back the radius a bit. The biggest offender to my mind is the huge "Achievement" title, which seems redundant and takes up a lot of room. Also, it has nothing to do with PS3-only games (I believe an option to switch to PlayStation black has come up before as well). — najzere T 10:47, 21 October 2009 (UTC)
 * So add a ps3 parameter that when filled changed the color scheme and make the font size adjustable (see the simple change I made to the 2nd use of Achievement above). The rounded edges only add about 60 pixels. I don't have a problem with it being able to float left, but we can get around that. By "consolidate all the treasures from one page into a single achievement template" do you mean just use the progress bar but with a number instead of a percent? -- 03:07, 22 October 2009 (UTC)
 * Naw, I think the terminology is getting mixed up. In Uncharted 2 you earn a trophy (PS3 object) after collecting so many treasures (in-game object). I was just saying that instead of making separate achievement templates each time you find a treasure, you could use just one that increments the progress bar by all treasures on the page. I've since scrapped this idea, as they're still too big for the times when two templates will be on the page. If I include any indicator (barring a slimmer template), I'll just come up with a guide-specific one. As far as the ps3 parameter, it would be nice, although I'm not sure what the font size would be for. If it was meant for the "Achievement" title, I would rather get rid of it all together as it's redundant. – najzere T 06:55, 22 October 2009 (UTC)

Here's a mockup for switching out system-specific colors: http://img188.imageshack.us/img188/3523/templatewj.png. Obviously the colors aren't exact, but you get the idea. The only changes to the layout I made were to get rid of the "Achievement" title and move the achievement name to the top of the template. In this example, it's using everything but the progress bar, but if you omitted things like the achievement image or gamerscore/trophy, it would become pretty thin. I still don't see why we'd want to limit our layout options by not including float parameters. — najzere T 20:43, 27 November 2009 (UTC)

Achievement/trophy page standardization
Is it better to have a standard way to present achievement/trophy info on these pages, or just leave it up to individual editors as long as they're using the correct templates? I like to split secret and DLC achievements/trophies from the main list and put them under separate headings, but I've also seen them mixed in with the "normal" ones in a single table. We don't currently do this, but as seen on other sites (example; click "Show secret details" link), there is sometimes special display considerations for secret/hidden achievements/trophies. If they were in a separate table we might have some options in that regard. On the project page it says to split the table to different categories, but it isn't very specific.

Another part of the pages that doesn't have a consistent representation is the intro line about how many achievements/trophies there are and what they're worth. That sort of thing might be able to be templated as it's always the same (X achievements worth ), though a simple guideline might be more appropriate. The project page gives a general guideline now, but it doesn't give any formatting rules and I've seen the number of achievements bolded, the system name linked, etc. Anyway, if anyone thinks the uniformity should be nailed down a little tighter, these are the major areas of concern that I've come across. — najzere T 23:20, 8 December 2009 (UTC)
 * In the vein of doing something special for secret achievements/trophies, I made a mockup of a possible hide/unhide toggle for them: test.html (mediafire d/l). It works by putting a class on the row with the secret achievement. The JavaScript goes through the page and turns the first three cells in rows with this class into hide mode. The user clicks the row to show the actual achievement/trophy image, name and description. It needs error-trapping for a row with no image and changes to direct clicks on the image to the image page, but it seems to work all right besides that. Anyway, it's just an example of how we could do something special for hidden ones, to keep in line with how various other sites do it and how it's displayed on the actual system before you've gotten the achievement/trophy. — najzere T 00:26, 11 December 2009 (UTC)
 * I agree that normal, secret, and DLC should be split into separate sections. People shouldn't be wondering why they don't see certain achievements in their game when they see it on the page.  They can also jump to the specific section for the DLC they may have newly downloaded.  I don't think there's any real benefit of templating/standardizing the intro line.  As long as it makes mention of the most important information (# of achievements/trophies, total G, etc.), I don't think there's much benefit.  Also, if we split the secret achievements off into a separate section, people can easily avoid reading it.  I don't feel the hiding functionality is necessary. -- Prod (Talk) 04:26, 11 December 2009 (UTC)
 * Sounds good. A remaining problem with secret achievements/trophies is when they are secret on one system and not on another. Using control selector would work, although it would be ugly with table code. I can see editors moving an entry from one section to another according to their system, but duplicating it in both sections would be confusing too. I haven't seen other sites dealing with this, since all the sites are specific to either achievements or trophies, or at least have them in separate sections. Maybe some games' wikias have had some ideas. — najzere T 07:30, 11 December 2009 (UTC)

Achievement solutions layout
Recently Najzere has been adding achievement solutions. He has handled this by putting the solutions at the very bottom and linking to them. The Godfather's guide once took a very different approach, putting the achievement solutions in the description column (a side-effect of migrating from a very different format). This has got me thinking about the best way to handle solutions. The way I see it there are a few possiblilities: It would be nice to have an official standard layout decided on since this sort of content will inevitably become more common. Anyway, I am curious to know what the rest of you think. --Garrett (talk) 08:55, 7 January 2010 (UTC)
 * Simply linking to an explanation below (Najzere's solution). This keeps solutions hidden from those who don't want it spoiled, but the downside is that those who do want spoilers have to go back and forth between the lists.
 * Integrating the solution with the table (probably in some different format). This puts the solutions close to hand but spoils it for those who don't want it spoiled and will make lists noticeably longer.
 * Having the solution hidden in the achievement row using a modified version of the nav box script, maybe with the whole row being clickable (sort of like this) and ideally with some sort of "expand/collapse all" link. This has the advantage of putting all the information in one place without actually spoiling anything but could feel a bit awkward and might make editing more complicated (it would probably mean using templates rather than raw table code).