Our 2014 Christmas Contests have begun! Check the Bulbagarden Forums to find out how you could win 1 of 30 copies of ORAS!
Please remember to follow the manual of style and code of conduct at all times.
Check BNN and Bulbanews for up-to-date Pokémon news and discuss it on the forums or in our IRC channel #bulbagarden on irc.systemnet.info.

User talk:Adamws

From Bulbapedia, the community-driven Pokémon encyclopedia.
Jump to: navigation, search
Welcome to Bulbapedia, Adamws!
Bulbapedia bulb.png

By creating your account you are now able to edit pages, join discussions, and expand the community-driven Pokémon encyclopedia. Before you jump in, here are some ground rules:

  • Be nice to everyone. It's in the code of conduct.
  • Make good edits. Preview them before you save to make sure they're perfect the first time around.
  • Use wikicode and link templates when adding content to a page.
  • Use proper grammar and spelling, and read the manual of style.
  • You can't create a userpage until you've added to the encyclopedia. It's a privilege. See the userspace policy.
  • Use talk pages to resolve editing disputes. Don't "edit war," or constantly re-edit/undo the same thing on a page.
  • If you have a question about something, be proactive. Take a look at our FAQ. If you're still stuck, ask for help. The staff won't bite.
  • Sign all talk page posts with four tildes (~~~~). This will turn into your name and the time you wrote the comment.
  • For more handy links, see the welcome portal.
Thank you, and have a good time editing here!
  It's Funktastic~!話してください 04:22, 20 March 2013 (UTC)  
 

The Preview Button

Instead of editing a page several times in a row, try using the preview button to make sure your edit looks the way you want it to. It's right next to the Save Changes button. Please try it out, so as not to clog up the Recent Changes. Thanks! ----Pokemaster97 03:57, 10 July 2013 (UTC) ok, I'll remember that. Adamws (talk) 04:08, 10 July 2013 (UTC)

Fixing red links

Keep in mind, the open allowance for users to fix such problems only extends as far as the links causing the unwanted entries on the wanted pages. Modifying anything that isn't causing any such problem entries is not permitted without the user's permission. - Kogoro - Talk to me - 23:20, 16 May 2014 (UTC)

Diurnal (and etc) tables

I cleaned up the tables you put on the Diurnal Pokémon page. I suppose you will do the same for Matutinal and Nocturnal, so it would be great if you could follow that example rather than repeat the same mistakes on the other pages. Thanks. =) Tiddlywinks (talk) 02:26, 12 October 2014 (UTC)

Mirage spots

With the different spots having different Pokemon, I'm thinking we should resort to the numbering system from the guide so we can be more precise with the locations. glikglak 00:28, 15 December 2014 (UTC)

