Location info...

Forums: Index > Planning Forum > Location info...

Post

Is there a wiki standard for {{loc}} information? I personally think that the more exact the location, the better -- especially for players not using uber-mega-extreme graphics settings, who can see every bump in the road from a mile away -- but I've been noticing lots of users "correcting" other users' edits by shortening locations. Example: ( 124, -21, 1469 ) /waypoint 123.93, -20.78, 1469.34 being changed to ( 123, -20, 1469 ) /waypoint 123, -20, 1469 . Even IF the standard is for simplified locations that "get you close enough", I still think this is a bad practice (just lopping off the information after a decimal point), mostly because in that example a closer location would be ( 124, -21, 1469 ) /waypoint 124, -21, 1469 (via rounding).

On a similar topic (that being of altering code), is there a purpose to redlinking to an item/NPC/mob not yet on the wiki using {{NPC|}}, {{Item|}}, {{Equip|}}, {{Monster|}}, {{Quest|}} etc etc? I haven't noticed that clicking such redlinks to start a page automatically loads the page with the NPC template. AND, once the link is added to the wiki, is there any point or purpose to keeping those links rather than [[regular brackets]] (or, as I've noticed some users recently doing, switching from the brackets back to links like {{Zone|}})?? -- Mysterious drake 01:14, March 2, 2010 (UTC)

For presentation purposes we like to go with integer values in the Loc template. With that said however, one change I'd like to make to that template (if I can get Kodia or Chili to unlock it) is to add automatic rounding. Then you could put 123.45678 in as a parameter and it would automatically round it to 123 in the display (but still copy the full precision). Whenever I make a change like that I round, not just truncate, as that is what should be done (unless I make that change to the template).

In regards to those link templates... they are only useful if it is a redlink. If it's a redlink, it adds it to a category like Category:Articles with quest redlinks for tracking. If it's a good link, they add no value and I actually dislike them (they add processing overhead that is simply not needed). New users tend to see all of those and think the [[ ]] syntax is wrong and just use the link templates. I prefer to replace them with a standard wiki link when there is a good link, the only time you'll see me use them is if it is a redlink. -- lordebon 01:35, March 2, 2010 (UTC)

Ahh, okay, redlink tracking makes sense. But I definitely see users replace [[working links]] with {{NPC|this style|}} at times. And yeah, as a webcode-monkey, the extra overhead (of code lines and processing needed) bugs me too... I'm just glad to have it confirmed that the [[ ]] style is proper once a page is created.

And thanks for the feedback on loc's too. I guess I need to stop being quite so anal-retentive, though I'm definitely interested to see Fuzzy or Kodia or Chili weigh in on this as well. (I definitely like your idea of auto-rounding, if it's possible, lordebon).

-- Mysterious drake 02:01, March 2, 2010 (UTC)

Yeah, there's no real added value in replacing a working link with a link template. All it does it maybe guard against something being moved or deleted in the future and becoming a redlink. As for auto-rounding, it should be possible. The {{#expr:}} function allows for rounding to specified decimal precision (so "round 0" would round it to an integer value). -- lordebon 02:04, March 2, 2010 (UTC)

Loc Precision Edit

To breathe some life back into this topic... I have working code to automatically round /locs. I currently have Template:Lordebon Dev set up to automatically round the numbers to the nearest integer for display purposes, but maintain full precision in the copied number (since those decimals occasionally do help locating the exact spot in-game. Does this behavior agree with everyone as to what should happen? If the consensus is to round the copied loc as well, I can always code in an optional parameter to not round the copied waypoint when a specific parameter is given (for those few cases I mentioned). -- lordebon 21:45, April 19, 2010 (UTC)

If I understood the complexity of the code you have written there -- well, let's just say I don't understand the programming language (per se) that the wiki uses. Wish I did, so I understood your coding better and/or to be able to test it and offer my two cents on what you've developed. Nonetheless, I like the idea of auto-rounding for display but unrounded locations for copy purposes. However, to play the devil's advocate, even on lower play resolutions, a rounded loc should get any and all users close enough to whatever they're seeking. -- Mysterious drake 00:23, April 20, 2010 (UTC)

I can unlock the template if you're interested in updating it. Please let me know.-- Kodia 10:42, April 30, 2010 (UTC)

Looking over your template... thats actually very well written for being that complex, Kudos! I'm wondering if we can merge the 3 [[Category:Locations with missing # coord]] into 1 category. I think its useful to have someway to track pages with incomplete LOCs (some people are into that stuff), but do we need to know which one is missing? Would simplify the code out of yours and some other templates. Anyone else have opinions? -- Uberfuzzy 13:43, April 30, 2010 (UTC)

I still wish I could find good resources else where in the wikia-verse, or elsewhere online, for the template "language" used for complex functions such as what Lordebon has developed.... Can anyone give me some better steering? However, I'm fond of the idea of merging the 3 "Locations with missing x/y/z coord" into one category. Last time I went perusing through there, it seemed pretty self-evident what was missing (or mis-coded) when the page in question was visited. -- Mysterious drake 16:46, April 30, 2010 (UTC)

i think you will find this page useful -- Vraeth 17:12, April 30, 2010 (UTC)

Yeah the parser functions page is hugely useful (I reference it quite a bit). I also have no problem with updating it to go to a single category for missing locs, do y'all want me to do that and test it, then we can unlock the main template and copy things over? -- lordebon 18:56, April 30, 2010 (UTC)

Ooooh, thanks for the link, Vraeth. I'm all for testing and seeing if that can simplify things, lordebon... Guess it's up to the admins to greenlight the concept though, first. hehe -- Mysterious drake 12:54, May 1, 2010 (UTC)

http://www.mediawiki.org/wiki/Extension:Parser_function_extensions is good too.

Updated Template:Lordebon_Dev to use only a single category: Category:Locations with a missing coordinate . I also fixed it so that if the x value is missing it still shows the other values (don't ask me why, but the old one was coded to put it in a "no-x" category that could never be used, since something with no x would cause the template to exit without doing anything). User:Lordebon/Sandbox shows two new examples, one with x missing, one with z missing. If folks don't see anything wrong, we should be able to open up the old template and make the changes. -- lordebon 23:16, May 2, 2010 (UTC)

I like the way it acts... Everything you've got on your sandbox functioned just fine for me just a bit ago, using the push to clipboard copy-function. Though, I can't help but wonder if some sort of announcement of how the {{Loc}} template will function after the introduction of the change. (I.E. "Use precise locs -- but be aware that the pages will display simplified locations even though they will still copy to your clipboard the precise location.")

My two cents' worth for now... -- Mysterious drake 04:39, May 3, 2010 (UTC)

Looks good. I had no trouble with it. But instead of just saying "precise" using an example would be far better. "If you type X (marks the spot), then Y is what displays." That would be my suggestion. I'll unlock the template for a couple of days and then lock it back up when you give me the all clear.-- Kodia 10:05, May 3, 2010 (UTC)

The template itself is currently only locked to new and unregistered users, so you should already be able to use it. Please let me know if you can't access or edit it.-- Kodia 10:13, May 3, 2010 (UTC)

Missed the original unlock message. Template has been updated and smoke-tested, documentation is being updated now. Should be safe to re-lock the template in about an hour or so (in case any issues pop-up in further testing). -- lordebon 15:05, June 25, 2010 (UTC)