Talk:Treasure Hoard: Difference between revisions
Gamefreak75 (talk | contribs) |
|||
Line 119: | Line 119: | ||
:Yeah, I remember the general consensus being that we ''should'' include stuff from the Japanese version; the only problem is, this being the English wiki, you don't get many editors with access to it, and it's hard to come across the information otherwise.{{User:Greenpickle/sig}} | :Yeah, I remember the general consensus being that we ''should'' include stuff from the Japanese version; the only problem is, this being the English wiki, you don't get many editors with access to it, and it's hard to come across the information otherwise.{{User:Greenpickle/sig}} | ||
This page has every treasure difference appearance wise: http://tcrf.net/Pikmin_2/Version_Differences | |||
== Page Redesign == | == Page Redesign == |
Revision as of 21:08, August 6, 2012
I'm trying to improve this by making the columns sortable properly (it looks like there's been an attempt to implement it, but strange things happen). So far, I've got:
Succulent Series
NTSC # | PAL # | Name | Real world object |
---|---|---|---|
1 | 1 | Cupid's Grenade | Cherry |
2 | 2 | Sunseed Berry | Small Strawberry |
3 | 3 | Combustion Berry | Large Strawberry |
4 | 4 | Seed of Greed | Chestnut |
5 | 5 | Disguised Delicacy | Half of a Kiwi |
6 | 6 | Insect Condo | Apple |
7 | 7 | Citrus Lump | Orange |
(Click the icons at the right of each title to sort.)
but I'm not sure how to link each of the tables for each group up into one big one like it is now. Is it okay to have series as separate tables, or should I keep experimenting? Alternatively, all treasures could be in one table (sorting is cooler then as well), but there'd be no series subtitles. Also, I need to learn how to have the last column non-sortable - there's no need to sort alphabetically by description. - Greenpickle(talk) 20:26, 12 November 2007 (UTC)
I find that seperating the series would make more sense than bundling it all together. It's easier to sort- and overlook it that way.
Uh, about the column. I'm not sure if we need this. I appreciate your work, but in my opinion, we should sort it the way the game does. So, basically it should be sorted by the NTSC numbers. However, that would make it harder for those with PAL, and if we make it sortable, and then we could sort the in-game name aswell; with that we would be where we started: everything ecxept the real-world name. Well, sorry I'm not being a big help here; I'm just not sure...--Prezintenden(babble) 12:28, 13 November 2007 (UTC)
Basically, I think having the columns sortable, at least by PAL/NTSC numbers, would help compare PAL/NTSC treasures, or just sort it as your version does. The default order still remains, it's only when you click one of the icons that the sort order changes. It reverts to the normal order each time the page is reloaded. What made me think about doing this was one of the entries on User:Discordance/to do. - Greenpickle(talk) 19:18, 13 November 2007 (UTC)
Aha! Last column is now not sortable! - Greenpickle(talk) 19:25, 13 November 2007 (UTC)
So what's the verdict? Change or no?GP
Huh? What do you mean? I thought you changed it? It's sortable...
Uh, now that I checked it again... It doesn't really sort it in a understandable way. I can't find a pattern. Does one even exist? I guess with your comment you ment that you weren't finished with this? If you want to sort it, then you have my full support.--Prezintenden(babble)
I haven't changed the one on the page at all, only put this one here as an example. I will change it then.GP
Okay, I've done that, but I think it would be nice to have all treasures together in another table with 'Series' as another column, and all sortable together. Should I put that on the same page, or make a new page for it? Or is it a silly idea?GP
I'm having a hard time understanding you. I get that you want make a table where the sortable series are. You then pick a series and the items from that series show up. Those again are sortable aswell. I think I'm misconceiveing you; but if thats what you plan: sounds superb and very complicated.
Ah, wait, I read it again. Yeah, sounds good; but is it possible to make it sort primarely by series and then, uh, sub-sort it by any other column?--Prezintenden(babble)
- Yes, the default order would be whatever I put in the edit box. If you're still unsure, I mean having this:
(obviously this is wrong)
Series | NTSC # | PAL # | Name | Real world object |
---|---|---|---|---|
Succulent Series | 1 | 1 | Cupid's Grenade | Cherry |
Another Series | 2 | 2 | Sunseed Berry | Small Strawberry |
Third Random Series | 3 | 3 | Combustion Berry | Large Strawberry |
Succulent Series | 4 | 4 | Seed of Greed | Chestnut |
Succulent Series | 5 | 5 | Disguised Delicacy | Half of a Kiwi |
Another Series | 6 | 6 | Insect Condo | Apple |
as a separate table, only with every treasure in. It would be sorted by default as the treasures are on the page now. What I'm asking is whether it would be too much to have that on the same page, that it should be put it somewhere else.
I know! I could have a hide box for it, so you could choose which to show, the treasures arranged in groups or all in one table! Agree?GP
Wait, is there a 'hide' thing in the corner of this for you?
[... The content you want to hide goes here ...]
Sounds fine. Will the table be like the one you display here?--Prezintenden(babble)
Yeah. I think I'll just add it underneath the others; it'd probably look silly in a collapsible box and they don't seem to work anyway.GP
The link to "Non capitalization is an in-game error" won't go away, nomatter what I do. Is it just my browser, or is there an extra link object I oversaw?--Prezintenden
[... TESTED! DOES IT WORK? ...]
Fly Guy 2 03:57, 17 April 2008 (UTC)
Yeah, we know they work now as I fixed the CSS a while back. Er, want to tone down on the repetition?GP 11:29, 17 April 2008 (UTC)
Japanese treasures
Should we note the japenese only treasures? I know a few such as the 'national high top battery' , the 'Akebono Pink Salmon tin', and the ' National NEO high top battery'. Theres also some sort of cap with a clover on it and a green thing which resebles a can opener (hope the link works). User:Joshazilla23
- Aren't they just objects put in promotional material as opposed to actual treasurse in the game? To make changes, we'll need at least number and name, and you're just basing it off this image as far as I can tell.GP
Carrying weight
Should we add the weight of the treasures to the charts, and what is the difference in the NTSC and PAL versions and what do they mean?
- The weight of each treasure is in their own article, it's not required. And don't forget to sign. Snakeboss14
For the other question, see this.GP
japanese pikmin 2 treasures
I saw a japanese pikmin 2 video walkthrough once and saw treasures that were in neither the american and european versions, along with some different branding. we should include hese treasures as well
- Yeah, I remember the general consensus being that we should include stuff from the Japanese version; the only problem is, this being the English wiki, you don't get many editors with access to it, and it's hard to come across the information otherwise.GP
This page has every treasure difference appearance wise: http://tcrf.net/Pikmin_2/Version_Differences
Page Redesign
I think that the current table for the treasures is not that informational. I think this would be a better design:
Succulent Series
Image | Name | NTSC # | PAL # | Cave | Real-world object |
---|---|---|---|---|---|
File:Cupidgrenade.jpg | Cupid's Grenade | 1 | 1 | Snagret Hole | Cherry |
It would be collapsible, like is now and would be separated by series. We could also do away with the treasures section since it is basically a carbon copy of the information above. Any thoughts, concerns? Pikmin1254
- Great idea! If everyone else approves I'll start making transparent images for the treasures. And Maybe the cave section should be changed to area/cave and carry weights could be added. Vol (Talk)
- I have a couple of concerns. First, the full treasure table is so a sortable list of every treasure exists - for those wanting the convenience of finding the heaviest, for example. Second, adding an image to every row would make the page much larger, so you could see far fewer treasures together. I have a couple of ideas of solutions, though; no time now, but I'll look at it later. Having that 'cave' (should be 'location') field is great, though. GP
- If we're worried about pictures couldn't the pictures be collapsable? So you only see it if you want to? Crystal lucario
How about we add the value in pokos? Thought that would make it a bit longer. Snakeboss14
Okay, how about this? First, you may have to bypass your cache (follow the instructions at the top of here). Now, does it work for everyone? The show/hide images are hardly final, just something I used for testing. The way the names are shown at the top (bullet points) should change too; I just didn't know how it would look best - ideas? GP
Okay, I think table.hideable is ready to use now. You can start replacing the thumbnail images we have with rendered ones and amending the series tables and all-in-one table with image, location and value columns (though I disagree with moving name before number). In a couple of days, time permitting, I might hack something together to do it automatically, if no-one's made the effort. GP
Oh, and weight and max. carriers. Use the infoboxes. GP
Done for the big table, and it'll be easy enough to extract the smaller ones - but yeah, it's going to end up huge in the edit window (70k now). I guess we should get rid of one, but which? I still prefer the big table for being all-inclusive, especially with regard to sorting, and see no reason for having the small ones. GP
- No-one answered my question as to whether we should get rid of one set of treasures (series or big table). GP
- From the point where the question has been asked, and a couple of months had passed, I think it's safe to say that one user may change it as s/he pleases, seeing as no one else objected since the question was put. Huh... what's the question again? I'm not reading through all this text... {EspyoT} 07:29, 28 June 2011 (EDT)
- "Done for the big table, and it'll be easy enough to extract the smaller ones - but yeah, it's going to end up huge in the edit window (70k now). I guess we should get rid of one, but which? I still prefer the big table for being all-inclusive, especially with regard to sorting, and see no reason for having the small ones." GP