Hi, Easton West, and welcome to the Istaria Lexica! Thank you for joining the community. We hope you'll feel very welcome and enjoy your visits.
New committers are very welcome to the site and I hope I can provide you with all assistance you may need.

You may be interested to read the following articles to get an overview of the Wiki:

---

Read the Gifted's guide to the Istaria Lexica Wiki Wiki editor's reference card Look into the complete list of guides Examine the wiki page history

List of wanted pictures List of wanted pages List of administrators

Please leave me a message if you got questions.

Best regards,

-- The Istaria Lexica Librarian (talk) 09:39, 12 July 2022 (UTC)

Well done!

Heya, thanks for contributing! I see you're good on it and handle all those templates. If you ever need some help or got new ideas let me know!

Elteria Shadowhand   [talk]

15:18, 1 August 2022 (UTC)

Please wait

Heya Easton, For the craftable products you want to edit, don't mind them at this moment. There will be a massive update for them soon (I am working on a batch process). I don't want you to waste your time since they are getting updated anyway. Thanks for your efforts! Cheers!

Elteria Shadowhand   [talk]

22:47, 7 August 2022 (UTC)

Template:VendorSells, Template:Sellsitem and subobjects

Heya Easton. You're a genius. I've looked for several hours of a way to realise that in wikicode only, and then switched to js. However I've got some questions. As far as I understand the new approach, the Record Property:OffersItem has become obsolete. Did you leave it in for a purpose? |sort = Is offered by.Port, Is offered by.Has query is a riddle to me. Sorting by port, that's fine. But why would we want to sort by an existing subobject? At this point we have at least one subobject due to the query selector '{{#ask:[[Offers::{{PAGENAME}}]]'. I've learned something new from you, yay and thanks!

Elteria Shadowhand   [talk]

12:07, 3 October 2022 (UTC)

Thanks, happy to help!

You're right, Property:OffersItem is redundant with the new subobjects. I didn't want to delete the property yet, because I wasn't sure if it was used somewhere else. If it isn't used, it's safe to delete.

The sorting was a hack. I wanted to preserve the same sorting as before: location, then NPC name. "Is offered by.Port, Is offered by" and "Is offered by.Port, " didn't work. "Is offered by.Has query" has the same name as the NPC and worked for some reason. I'll redo it in a different, less hacky way. Easton West (talk) 22:32, 3 October 2022 (UTC)

Thanks for the heads up. OffersItem is indeed only used here so it's safe to get rid of it.

Elteria Shadowhand   [talk]

22:35, 3 October 2022 (UTC)

Interface Admin

I gave you access to edit css and js files.

Elteria Shadowhand   [talk]

13:55, 3 October 2022 (UTC)

Template:NPC Summary parenthesis names

Hiya Easton, I'm not sure if this may come into conflict some day, if we remove the parenthesis'ed part on NPC names. One example I could think of is Khemarius. He isn't a Vendor at all, but he got several locations he can pop up which are put into parenthesis. In theory, each of those NPCs could offer items individually. Is there any point I don't see why we remove the parenthesis for the NPC names?

Elteria Shadowhand   [talk]

11:13, 4 October 2022 (UTC)

@Elteria I think it's good to have the unmodified in-game name stored as data — it could be useful for "see also", "same name, different article" links, or other purposes later. You're right that the #ask query for Template:VendorSells needs to be the article name (with parentheses). I couldn't get the article name to work for #ask sorting, though, so having the NPC name was useful for that. Easton West (talk) 18:28, 4 October 2022 (UTC)

Okay let's stick with that then. Ummm.. for the name sorting I riddled a bit myself, you're totally correct to set the name. It's the only way since #ask queries can only be sorted by a defined property. Only exception is the article name itself, which we don't use in that scenario ('Sort= ' or 'Sort=Is offered by.Port, ', mind the blanks) I guess you know that trick already.

Elteria Shadowhand   [talk]

20:03, 4 October 2022 (UTC)

Obsolete templates

Hiya Easton, if you find a template becomes obsolete (referring to the lootlists you commented out), leave me a short message. I'll try to find a way to remove them from all articles by scripting. Thanks!

Elteria Shadowhand   [talk]

16:00, 6 November 2022 (UTC)

@Elteria Sure no problem. I wasn't 100% sure about the loot, but if you can confirm it's not loot, then all good. Easton West (talk) 23:52, 6 November 2022 (UTC)

Hiya, what did you mean with 'loot' in particular? As fas as I know, only formulas and techs were removed from the loot tables.

Elteria Shadowhand   [talk]

13:37, 7 November 2022 (UTC)

@Elteria OK sounds good, that's what I thought too. (At least for T1 and T2, I'm low level.) Easton West (talk) 06:36, 8 November 2022 (UTC)

Hint for the tiers

Hiya Easton, for the tiers on pages, the tier is determined using the highest minimal skill needed. For example, at Dim Kinetic Suspension, Water needs a skill of 400, which is tier 3. Usually that's beneath every logic, because Dim stuff should be considered tier 1, thats weird game design.

Elteria Shadowhand   [talk]

01:10, 11 November 2022 (UTC)

@Elteria Ah that's a good point, I should've checked that. And I'm glad I did. The skill requirements seem to be incorrect, so I'll update them. Easton West (talk) 12:43, 11 November 2022 (UTC)

@Elteria Oh, this is weird. The skill requirement is different between Beginner Cognitive Suspension and Journeyman Cognitive Suspension. I guess Expert Cognitive Suspension is bugged too. I edited the T1 and T2 suspensions to match the beginner formula, and the T3 and T4 suspensions to match journeyman. But it's still weird... Easton West (talk) 10:58, 12 November 2022 (UTC)