User talk:Gaerlin

Archives
2017
2016
2011
2009

Verified template

It doesn't seem like the Verified template is working as intended. If you leave out the update parameter, it uses the currentupdate template - but that means that when the currentupdate is updated, all the verifications are dragged along with it when they shouldn't be. For example, A Warden's Cunning - Tier 1 says it was verified in October of last year, for the update that just released a month ago. We either need to remove that condition, or else make it substitute the current update rather than linking to the template.

(I know you didn't create the template yourself, but you're the one who's been making the most use of it so I thought I should bring this to your attention.) -- Elinnea (talk) 15:37, 6 July 2017 (UTC)

Thanks for letting me know. I agree that it should subtitute the current update instead of just using the template. I'll see if I can make that correction. --Gaerlin (talk) 16:10, 6 July 2017 (UTC)

Looking at this I realize that substition is not possible, because we have no way of modifying the original page to "pin" the Verified as occurring at a specific update. This is the reason that the date/time is a required property. The best way to specify an verification as corresponding to a specific update is to put {{subst:CURRENTUPDATE}} in the fourth parameter of {{Verified}}. I will modify the template instead to not show any update number if one isn't supplied with a parameter. At least that way it will be less misleading. --Gaerlin (talk) 16:30, 6 July 2017 (UTC)

What are those 6 numbers after date parameter in the template?

Steppenwolf (talk) 09:47, 20 July 2017 (UTC)Steppenwolf

That's the date/time format that {{subst:CURRENTDATE}} uses, which is in the format YYYYMMDDHHMMSS. The HHMMSS part isn't shown in the output of the template however. --Gaerlin (talk) 16:24, 20 July 2017 (UTC)

Scaled Items

Do not change tool-tips of scaled items from cap level to dots, it looks awfull... And do not change size of 100px tables, I'm trying to uniform it...

Steppenwolf (talk) 06:37, 22 July 2017 (UTC)Steppenwolf

I actually like the dots because it accurately communicates that the values for those fields varies by level. If we're not going to use dots, we need to come up with some other way on the tooltip to indicate that it is a level-scaled item. Just putting the level 105 values on there is misleading because, just looking at the tooltip, you'd never realize it is level-scaled. Maybe we can add a "scaled = y" parameter to Template:Item Tooltip that displays some grey text in the tooltip saying "This item is level-scaled" or something like that. Thoughts? --Gaerlin (talk) 12:08, 22 July 2017 (UTC)

Better than dots anyway... Dots are annoying, numbers at least give you some idea about attributes ratio...

Steppenwolf (talk) 15:34, 22 July 2017 (UTC)Steppenwolf

We've been using the dots for a long time in skills, most of which scale in some way - for example, Fiery Ridicule. I'm not claiming it's the best, but it does make sense to indicate in some way when part of a tooltip scales with level. Just using the level cap value is not good, because then as soon as the level cap is raised, the tooltips are stuck with a random value of whatever was the level cap at the time when the item was added to the wiki. Some people have tried to reverse-engineer ratios or formulas to display in the tooltips, but then they change those in-game and it becomes a mess.

We've never found a perfect solution. Using either ... or x in place of a value, and then providing the specific values in a table if needed, has worked pretty well for the page itself, but isn't as helpful when you're just reading the mouse-over tooltip. Using the triple dots for item level itself at least has the advantage that it gets added to Category:Item Level ...-- Elinnea (talk) 01:08, 23 July 2017 (UTC)

First, those who are really interested in values of other than cap level items will enter the item page and read tables... Those who need basic info only will read mouse-over tool-tip... If tool-tip is with dots, they will know only what attributes are involved, but will absolutely have no idea what amount to expect... If it says +... Might, +... Vitality, it can be +999 Might, +100 Vitality, or +100 Might, +999 Vitality, or +100 both, or +999 both, or any other ratio and no one will have idea if that's might based item, vitality based item, or balanced item, or whatever... But if it says +300 Might, +150 Vitality for cap level, they will have idea what to expect for lower level items... "scaled = Yes" parameter would be good addition to tool-tip, better than dots in every sense...

Steppenwolf (talk) 06:39, 23 July 2017 (UTC)Steppenwolf

Scaling Items

Please see discussion on the Talk Page of the Boilerplate: Item help page: Talk:Boilerplate:Item#Scaling_Items_revisited

Wm Magill - Valamar - OTG/OTC - talk 16:48, 23 August 2017 (UTC)

Template patching -- Template:Crafting

Since you seem at home with CSS and Templates...

This template is used in the "New Recipe" process. Template: Crafting

See the last comment (from 2014) on the talk page Template talk:Crafting

It's still broken.

I've looked and can't find the issue, but I am now 10+years away from such stuff (I retired in 2006), so "younger eyes" are needed! :)

