User talk:The scribe

From Old School RuneScape Wiki
Jump to: navigation, search
Wiki.png
Hello, The scribe, and welcome to the Old School RuneScape Wiki! We're happy to see new editors making contributions. Here are some links you may find helpful:
Please remember to log in every time you edit and sign any messages you leave by typing four tildes (~~~~); this automatically inserts your username and the date. If you have any issues, feel free to ask on the user help page, or join us on Discord, where many of our editors hang out.


We hope you like it here and decide to stay!

-- Recent uploads SpineTalkContribs 06:33, 8 October 2019 (UTC)

Discord[edit source]

Hey, appreciate the contributions you've made recently. If you have a Discord account, it would be helpful on occasion if you could join our server for discussion (for example I was gonna mass revert the bot edits removing <nowiki/> tags as they're at least most of the time used on purpose, and it would be quicker to communicate there to inform you). --laagone talk 22:50, 7 July 2020 (UTC)

Hi. Well, I noticed that I was a little too fast with some of the nowiki edits esp. places that combined something italics with an apostrophe and similar cases (wish I knew of an alternative to nowiki tags in that case), so I went back over each one and undid those that were bad. Those I left should have been fine I think. Sorry if it caused any problems, I'll be much more careful from now on. --The scribe (T | C) 23:17, 7 July 2020 (UTC)
No worries; for reference, the ones I just finished reverting were breaking bulleted lists in a template parameter (as in here) where the tag is used as a workaround to get around problems with formatting. --laagone talk 23:21, 7 July 2020 (UTC)
I see. I just tested the emergency break. It doesn't seem to stop edits done using JWB. :( --The scribe (T | C) 00:06, 8 July 2020 (UTC)

Re:Infotable Bonuses and sorting[edit source]

When you say multiple values, do you mean in the cases where there are multiple versions in the infobox? The way this is supposed to work is that the stats for each version get saved into a separate SMW subobject (see docs). For example, Guthan's warspear has properties set at different subobjects for the undamaged and damaged versions. This way dynamic tables like Two-handed slot table can list each subobject as a separate item.

Sorry for the delay, if you join our discord server there's a channel #wiki-tech where more people can see questions and answer much faster. Riblet15 (talk) 03:00, 19 July 2020 (UTC)