Ok, go for it with the Main Spaced ones. And with the Mirage Forests, I will try to get that one out as fast as possible, then it can be brought to the same standard. Adamws (talk) 00:22, 16 December 2014 (UTC)
Pardon me for butting in, but I actually don't understand how using completely abstract numbers helps anything in particular. I think having the location as the header seems like the best option (especially since it appears in the TOC: it means you can see all of the locations in more or less one place without having to scroll the entire page and read each section). Tiddlywinks (talk) 00:27, 16 December 2014 (UTC)
Ok, I know this makes me sound like a flip-flop but I do agree with Tiddlywinks on this. I do see how a number system would work but, the way that they are now with them being labeled by their location works too. Adamws (talk) 00:31, 16 December 2014 (UTC)
As it is now, things like Pokemon's availability locations only say Mirage Mountain, Mirage Cave, etc. When there's eight of those, and they don't appear at the same time, saying just Mirage Forest doesn't help much. We currently can't get much better, though; putting rough directions in the Availability templates isn't going to look too good. If we have an exact, official naming system, we should use it for convienence sake.
I suppose we could anchor the numbers below the headers, but I see people getting confused when they click Mirage Cave 1 and nothing on the page says Mirage Cave 1. glikglak 11:01, 16 December 2014 (UTC)
That is interesting. But I kind of think the same thing about availability entries as the section headers: I think it's still nice if people don't have to reference the Mirage Islands/etc page to know where to find the place they're looking for. Of course, this means I think it should be better than it is at the moment, too; but IMO something like "Dewford Town Mirage Island" (which naming is complicated by the multiple Mirage Mountains around Routes 125 and 129) or "Mirage Island (west of Dewford Town)" would work just fine.
I think something like that is best. But if "Mirage Island 1"/etc really seems best to you, I could be okay with calling the sections things like "Mirage Island 1 (west of Dewford Town)". If you add an anchor for just "Mirage Island 1" below that, you could easily link just "Mirage Island 1" in a Pokemon's location then. For my money, though, I'd much rather just make the location explicit in the availability entry. Tiddlywinks (talk) 16:09, 16 December 2014 (UTC)
Being new areas, people would have to go to the page to find out where they were, even if they had precise locations. Giving them specific names (even if it's just a number) will help people remember which spot is where and what it has. But now that I think about it, the directions should probably go next to the names in case the community (or even the anime) comes up with its own nomenclature. "Mirage spot # (directions)" looks like the best option. glikglak 01:00, 17 December 2014 (UTC)
Just because they're "new" areas, that doesn't mean they will always be "new" to people. Soon enough, people will know all they feel they need to know from Mirage Forests/etc, and if, at that point, they just want to find a given Pokemon, they shouldn't still be forced to visit the Mirage Forests/etc page just to figure out which location it is.
People can remmeber names, but numbers are not—at all—"good" names. Especially when they're never overtly reinforced by the games. If the anime ever wants to do something, we can worry about it then; we don't need to complicate things with what may not be a problem. Tiddlywinks (talk) 02:22, 17 December 2014 (UTC)
They're certainly better names than "Mirage Mountain northeast of Route 125 but not too far north". What we got is what we got; using both is our best option. But that still leaves the question of what we're going to name the headers. Having just a line underneath that says " This is Mirage Cave 1" would look silly. Do we condense them, "Mirage Island 1 - East of Dewford"? glikglak 11:02, 17 December 2014 (UTC)
With your above comment, it sounds like you still think that the availability entries would be best written as just "Mirage Island 1" and such. Let me be clear about that: I very much do not like the idea of not giving the explicit location in availability entries. I have no intention of accepting that unless staff should say that's best. Like I said above: you don't force people to visit a page if they don't need to.
I've not said it out, but let me just make it clear what I currently recommend: the availability entries should be edited to things like "Mirage Island (east of Dewford)" (and it's kind of ridiculous to suggest that something like "but not too far north" would need to be included...). That's all. All the rest remains as it is. I don't suggest we use the phrase "Mirage Island 1" ever...I simply don't see any real need/use for that sort of phrase anywhere.
But...if it'll bring an end this debate, I'll accept changing the headers to "Mirage Island 1 - east of Dewford" and the like; maybe add an explanation somewhere that the numbers represent the order of the internal location indices (and maybe that the guide book uses that naming, though that comes off like the bad kind of trivia to me). Besides that, I don't know of anything else that would be remotely useful. (If you want to use the full section header in availability entries, fine I guess, if a bit pointless.) The only complaint I have with this is that it puts the locations in (from a usability standpoint) an arbitrary order, as opposed to the current route progression. I don't like it, but I'd just like to solve this more. Tiddlywinks (talk) 15:22, 17 December 2014 (UTC)

(resetting indent)Using "Mirage spot #" no more forces people to look at the page than all the B2W2 entries that say "Hidden Grotto"; if you don't know what it's referring to, you have to look at the page. "but not too far north" was an exaggeration to point out that the directions are inexact. With a 360° camera and no form of compass, the difference between north and northeast becomes hard to tell. And keeping to the loop-de-loop of the routes for something that isn't limited to it seems more arbitrary; a clockwise rotation would be better from a usability standpoint. glikglak 01:54, 18 December 2014 (UTC)

The directions of north of location or northeast of location aren't too confusing. There is a map on the bottom screen with an arrow that represents the player and which way they are facing. Adamws (talk) 02:03, 18 December 2014 (UTC)
Glik, you say that "if you don't know what it's referring to, you have to look at the page". This is very true. It's true of anything. There is, simply, no getting around that circumstance. That's why I didn't even think it worth mentioning.
But what about once you do know the basics? If you know what Mirage spots are, you certainly don't "need" to visit the Mirage Islands page to know what they are... So if the availability just says "Mirage Island 1" and you don't remember where that's supposed to be (and there's no good reason you should remember)...well, then you're gonna have to visit the Mirage Islands page for the sole purpose of figuring out where "Mirage Island 1" is—when the availability entry could very easily have just said the location right out. That should not happen. Tiddlywinks (talk) 02:21, 18 December 2014 (UTC)