Wm Magill - Valamar - OTG/OTC - talk 17:28, 23 August 2017 (UTC)

I think I fixed it - take a look and let me know. --Gaerlin (talk) 05:09, 24 August 2017 (UTC)

Actually it does look fixed, but existing pages using the template are not updating until they get re-edited/re-saved for some reason. I thought all pages with templates got refreshed automatically by some background process. Is this not the case? --Gaerlin (talk) 13:30, 24 August 2017 (UTC)

Relic template

Note that the Relic Template is apparently broken.

It is definately wierd in that you have to specify the "image" not "icon" value to get the image to diaplay on the page.

Then on the Index page, you get an error instead of the correct pop-up.

Wm Magill - Valamar - OTG/OTC - talk 20:58, 25 August 2017 (UTC)

I fixed {{Relic}} such that the "icon" parameter now works. If "icon" is specified it will show it, otherwise it will check if "image" is specified and use that (but "icon" will take precedence). --Gaerlin (talk) 21:09, 25 August 2017 (UTC)

Thanks!

Very strange -- that is how ?all? of the other templates work. I wonder how long that has been broken.

However, the pop-up is still not happening. The basic design of this template is very different from the others which use the ToolTip template.

Wm Magill - Valamar - OTG/OTC - talk 00:06, 26 August 2017 (UTC)

Legendary Legacies Index

Truly awesome work!

Creating the page itself is trivial compared to the work involved in collecting the data!

The community appreciates your dedication.

Wm Magill - Valamar - OTG/OTC - talk 08:11, 5 October 2017 (UTC)

Thanks very much :) I think this fills a gap that's been there for a while, so I'm glad I was able to fill it. --Gaerlin (talk) 14:00, 5 October 2017 (UTC)

Very nice :)

Thanks for the new format of the coordinates lists on the treasure cache deeds pages - sure a lot of work, but it pays off, makes it easier for readers. :) --Dathor (talk) 08:31, 22 August 2018 (UTC)

Thanks! At some point I'll go back and update the older pages as well so they're all consistent. --Gaerlin (talk) 17:06, 22 August 2018 (UTC)

Promotion to Bureaucrat

Congratulations Gaerlin we directors have selected you for a promotion! Well deserved and well done it's been a journey! Rogue (talk) 21:30, 6 October 2018 (UTC)

Wow, thanks so much! Quite an honor :) --Gaerlin (talk) 21:39, 6 October 2018 (UTC)

Arbitrary One-handed Weapons (Level 1-20) rollback

Sorry about that, that was a misclick. I think I also assumed that there would be a confirmation before the rollback took place... won't happen again. Orodalf (talk) 02:43, 5 December 2018 (UTC)

OK no problem, understood :) --Gaerlin (talk) 03:35, 5 December 2018 (UTC)

Level-Scaling Essences

I want to commend you on all your work with Level scaling, with all the ... items and item indexs. I hope you have some bots working for you, it could take forever to update them manually.

