Forum:Add drop tables on item pages

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > Add drop tables on item pages
Archive
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 29 January 2011 by Liquidhelium.

Proposal: Add drop logs on item pages, like how drop logs on monster pages work now. It would be in a table looking like this(for dragon boots):

Monster Combat level Quantity Rarity
Nex 1001 5 Uncommon
Spiritual mage 100-123 1 Rare

etc.

I think this would be useful to make finding information a lot easier.

Discussion

Strong support - Per nom JOEYTJE50TALKpull my finger 11:14, January 11, 2011 (UTC)

Comment How do you propose doing that for gems, or herbs? 16px‎AtlandyBeer.png 14:33, January 11, 2011 (UTC)

Not all items need have drop tables on them. At the least, a drop table with the x most frequent droppers could be added. Gems along with key halves and stuff could, instead of having drop rates for that item, have the rarity that NPCs drop from the 'rares' table, or a link to the appropriate page with such a table on it. --Dungeoneering-icon.png Deathslayer Fishing-icon.png 15:26, January 11, 2011 (UTC)
Items from the Rare drop table will not be included with this. Those are dropped by SO many monsters it is almost impossible to make the list complete. For that people can look at the list of monsters on the page. JOEYTJE50TALKpull my finger 17:45, January 11, 2011 (UTC)

Weak support - It's going to be difficult, even with some items not on the rare drop table, like herbs and seeds, a lot of armour, etc, although I see how it would be useful if we did it. Real Crazy 17:47, January 11, 2011 (UTC)

Support - Sure. bad_fetustalk 18:11, January 11, 2011 (UTC)

Comment - I like the idea, but there would be some redundancy by including the rarity column. If you can't pull the rarity from the respective drop table, then it shouldn't be added since there would be a lot of potential of mis-matched rarities. Farming cape (t).png Lil cloud 9 Talk 18:20, January 11, 2011 (UTC)

We could just transfer the rarities from the monster pages, and if they are not filled in yet, we just leave it open. JOEYTJE50TALKpull my finger 20:10, January 11, 2011 (UTC)
What I believe they mean is that having multiple entries of a value would cause inconsistancy - you'd be declaring the drop rate on more than one page, and so different pages could contradict each other. --Dungeoneering-icon.png Deathslayer Fishing-icon.png 20:30, January 11, 2011 (UTC)
Hmm yes, there should actually be a main page, like "Drops:Monster" where the data is stored. But, this might create so much work, we might wanna start with just manually transferring it first, and later we can do that. Then my drop logs project might have collected enough drops to be used to support the rarity of items. JOEYTJE50TALKpull my finger 21:01, January 11, 2011 (UTC)

Conditional support - Having categories of types of monsters, as well as making it collapsible is necessary in most cases. Additionally, I think this would be possible using bots, and much simpler. Quest point cape.pngTalk Newbie856 edit count Nomad guideMusic icon.png 21:44, January 11, 2011 (UTC)

It would use the same categorising as on monsters. If there are too few good categories they can be placed in, they are just put in one table. And I'll ask Q about that bot part. JOEYTJE50TALKpull my finger 21:52, January 11, 2011 (UTC)
What I meant for categories was something like this (using bread as a random, fictional example)
Dropped by (lvl 2 header):
Level 1-50 monsters (lvl 3 header):
Monster Combat level Quantity Rarity
Cow 1001 5635 Uncommon
Chicken 3 5 Rare
Bosses (lvl 3 header):
Monster Combat level Quantity Rarity
Nex 1 1 Uncommon

 —The preceding unsigned comment was added by Newbie856 (talk).

Support - Would be useful but a hell of a lot of work. You could say for rare drop table stuff, "This item is part of the rare drop table, a list of monsters that have access to the table can be found here." Hunter cape (t).png Sentra246Blue hallowe'en mask.png 01:48, January 12, 2011 (UTC)

Ye, thats a table with monsters having access to the drops table. In real, there are lots more, but not listed there. Those just monsters likely to give access to it. It's just impractical to list such items(same for items that are on the lists at Template:Dungeoneering droptable) JOEYTJE50TALKpull my finger 09:46, January 12, 2011 (UTC)

Support - As long as we do a proper job where the tables automatically update as new monsters are released which drop them. While preventing missing information and inaccuracies. 222 talk 01:50, January 12, 2011 (UTC)

Comment - To further elaborate on my point earlier, Dragon boots is contained inside a template (namely DropsLine). It shouldn't be too difficult to develop a short line of code to fetch the rarity on the pages like Nex and Spiritual Mage. Once that's worked out, I'll support this. Farming cape (t).png Lil cloud 9 Talk 02:24, January 12, 2011 (UTC)

Ye, that's not really hard to make. It would be using {{#explode}}. The problem is that you transclude the whole page then. That gives the same issue as at Forum:Simplifying all infoboxes, and we just can't do it. And btw, it would require really much loading to let it check ALL pages with {{DropsLine}} on it if it includes an item. We would have to load 750 pages (or so) for just one item page. For each item page. It is just impractical to automate it that way. Oh and working with something that makes the item tables the only part of the page which is transcluded is also impossible, as it is not possible to transclude <noinclude>, <includeonly> and <onlyinclude> tags.  —The preceding unsigned comment was added by Joeytje50 (talk).
Is it just me, or do you love the {{#explode function? 222 talk 10:05, January 12, 2011 (UTC)
It would be useful, but like i said it would have to load hundreds of pages for the price of one, it is not practical here. And yes, i do love the #explode function, as it makes magic possible OMG! JOEYTJE50TALKpull my finger 11:51, January 12, 2011 (UTC)
Then make it efficient by only checking the ones you want. Farming cape (t).png Lil cloud 9 Talk 18:16, January 12, 2011 (UTC)
How? That would be possible if we manually enter the monster names. As we could then as well just fill in the thing, it it kind of useless. To make such a list automatically, we need to check all pages if they got the drop in the table. It's just so enormously much loading(for each monster that drops it we would have to load another page, even if we manually make the list). It is just impractical. We have to do the work, or *maybe* a bot can do it. JOEYTJE50TALKpull my finger 22:29, January 12, 2011 (UTC)
Bots *can* do it, they are magic gods or something :P. In all honesty, it seems like something a bot can do, using the text info located in the DropsLine as well as the infobox (for the level(, it can read through it and write the MonstersLine (or some other name) template consequently. Just need someone willing to write the code. Quest point cape.pngTalk Newbie856 edit count Nomad guideMusic icon.png 02:31, January 13, 2011 (UTC)
According to evil we "really shouldn't expect someone else's bot to do a job unless they say they can get it to do what you want and would be willing to get it done." I asked Q though, (thats why evil said that) so if he has time to programthe bot, he could let his bot do it. I don't know stuff about bots, so here i can't help you. JOEYTJE50TALKpull my finger 11:53, January 13, 2011 (UTC)

Neutral - Per Real Not Pure. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 12:52, January 15, 2011 (UTC)

Support - As long as we use a bit of common sense when deciding what items need tables - [Pharos] iPhone Edit 12:07, January 16, 2011 (UTC)

Strong support - I actually had something liek that in my sandbox I was working on but I couldn't figure out the coding. Matt (t) 03:01, January 23, 2011 (UTC)

Closed - Drop tables will be added to items that aren't considered rares. Basically, that includes items that are dropped by a low enough number of monsters such that it can be chronicled in a table of reasonable length. There will be a lot of common sense involved. So, for example, adding a drop table to Bones is not appropriate, while adding one to Cowhide would be. --LiquidTalk 03:26, January 29, 2011 (UTC)