Yes, I'm talking about items that have multiple versions in the infobox. Thanks for the explanation of how the data is organized, it does clear things up for me.
Unrelated to this I now also understand why the SMW query at the Staves page failed. Not because it was too large (since the 'Slottable' module submits a much larger query), but rather because I submitted a query with too many pages in the page selection part of the query.
But back to the matter at hand. Looking at the main property page for Guthan's warspear, you see the cummulative attribute sets such as 'All Slash attack bonus' lists two values. This means that SMW basically can not reliably use this column for sorting. And pre-sorting is kind of important since the order in which modules gets their parameters is random, and only sorting by name is not desireable in many cases (see the Scimitar page for example, which is sorted by Strength). And the main item pages is how I go about selecting items to list. If I start listing all the sub-variants of items instead, I'm afraid that the page selection part of some queries might grow so large that I end up with the problem that SMW starts rejecting them. Besides for 'Infotable Bonuses' we're really only interested in the principal variant of an item and can ignore all the others. --The scribe (T | C) 13:58, 19 July 2020 (UTC)
I'm not sure the best way to figure this out from lua, but the "principal variant" will always be one of the subobjects defined on the page. By default, it will be version1, but this can be changed using the defver param in the infobox. The subobject name will be ArticleName#VersionName, but this can also be changed using the smwname parameter. Attack potion is a complicated example, where the defver is set to 4 (version name = 4 dose), then the smwname4 is set to (4). So in this case the principal subobject would be Attack potion#(4).
In many cases, it should be possible to query for items instead of listing them all explicitly. For example on the spears table you could find all subobjects with Combat style set to "spear" (example). I think this would at least avoid the restriction you're running into about the query having too many items in it. I would probably recommend having all subobjects in the output, unless it ends up looking really bad.
I haven't tried this, but it's possible you could also get around the restriction by keeping each line of the infotable as a separate template. Instead of 1 query with N arguments you would have N queries, which may or may not bypass the SMW limits (I'm not sure if the limit is applied for a single query or for a single page render).
I really do recommend asking some questions in Discord, there are at least 5 people who have much more SMW experience than me and might have better suggestions. Riblet15 (talk) 18:14, 20 July 2020 (UTC)

Lua error[edit source]

Hey! I know you've been working on the Infobox Bonuses stuff as of late. I noticed on the Halberd page that there's now an error: Lua error in Module:Infotable_Bonuses at line 92: the number of sort orders must match the number of sort keys. When you have a moment can you investigate and remedy? Thanks! -Legaia2Pla · ʟ · 22:06, 21 July 2020 (UTC)

Whoops. I'll fix it immediately. Thanks for letting me know. --The scribe (T | C) 22:09, 21 July 2020 (UTC)
Seems to be sorted, thanks! -Legaia2Pla · ʟ · 23:09, 21 July 2020 (UTC)

<math>[edit source]

Hi, I hope things are going well! I have a few questions about the use of LaTeX on the wiki with a particular focus on the Energy page. (1) Why did you insert an align environment? This environment can be useful when there's more than one line of equations but isn't useful when there's only one equation. (2) Why did you restrict the domain of the function L to [0,64]? That mapping is correct with the domain you edited in, but players would want to know the mapping for any nonnegative weight. (3) Why did you remove the comma from the end of the mathematical expression and insert a colon at the end of the preceding english sentence? Math can be placed into sentences, and now the sentence doesn't make grammatical sense to me with the "where w is weight..." at the end. (4) Why did you replace \left\lfloor with \lfoor (and same with \right\rfloor to \rfloor)? The \left and \right delimiter counterparts are used to scale the the delimiter to the correct size. Heritability (talk) 19:05, 2 August 2020 (UTC)

The rollback on that page was accidental and I apologize for that. I have no reason in particular for my last edit other than aesthetics which isn't a good reason, so I'll make it simple and undo it. Hope that's satisfactory. --The scribe (T | C) 20:14, 2 August 2020 (UTC)
Okay, thanks! Perhaps we could reach out to the broader wiki community to see the formatting for math that is generally preferred? Also, what was the test that you did that lead you to conclude that the energy formula is "close enough" to correct? From my tests, it seems to be exactly correct. Heritability (talk) 22:04, 2 August 2020 (UTC)
I don't think there is a style guide at the moment, so it's mostly up to whoever is writing it. It should be possible to suggest a style guide on the Runescape:Active discussions page if you want to. What I've been doing lately is pulling out big formulas where it would disrupt the flow of text. Examples: Larran's key and Brimstone key. Latex support in Mediawiki is lacking a lot of features, but I've found that align gives a lot of flexibility with formatting, so I started using it a lot, even in places where I only needed some horisontal spacing. The test I did wasn't particularly accurate, hence the phrasing. --The scribe (T | C) 22:45, 2 August 2020 (UTC)
Those are interesting examples; thanks for sharing them! I think this could be a place where our preferences disagree. To me, the page shown here cPcivoZ.png looks better, since the reader doesn't have to read around a block of formulas in the middle of the page and keep up with which number references which formula. Do you prefer the page as it is currently formatted? (I'll keep these examples in mind when making a discussion for a style guide.) By the way, could you respond with whether you're on Discord? It would be more convenient I think to have some quick discussion there. Heritability (talk) 00:53, 3 August 2020 (UTC)
True, your example is more readable, like you said. What I was ultimately trying to avoid there is the look of the Brimstone key page as it was 25 June, with two big math blobs right in the middle of the sentences. But some pages looks nice even with inline math, such as Chaos Temple (hut), so it's a bit subjective... Another thing I believe is not good style can be found on the Combat level page - variables that are either words or multiple words. Using single letter variables like for instance, would make the formulas less cluttered, but then one has to describe what each variable is elsewhere. I guess that about covers what I think about style. If you want to, you can just change the style of those pages (as encouraged by RS:BB), I doubt anyone would mind, and it beats waiting while a style guide is submitted for approval. I'm not on Discord btw. --The scribe (T | C) 15:25, 3 August 2020 (UTC)
Okay, thanks for sharing those! Yeah, I agree with your sentiment about using single letter variables, I'm not sure what's best there. (One thing I don't at all like now is how so many equations are just having expressions like "", which is an inappropriate use of LaTeX since each character is treated as multiplying the others, rather than being treated as a word.) I'll make a post in the next few days seeking consensus about style for mathematical expressions. Tbh, I wasn't a big fan of the math on the Chaos Temple page, but I just edited it to include inline math mode, which imo makes the page much cleaner. Thanks for the update on Discord! Heritability (talk) 18:25, 3 August 2020 (UTC)

{{#if:{{{nocat|}}}[edit source]

Heya, was wondering about the templates such as {{Crop}} where you had added the bit {{#if:{{{nocat|}}} to them. What does this do instead of leaving them as mainonly because now they're causing other pages to show up in maintenance categories. The main offender is RuneScape:Images and media policy. If you could explain the changes and why they're necessary that'd be great, and further, if the chance is necessary, could we do something to prevent RS:Images and media policy from being categorised. Thanks! Legaia2Pla · ʟ · 00:41, 9 August 2020 (UTC)

Hi. Adding that parameter was a habit I developed after observing that some templates would fail to add a maintenance category outside of the main namespace. I forgot the specific template, but I remember adding a maintenance template to an article in the project namespace (Runescape) and not having it added to the maintenance category. Example uses of the templates (such as those on RS:Templates or template documentation pages) were supposed to set the parameter to true, I guess I overlooked a page, which is sloppy work on my part.
I guess some templates that won't ever be used for examples, or templates that is guaranteed not to have a use outside of their intended namespace(s) do not need such a parameter and would be better served by instead white/black-list certain namespaces. I don't mind doing the manual labour of adding that parameter to all the places where templates are being used as an example. But if there is a chance this could become a maintenance hassle going forward, perhaps the better option is to drop the parameter where it is appropriate. I guess for the Crop template and similar templates this is would be the best option.
I'll start by having a look at that page and either add the parameter or try to identify templates that might be better served by having the parameter removed. If you spot any templates other than the fileonly ones that probably don't need this parameter please give me a hint, so I can fix it up. --The scribe (T | C) 11:32, 9 August 2020 (UTC)
Thanks for addressing these; my apologies also for being misleading earlier when I said mainonly, I meant fileonly. :) Legaia2Pla · ʟ · 14:56, 9 August 2020 (UTC)

Slayer boss param[edit source]

Hi Scribe! I am a bit confused about the addition of the slayboss param to the Infobox Monster module. The edit comment says "add optional 'slayboss' parameter; this will allow the slayer category to be single-value", but adding the slayboss param doesn't actually solve that issue. See monsters like Vorkath which have two regular categories (zombie and blue dragon). There are also a variety of non-boss monsters that have this as well, like Demonic gorillas. If the goal is to get the slayer category to a single value, I don't think this approach will work. This fragments the slayer categories for monsters which can be a bit confusing imo, especially in cases where the slayer category is ONLY boss like Commander Zilyana since other boss monsters have had the Boss category moved to the new param but Zilyana has not. If I'm misinterpreting the end goal here, please let me know. Andmcadams (talk) 15:02, 4 September 2020 (UTC)

Hi. I brought up the issue before but didn't get any replies then. You're absolutely right, this unfortunately doesn't solve the issue, like I hoped it would. Single-value properties is neccessary for SMW selection and sorting. As a result the Slayer assignment pages in the Bestiary is kind of unfixable and has been for some time.
In the short term would you prefer I finish adding the parameters or should I just undo what I added so far?
In the long term I don't know what would be best, but I suspect storing all the slayer information in a central Lua repository instead of in infoboxes is the way to go. SMW just has too many annoying limitations. I'm really interested in what you think about this. A new slayer task bestiary can be generated from this data and I can probably make use of some of the stuff you wrote like slayer consts and the slayer library stuff. --The scribe (T | C) 15:52, 4 September 2020 (UTC)
I didn't see that talk page post before so thanks for pointing me to it. I totally agree it is a problem that there's no way to pull the slayer info when there are multiple categories. That was a big part of why I had to create the SlayerConsts module. Unfortunately, not being able to pull all the cats also made it a huge pain to figure out which monsters are actually in multiple categories. That's why Module:Master comparison calculator only handles some of the multi-task monsters in specialTable (in addition to not wanting to clutter the calculator). Not to mention the wiki is missing some of these secondary categories, and when they're updated the lua would have to be manually changed.
In the short term, I'd personally say undo is the way to go. I think that going further down this path won't bring much benefit, and might make the problem a bit harder to solve in the future if bot editing is involved since the case with the slayerboss param would have to be handled too.
As far as the longterm, I'm honestly not sure either. I'm not particularly well informed about the limitations of smw (or how the infobox module handles the cat param). I think it might be a good idea to make a discussion thread and see what others think. I'm more than happy to alter the slayer consts or library stuff to be a bit more flexible if that ends up being a direction we want to move in. It could be that once the Slayer Assignment pages are under active work (or completed) the needs might change, so it could be useful to look at it in the context of that too. Andmcadams (talk) 16:14, 4 September 2020 (UTC)
Did some more testing today and had an epic facepalm moment a revelation. Apparently SMW is not as hopeless as I had previously thought, and some these issues might turn out to be fixable after all. You see, the slayer category property doesn't really store multiple values, it stores a concatenation of values into one string value, therein lies the problem. Splitting these properties into multiple values does seem to allow them to be selected for in a query. Still IIRC this doesn't fix the problem of sorting, and properties with actual multiple values will remain unsortable. There should be ways around that however. --The scribe (T | C) 10:44, 5 September 2020 (UTC)
Well that's good to hear! By splitting do you mean creating multiple params (ie. cat1=Cow, cat2=Zombie, etc) or do you just mean splitting the concatted string on the ", " once it's received? If it's the former, I'd be a bit wary about monsters with switch infoboxes, since iirc the 1, 2, ...n params apply to those and could get messy/confusing on those pages. The latter sounds fine in the short term, but like you said, it's more of a workaround than a real solution. Andmcadams (talk) 14:48, 5 September 2020 (UTC)
The infobox module has functionality to split a property into multiple ones by a separator. All the tests I've done suggests it's a proper fix. Check the diff from the Aug.31 version. --The scribe (T | C) 15:19, 5 September 2020 (UTC)

DEFAULTSORT[edit source]

Is it possible to add that functionality to the infoboxes themselves, using the |name params? I'm not familiar enough with DPL/SMW stuff myself, but I figured you might know. -Towelcat (talk) 05:49, 6 September 2020 (UTC)

Hi. Well... I didn't actually know anything about either Lua, SMW, DPL or Infoboxes before I came here. I was just looking for interesting (and educational) projects and was willing to figure out things the hard way. I didn't even want to touch infoboxes, but apparently annoyance at broken things is a powerful motivator. :-)
As for DEFAULTSORT, I didn't know either, so I ran a series of tests to figure it out. Normally pre-processing happens before modules are called, but you can manually insert a call to DEFAULTSORT from within a module. See page sorting key tests.
But even if it is possible, should it be done? The number of pages that needs to have a manual sorting key applied is probably very low, unless you want to start sorting people on their surname first. Also a number of infoboxes will have to be updated. IIRC even the big english Wikipedia adds these tags manually. --The scribe (T | C) 12:14, 6 September 2020 (UTC)

max hit changes[edit source]

Hi, not sure if you already have a process for finding which max hits to fix. These are the ones my bot says might be worth checking:

  1. Abyssal Sire
  2. Adamant dragon
  3. Alchemical Hydra
  4. Black dragon
  5. Blue dragon
  6. Bronze dragon
  7. Callisto
  8. Cerberus
  9. Demonic gorilla
  10. Ice demon
  11. Karamel
  12. Lava dragon
  13. Muttadile
  14. Pestilent Bloat
  15. Scavenger runt
  16. Skeletal Mystic
  17. Vanstrom Klause
  18. Vasa Nistirio

Riblet15 (talk) 16:52, 7 September 2020 (UTC)

Nice. Thanks. --The scribe (T | C) 16:55, 7 September 2020 (UTC)

infobox smw[edit source]

What's the purpose of Property:Uses infobox? Do you have an example of when we would we need to know which infobox is setting the properties? Riblet15 (talk) 22:14, 8 September 2020 (UTC)

Historically "Uses infobox" replaced "Page type" and at the time it was only used by "Infobox Monster". It's purpose was important in providing a reliable way to query all the monsters in the game for use in the Bestiary. Since pages can use many infoboxes, "Page type" is a bad name since it implies a unique value.
Now categories are used for very much the same thing, and infoboxes often set them. But categories may be used on pages that's not exactly what you're looking for. Say you wanted to list all the items in the game you could have a look at Category:Items. However there's nothing preventing other articles from using that category for things that are items in some sense, but doesn't use Infobox items or is an actual game item.
It helps making things searchable, and while not every case might be useful today, who knows what use it can have in the future? I don't see any problems with setting this property. We categorize pages all the time, this is no different. It's just another way of selecting pages for generated lists. --The scribe (T | C) 23:35, 8 September 2020 (UTC)
Also I mentioned before that at least in the cases where SMW subobjects are used, the subobjects doesn't inherit the categories from the main page. So this is one instance where categories become useless.
 Category
Guard (Deadman Mode)#East Ardougne
Guard (Deadman Mode)#Falador
Guard (Deadman Mode)#Fremennik
Guard (Deadman Mode)#Fremennik 2
Guard (Deadman Mode)#Ghost guard
Guard (Deadman Mode)#Gnome guard
Guard (Deadman Mode)#Kourend guard
Guard (Deadman Mode)#Ranger
Guard (Deadman Mode)#Sophanem
Guard (Deadman Mode)#Varrock
JalTok-JadOld School-exclusive content
Slayer monsters
Inferno
Monsters
Phosani's NightmareOld School-exclusive content
Monsters
The Nightmare
Discontinued content
SotetsegBosses
Needs drop rarity added
Theatre of Blood
Monsters
Pages with drop log-supported drop tables
The Maiden of Sugadinti#30% Health
The Maiden of Sugadinti#50% Health
The Maiden of Sugadinti#70% Health
The Maiden of Sugadinti#Normal
TzKal-Zuk#Enraged
TzKal-Zuk#Normal
Verzik Vitur#Phase 1
Verzik Vitur#Phase 2
Verzik Vitur#Phase 3
XarpusBosses
Needs map
Incomplete references
Theatre of Blood
Monsters
Non-player characters
Needs options
There is no way to ask SMW to exclude the Guards from Deadman mode here. Categories doesn't help us, only a property will do in this case. --The scribe (T | C) 00:07, 9 September 2020 (UTC)
If you're worried about me adding properties willy-nilly, don't be. I wouldn't create a new property if there wasn't a clear use-case. In the case of 'Uses infobox', I just found new uses for an already existing property, although with a slightly different name at the time. --The scribe (T | C) 10:04, 9 September 2020 (UTC)
I also asked myself why would the original author of the Monster infobox use a property ('Page type' later 'Uses infobox') to select pages in the first place, after all SMW is capable of selecting using categories isn't it? The answer here is also subobjects. When you select using the property you get a list of all the subobjects, and if you used a category you would just get the list of pages without variants. Additionally there are more restrictions on categories that properties don't have, one example is that you can query based on a property not having a certain value, this is something you can not do with categories.
I had an idea last night that might address some of these issues, if it works like I hope it will. But for now that's off-topic. --The scribe (T | C) 11:46, 10 September 2020 (UTC)

Infobox Monster[edit source]

Heya,

Next time you plan on Infobox Monster could you give me a heads up? Changing the smw properties of Infobox Monster breaks our DPS Calculator script: https://oldschool.runescape.wiki/w/User:GauBot/Combat_Calculator/log.txt

Improving the smw isn't necessarily a bad thing - it's just that I need a heads up to make sure the calculator continues to run smoothly.

Cheers

--Gau Cho (talk) 14:29, 11 September 2020 (UTC)

Sorry. I thought I checked for possible breakage, I'm guessing I overlooked it because it sort of looks like a private calculator project that's not yet deployed?? I'll make sure to notify if I ever change a property. --The scribe (T | C) 15:01, 11 September 2020 (UTC)
Yeah it's a project in the works! It's been discussed a fair amount on the discord mainly (hope you'll join one day!) but hasn't received a lot of attention on the wiki proper yet. No worries! It was just a heads up for next time. I might modify your code a little bit here and there to make it compatible. Gau Cho (talk) 00:20, 12 September 2020 (UTC)

Bot task[edit source]

Hello! I was hoping you'd be able/willing to do a bot project for me. There's a lot of /doc pages on Special:WantedPages. I would love to have those created with {{No documentation}} in order to better categorise and track them. The issue is I can't easily do it with AWB. Let me know, thanks! -Legaia2Pla · ʟ · 17:29, 12 September 2020 (UTC)

Nevermind, someone saw this and gave me a DPL that made it possible... :P Legaia2Pla · ʟ · 17:59, 12 September 2020 (UTC)

Pugel[edit source]

Hi Scribe! I noticed you removed the infobox bonuses for pugel since the page said it wasn't equipable. While it is not equipable in the traditional sense (no equip option), it can be equipped by getting on the balance beam in the POH while a pugel is in the player's inventory. I added the infobox back and updated some info (including setting equipable = yes), as it appears the stats were changed and the attack style made to be unarmed. I'm going to update the prose as well, but thought I would let you know why I added it back first. I figure this meets the requirements to be considered "equipable" since similarly weird items like two barrels and dharok's greataxe 0 are considered equipable. If not, that's fine, but I thought I would try and clear up the confusion. Andmcadams (talk) 20:17, 18 September 2020 (UTC)

Thanks. I was trying to make sure the "Equipable item" category was consistent throughout the wiki. There's probably going to be a few changes I'm not 100% sure about, it'll probably state so in the log message if that's the case, so its nice to get them checked. Got about 15 more items to go over and check atm. --The scribe (T | C) 20:29, 18 September 2020 (UTC)
No problem! I updated the prose so it hopefully makes more sense now. As far as equipable items go, this is a topic that has apparently come up in the past on RS wiki. Not saying os wiki needs to stick to that, but it's clear different people have different ideas of what an equipable item is. It might be a good idea to make a forum post to try and establish some consensus so that people don't change what you've done, especially if you're going to be pulling this info somewhere else (not sure if that's your plan). Andmcadams (talk) 20:59, 18 September 2020 (UTC)

RE: RFD[edit source]

I figured on the strike through, so I left a message on the talk page, although it will likely go unseen since it is an IP edit. Badassiel 04:18, 22 September 2020 (UTC)

new infobox feature[edit source]

Gaz just added the ability to disable smw on individual articles by setting |smw = No, or |smwX = No if you only want to disable smw on version X. We should keep Infobox Bonuses on unobtainable items, but you can disable SMW so it won't show up in the equipment queries. Riblet15 (talk) 03:13, 23 September 2020 (UTC)

I see, thanks. This can be useful for Unobtanium items that are definitely never going to be on any lists. IIRC i only removed or replaced two infoboxes recently, I can go back thrugh the log and fix those now. --The scribe (T | C) 04:04, 23 September 2020 (UTC)
Oh, I see now I removed them earlier... I totally forgot about that. --The scribe (T | C) 04:11, 23 September 2020 (UTC)
Maybe I'm too tired, but I can't seem to get it to work when I tried it on the page A jester stick. --The scribe (T | C) 04:49, 23 September 2020 (UTC)
Ok, needs to be lowercase. That made me chuckle. --The scribe (T | C) 05:01, 23 September 2020 (UTC)
Makes sense, i'll ask gaz to support title case too since usually that's how we do params Riblet15 (talk) 05:22, 23 September 2020 (UTC)
Hey Scribe, would you be willing to revert the changes you did to "equippable=no"? If the item has a "Wield" option then equippable should be set to yes (see A jester stick here in our moid: https://chisel.weirdgloop.org/moid/osrsid.html#10840). Let me know if this makes sense. Cheers :) --Gau Cho (talk) 18:05, 23 September 2020 (UTC)
I'll do it this time, in the spirit of cooperation. You know... I did ask well in advance of making those changes, and got no reply. This is not the first time this has happened either. --The scribe (T | C) 00:18, 24 September 2020 (UTC)
Yeah I think there was suboptimal communication between the rest of the wiki team and yourself with respect to this. We did notice and appreciate all the work you did for the slot tables though. But yes there were a few dependancies that were broken because some people didn't notice what you were doing. I hope you're not too upset. I asked you to switch the equippable back to yes because I didn't want to blatantly revert a bunch of edits that you did. In order to get more attention for your projects, you could write a thread in Forum:Redwood_Grove. All threads get flagged in our discord so it's more likely to be seen and it has to at least eventually be responded by our bureacrats even if there's not much input.
That being said, I would strongly encourage you to join the Discord, even if you lurk and don't write in discord to us. A lot of discussion and projects these days bypasses the wiki proper: https://discord.gg/runescapewiki
I hope this clarifies things a bit. I'm not upset at you, and I don't think people are upset at you for the changes that were done, although we did prefer using smw=no to removing the Infoboxes (which we implemented to make sure both parties could be satisified). --Gau Cho (talk) 00:40, 24 September 2020 (UTC)

Weapon attack speed[edit source]

See my answer --Gau Cho (talk) 00:52, 24 September 2020 (UTC)

Do you want a free wiki t-shirt?[edit source]

Hi The scribe!

To celebrate the two-year anniversary of the new site, we're giving away RuneScape Wiki t-shirts to a bunch of wiki editors. Because of your contributions to the community over the last year, we'd like to send you one! If you're interested, go fill out this form, and we'll get those shipped out before the end of the month.

If you have any questions, shoot me a talk page message or a DM on Discord (Cook#2222). Thanks!

ʞooɔ 21:58, 2 October 2020 (UTC)

Black pickaxe[edit source]

Yo, I was just wondering if you may have accidentally removed the mention of beginner clues on this edit or if it was on purpose and there was something I didn't know? Mod Tide's tweet seems to show black pickaxe as a rare reward from them here. zTUG5mD.png Crow 653  02:50, 12 October 2020 (UTC)

I see. At the time I simply checked the page Treasure_chest_space which only listed it on easy tier. It's not necessary to message me for small fixups, a log message works nicely too. Have a nice day. --The scribe (T | C) 03:12, 12 October 2020 (UTC)

Property chaining[edit source]

Hey, that change to Get drop info is actually phenomenal. Doing repeated calls to mw.smw.ask is the single biggest source of latency on the wiki, so getting it down to a single call is a big deal. Are there other places we still do that? ʞooɔ 10:16, 19 October 2020 (UTC)

Oh. Thanks. That was a bit of a surprise. On osrswiki the two places I know that used several calls to mw.smw.ask() was 'Get drop info' and 'Store locations list' both which I added property chaining to. I just finished timing SMW, and for 'Get drop info' testing 'Grimy ranarr weed' it seems the elapsed time is still high and actually went up a bit, which is depressing. I'm guessing property chaining does not reduce the algorithmic complexity, or cache better, it's just an easier way of doing essentially the same operation.
I'm curious, does the site use a shared SQL database in the same datacenter? Or do you guys run everything on the same VPS/Dedicated server? Shared databases are horrible. --The scribe (T | C) 11:58, 19 October 2020 (UTC)

Beastiary attribute pages not listing vorkath[edit source]

As you can see on Vorkath, its attributes param is: |attributes = dragon,undead,fiery however it doesnt show up on Draconic (attribute), Fiery (attribute), or Undead (attribute). I'm not quite sure what the issue is by a cursory glance at the beastiary module and the other examples currently on the page. Would you talk a look and see if you can figure it out? Choppe|T 18:09, 13 November 2020 (UTC)

@Choppe: Sure. Judging from the edit history on undead attribute I guess you already figured out that the issue was caused by the exclusion of quest monsters. Weirdly enough this also seemed to affect the post-quest variant, I'm guessing thats an error in the infobox. I don't know you would prefer quest monsters to be listed in general, but feel free to change that. Will you do me a favour though, tell me if you received a notification message for this reply? Thanks. --The scribe (T | C) 16:45, 18 November 2020 (UTC)
I did not get a notification in my alerts, I know there is a way to trigger it, but I'm not sure why it didn't do so. I looked through the module and noticed Categories being checked, we talked about it in discord, wanting to add |quest = param to the infobox, but as there were multiple mentions in recently of vorkath not showing in the list I figured it was best to show quest monsters in the mean time. Thanks Choppe|T 16:55, 18 November 2020 (UTC)
I have never been on Discord. This is a personal choice which in my opinion I don't feel the need to defend, I also don't use Twitter, Facebook etc. If someone said they are me on Discord they are an impostor. I would also like to point out that the rules of this site seems to give you the opportunity to ban people who claim to be someone who they are not, in this case I would even encourage it. --The scribe (T | C) 17:24, 18 November 2020 (UTC)
Sorry, that was misinterpreted! I meant, I was talking to others about how to fix it, not someone claiming to be you. Again sorry.Choppe|T 17:26, 18 November 2020 (UTC)
Had another look. The exclusion lists uses categories which means that if one of the monsters is a quest monster, all the other variants are treated as such too. Just to be on the safe side I changed all of the attribute pages to include quest monsters. As for adding properties to the infobox, sure that will fix this proper, but there's a lot of categories that is used in the exclusion lists that could be turned into properties as well. IIRC some of these categories aren't all that accurate either. But that's a lot of work for little gain, but if someone is willing to put in the effort, sure why not. If this is something the wiki wants to do I could offer to write some bitmap code that will allow lots of booleans to be stored in one single property. in addition to compact storage this will also allow you to apply a bitmask to the results, in other words pick out or discard monsters that satisfies a range of attributes. While this might seem less flexible than excluding monsters already in the smw query, it might be a better way to exclude monsters after the query since in the future the full monster lists might be saved as JSON for speed reasons. --The scribe (T | C) 07:40, 19 November 2020 (UTC)
I appreciate the changes for the time being to make them accesible. I'll talk to some of the more technical people and ask them about what the best solution is.Choppe|T 08:09, 19 November 2020 (UTC)