I have read thru most of your discussion on the Talk Page of the Boilerplate: Item help page: Talk:Boilerplate:Item#Scaling_Items_revisited and your level scaling discussions here. I am currently converting the essences to use level-scaling instead of the "..." monkeyer. After reading thru the boilerplate:Item updates I realized you had also started removing existing stat tables from level scaling items. I love the level-scaling idea, but keeping the existing stat tables would allow for specific item stats to still be available. I am not suggesting that new items require stats tables, but I do believe we should keep all the individual item data already added to the wiki. Think about it and get back to me. Matthew.zellmer (talk)

That’s good to hear you’re working on cleaning up the ... on Essence stats and conforming then to the new standard! Strictly speaking Essences aren’t level-scaled anyway, they’re tiered. Therefore the intermediate values are easy to determine and we should leave the value tables in place on the Essence pages. --Gaerlin (talk) 13:11, 21 May 2019 (UTC)

excellent thanks for getting back to me. Matthew.zellmer (talk)

I have a function library which can calculate most stats. I have versions for a couple of Basic languages and LUA-script at the moment.

The standard function call which returns a value is like this: CalcStat("stat identifier",stat level,optional stat points) --Gisel Avaleazar (talk) 18:48, 14 June 2019 (UTC)

coords.js update

Hello, the popup map on the Treasure-seeker of the Vales page is messed up, seemingly because the wrong coordinates have been entered for it in User:Eleazaros/coords.js. Copying the way it was done for other regions, I think the "Values of Anduin" section should look like this:

		case "Vales of Anduin":
		// Special case: Lies entirely north and west of the origin,
		// so we need to flip the north-south and east-west positioning (the "100 - getOffset" bit)
			// [[NW= 18.3N 81.4W]]  [[SE=12.4N 40.4W]] 
			xMin = 12.4 * 10;
			xMax = 18.3 * 10;
			// area is north of the origin; invert positioning
			xPos = 100 - getOffset(xMin, xMax, xNum);
			yMin = 40.4 * 10;
			yMax = 81.4 * 10;
			// area is west of the origin; invert positioning
			yPos = 100 - getOffset(yMin, yMax, yNum);
			break;

I don't have access to edit the script, can you update it? Thanks, -Thurallor (talk) 05:53, 12 June 2019 (UTC)

Updated - let me know if that works. --Gaerlin (talk) 05:56, 12 June 2019 (UTC)

It didn't work. I found my error, fixed it, and verified that it works by modifying the javascript on my local machine:

		case "Vales of Anduin":
			// xPos is a special case for Vales of Anduin due to 0.0 North/South in zone.
			if (xType == "N") {
			// North -- 0 base the top of the map by removing North reference to the 0 point.
				xNum = 183 - xNum;
			}
			else {
			// South -- Add 183 to the number to offset the 0 base at top.
				if (xType == "S") {
					xNum = xNum + 183;
				}
			}
			// [[NW= 18.3N 81.4W]]  [[SE=12.4S 40.4W]] 
			xMin = 0.1 * 10;
			xMax = 30.8 * 10; // 0.1S to 12.4S + 0.0N to 18.3N = 30.8
			xPos = getOffset(xMin, xMax, xNum);
			yMin = 40.4 * 10;
			yMax = 81.4 * 10;
			// Special case: Lies entirely west of the origin,
			// so we need to flip the east-west positioning (the "100 - getOffset" bit)
			yPos = 100 - getOffset(yMin, yMax, yNum);
			break;

I would like permission to make some changes to this script to make it easier to maintain. It should not require a reverse-engineering exercise every time we need to add a new map. Who would I contact to get permission? Thanks Thurallor (talk) 18:49, 12 June 2019 (UTC)

OK I updated it again. You'd need to ping User:Lotroadmin (skunark on Discord) to get permissions to edit the file. --Gaerlin (talk) 19:03, 12 June 2019 (UTC)

Updated Virtue values

