While this could be a good idea, I can give you some reasons why this isn't happening.
1. HUGE Database. This will not only increase the size of the database, but it will also clutter the items page (you'll want to be able to reach all of them, right?).
2. Outdated guides are outdated for a reason - they no longer reflect the best way to play a champion. Sure, there might be some useful info in there, but it's like having to go in the sewers to search for a well preserved hamburger; You can probably find a hamburger just as nice in a somewhat cleaner place.
1. HUGE Database. This will not only increase the size of the database, but it will also clutter the items page (you'll want to be able to reach all of them, right?).
2. Outdated guides are outdated for a reason - they no longer reflect the best way to play a champion. Sure, there might be some useful info in there, but it's like having to go in the sewers to search for a well preserved hamburger; You can probably find a hamburger just as nice in a somewhat cleaner place.
DuffTime wrote:
ok ok plz carry me omg
i was only waiting for you to ask
Temzilla wrote:
Too hot to be icecream.
Luther3000 wrote:
He looks like a hair gel advert on legs
Toshabi wrote:
Icecreamy, with hair as slick and smooth as the ocean waves of Cocobana
(I think the +rep threshold needs to be increased) I like your idea, Serag, but like Chris said, it'd clutter the database completely. Items get patched all the time.
A spin off would be to increase the staleness of the guide if it an item is changed. So for instance, if they adjust Trinkets, all guides with Trinkets are become "Fresh" when the database item is updated.
Don't know how hard that'd be to implement, though.
A spin off would be to increase the staleness of the guide if it an item is changed. So for instance, if they adjust Trinkets, all guides with Trinkets are become "Fresh" when the database item is updated.
Don't know how hard that'd be to implement, though.
That could be a good idea too, but then again you might just as well change the staleness of all guides :P Plus, it happens that someone [me :(] makes a mistake, and that an item is edited later. Kinda lame if a correction would mean hundreds of guides are suddenly not "fresh" anymore...
DuffTime wrote:
ok ok plz carry me omg
i was only waiting for you to ask
Temzilla wrote:
Too hot to be icecream.
Luther3000 wrote:
He looks like a hair gel advert on legs
Toshabi wrote:
Icecreamy, with hair as slick and smooth as the ocean waves of Cocobana
I'd love it if there was an "archive" of the items too. Or even champion abilities.
Force of Nature being gone as well as Heart of gold and all of old Katarina's skills is sad, and we have literally no record of them since they're not in the database anymore.
What I'd propose, is a "patch filter" for each item. Every time we update an item, it can get a new "patch log" that will outdate all guides with that item in the build order. Same with skills, runes, masteries, and so on. However if we just make a small tweak to an item/skill, say a number is messed up and a patch didn't change it, we could choose to have it not get a new "patch log" and guides wouldn't be outdated. All the "patch logs" would be easily viewable for record keeping.
Thoughts?
Force of Nature being gone as well as Heart of gold and all of old Katarina's skills is sad, and we have literally no record of them since they're not in the database anymore.
What I'd propose, is a "patch filter" for each item. Every time we update an item, it can get a new "patch log" that will outdate all guides with that item in the build order. Same with skills, runes, masteries, and so on. However if we just make a small tweak to an item/skill, say a number is messed up and a patch didn't change it, we could choose to have it not get a new "patch log" and guides wouldn't be outdated. All the "patch logs" would be easily viewable for record keeping.
Thoughts?

They are actually still in the database, they're just not visible since there's no reason for anyone to use them.
Force of Nature
Btw,
Heart of Gold is still able for purchase in TT I believe :)

Btw,

DuffTime wrote:
ok ok plz carry me omg
i was only waiting for you to ask
Temzilla wrote:
Too hot to be icecream.
Luther3000 wrote:
He looks like a hair gel advert on legs
Toshabi wrote:
Icecreamy, with hair as slick and smooth as the ocean waves of Cocobana
IceCreamy wrote:
While this could be a good idea, I can give you some reasons why this isn't happening.
1. HUGE Database. This will not only increase the size of the database, but it will also clutter the items page (you'll want to be able to reach all of them, right?).
2. Outdated guides are outdated for a reason - they no longer reflect the best way to play a champion. Sure, there might be some useful info in there, but it's like having to go in the sewers to search for a well preserved hamburger; You can probably find a hamburger just as nice in a somewhat cleaner place.
IceCreamy wrote:
They are actually still in the database, they're just not visible since there's no reason for anyone to use them.

Btw,

1- I don't think the database size would really bloat THAT much, specially that as you mentioned, removed items are still there for reference. And although I of course would expect to have access to all the versions of an item, but again as per your example, it doesn't need to be easy. It just need to remain behind.
As I can now see, linking an item is just as easy as typing its' name within a couple of square brackets, this wont remain the same though, and some way would need to be figured out to make it easy without defeating the whole purpose, or over complicating the author's life....
2- Well, I usually only checked the first three highest ranking guides or something, and all post S3 (at the time), yet quite a bit of guides had some discrepancies in the body that didn't make sense, until I found another guide that hinted that the items in question got changed, and then I didn't even get what the changes were to begin with.
If you did a database entry for every patch change, yes there would get to be way too many database entries.
The items that were removed from game don't show in the database to avoid confusing new players. They are all still there, just hidden, but even if we show them their recipes will eventually get messed up if their components have their recipe changed or their components are changed.
We could still possibly have a way to filter to include outdated items, just not include it by default for the new players.
The items that were removed from game don't show in the database to avoid confusing new players. They are all still there, just hidden, but even if we show them their recipes will eventually get messed up if their components have their recipe changed or their components are changed.
We could still possibly have a way to filter to include outdated items, just not include it by default for the new players.

Thanks to GrandMasterD for my sig!
IceCreamy wrote:
They are actually still in the database, they're just not visible since there's no reason for anyone to use them.

Btw,

Do

You need to log in before commenting.
While I've seen the post about the new way of decaying the votes by time, but I found that some outdated guides were quite helpful, when one got the context of the author, at the time of writing the guide.
So, what I'm purposing, is to keep different copies of the same item, one for each patch change, indicating the stats at the patch number and date.
eg: +100 Armor, 3.14.13_11_19_11_32, last change date, Up to date (True) || eg: +120 Armor, 3.14.13_11_19_11_21, last change date, Up to date (False)
This way, when a guide is written, only the current version of the item is linked, allowing the reader to know when something is outdated, With the Up to date field (False), and forcing the author to update the items throughout the text, if not relevant anymore.
And, discussion on the items, will be apparently either talking on the new or old version of the item, since each would have its' own page....
More or less, I propose archiving the old stats, instead of just "Updating" them.