Hi, I discovered that Virtue rank 49 has a different item level on live. In beta on BR, rank 49 had item level 188 and now it has 190. This means that all the stats for that rank were incorrect. I've updated the table image and source files to reflect the right values. --Gisel Avaleazar (talk) 18:56, 14 June 2019 (UTC)

Thanks - I updated all of the Virtue pages to reflect this. This change is actually pretty easy to make since all of the values are stored in tables in subpages under {{VirtueStats}} (see doc for details). --Gaerlin (talk) 20:42, 14 June 2019 (UTC)

Item Indexes

Hello, i noticed after your work on the indexes there is around 120 double redirect pages. Not sure if they should be corrected to the real target or deleted since i checked some of them and it seems nothing links to them anymore. In most cases even the middle redirect page has nothing that links to it. Can you please look at it? Thanks Drono (talk) 08:45, 6 August 2019 (UTC)

I will check into this, thanks for the heads up. --Gaerlin (talk) 18:24, 6 August 2019 (UTC)

Armour Sets

Hello, your recent edits on some armour sets removed the categories they belong to and some cosmetic information.
example: 'Armour of the Lady's Favour' more affected sets are in the Uncategorized pages.
Drono (talk) 08:12, 30 October 2019 (UTC)

Oops sorry about that - I'll go back and review to make sure they have their categories back. --Gaerlin (talk) 16:40, 30 October 2019 (UTC)

Stout-axe traits and deeds

Hey there! I've filled in some information on these pages you've tagged as under construction. Mostly level requirements and rollover text. Dadwhereismom (talk) 22:36, 30 October 2019 (UTC)

That's great, thanks! I'll take a look and remove the under construction stub from anything that looks complete. --Gaerlin (talk) 03:33, 31 October 2019 (UTC)

My lvl 42 would greatly appreciate more work on this page :P

Traceries attribute corrections

Hi Gaerlin!

I noticed recently that all (as far as I can tell anyway) of the Tracery item pages have an incorrect attribute in them; they have "binding" instead of "bind", which prevents that property from showing up in their tooltip. I've also seen that you've been running a lot of bot edits on those pages lately, so I was wondering if you could perhaps work some of that bot magic on all of the traceries (Heraldric, Word of Mastery, Word of Power and Word of Craft) to correct the naming of this attribute? Oh, and additionally; since Update 30.3.1 all Traceries are now Bound to Account, so if you could also get the bot to update that at the same time, that would be lovely! It would save having to go through all those hundreds of pages and changing it manually. :)

So, in summary: if you could please do a bot replacement of "binding" with "bind   ", and "BoA" with "BtAoA", for all the traceries in all categories. Thanks! ^_^
--Stargazer (talk) 14:07, 28 October 2021 (UTC)

I don't actually have a bot, just a custom editor, so I don't have a way to automate updating all of the Traceries. I believe Drono does though so I'll ping them on this. --Gaerlin (talk) 22:17, 28 October 2021 (UTC)

Please Slow Down Your Bot

For many hours now Lotro-Wiki has been very sluggish with lots of timeouts and alike. I found that you are running your bot and it seems at quite a high rate, exhausting the server I presume. Please throttle your bot.

Also, shouldn't you run your bot using a bot account and list it at Lotro-Wiki.com:Bots? I am quite certain I read some policy or guide-line that an account is the suggested way but I cannot find it quickly now. Either way, using a bot-account you never have to play around with your user rights as I see you do now 😉 — Zimoon 19:54, 28 June 2022 (UTC)

I'd be surprised if my edit volume is enough to cause performance issues since it's not any more than I've done lots of times previously, but I asked Skunark to look at the logs to verify just in case. Have the issues continued for the past couple of hours? I haven't done any edits during that time.--Gaerlin (talk) 00:06, 29 June 2022 (UTC)

Skunark confirmed, nothing unusual in the logs and no particularly high level of activity indicated. So most likely the slow performance was network related instead. --Gaerlin (talk) 00:26, 29 June 2022 (UTC)

Could be network issues, yes. Sorry for the noise then.

But what about using a separate account for your bot? 🙂 — Zimoon 17:39, 29 June 2022 (UTC)

HEH, now I understand I didn't see your response. You replied when you were on bot-permissions ... but the default "recent discussions" filters out bots 😛

Yet another reason to... — Zimoon 17:41, 29 June 2022 (UTC)

"Cleaning up" quests - please don't

Hi Gaerlin, I have noticed you've been "cleaning up" parameters in quest-info boxes every now and then. But removing parameters makes it more painful when other editors are adding missing data, such as coords or quest-starters/enders or locations. As there is no value in removing them, please don't do that. It only adds another change-edit to the database but does not add any performance boost or anything like that. But more work to other editors. Thanks for your understanding. — Zimoon 16:12, 23 July 2022 (UTC)

Sure, that makes sense and I can see how it would make editing templates like a Creature or Quest harder without the blank parameters. Originally it was intended for very long templates like Item Tooltip where the information is typically all present at time of inspection so new parameters would rarely need to be added, so I'll refrain from doing so for the smaller templates. --Gaerlin (talk) 22:42, 23 July 2022 (UTC)

Many thanks! — Zimoon 09:47, 24 July 2022 (UTC)

Cleanup

Hey, i have added the {{Cleanup}} to this page "Incomparable Scaled Gear by Drop Location", its about 2 years now that its showing in uncategorized pages and has some broken syntax. Not sure how the {{Cleanup}} works so leaving a message here too, can you please look at and either fix or delete if its not used? Thanks. --Drono (talk) 06:16, 25 September 2024 (UTC)

You're right I totally forgot about that page. I'll move it to a work-in-progress under my own page, thanks. --Gaerlin (talk) 19:10, 25 September 2024 (UTC)

Item changes

Hey, Gaer since we are both using more or less automated ways of updating the item pages, we should probably get them to not overwrite each other changes. Recently i noticed lot of changes with different capital letter in WEffect apperaered in my bot log. I have filtered them out, so at the moment they got overwriten only if there was also some other change. The changes are eg {{WEffect|Axe}} to {{WEffect|axe}}, as well as some param ordering amount before chance. I have coded the weapon name lower case, because it was lowercsae in the template doc , also the param order in the doc is with chance before amount, i know they are positional so it doesnt matter, but iirc i have seen it on some pages beeing fliped between mine and yours edit, so we shoould probbaly sort it out. I would vote for the order same as it currently is in the template doc eg.
{{WEffect | <item effect type> [| chance = <chance to apply>] [| amount = <amount of effect>] [| type = <damage type>] }}
Weather the effect type should be lower case or capitalized - i dont really have a preference but would like to synchronize it with you and edit the template doc accordingly, so we dont flip-flap it with our edits.

Also if you see something similar, that my bot is 'undoing' some of your changes, please let me know. --Drono (talk) 18:50, 20 November 2024 (UTC)

Hey Drono yeah my editor does a lot of automatic changes like that. I thought it was defaulting to lowercase for parameters in WEffect and AEffect, but I'll double check as it makes sense to keep it lowercase for consistency. It also automatically reorders parameters in templates like Item Tooltip into the same order as in the Preload template, which is why it switches the order of things like item_id and disambigpage. For WEffect/AEffect templates it also removes parameters that are spurious, i.e. if they are the same as the default values. --Gaerlin (talk) 21:16, 20 November 2024 (UTC)

And I agree following the parameter order in the template doc makes sense. I modified my editor to output both WEffect and AEffect parameters in the template order: chance, amount, type, duration, level.

I havent done the ordering in Item Tooltip, but i am also working on fixing the params order based on the Preload template.

Currently I sometimes use the default param, some of the defaults makes sense, some of them are actually never changed (like, crossbow/jevelin chance is always 5), some of them have multiple values and i didnt check which is the default, will try to change that. --Drono (talk) 09:22, 21 November 2024 (UTC)