The God Complex - Single "God Mode" Champion Settings
#31
what we really need is a simple database/page to feed the data in universally and let things like monolith, etc. sort out the incoming data feed (something trivial to anyone with minimal coding skills.)

That way it remains agnostic to the technology and can benefit everyone. At the very least I would prefer to see a simple database page that could be searched for a champion and/or add a particular key or key(s) to a champion, while I know sida does this with Monolith I feel it would ultimately be best served as a service that any user can consume and not tied to one application or one persons time.

I know everyone's time and focuses change and that there are multiple League of Legends projects that some of us are participating in or working on, hence my suggestion for a central repository/db, but unspecific to a tool or utility (I too have started to use Monolith, but for something like this I think data should be in one place and freely accessible to all.)

--------
I don't often contribute to anything....but when I do....
Bob Ross Approves of this happy little link....
Reply
#32
(11-24-2012, 03:44 AM)fragma Wrote: what we really need is a simple database/page to feed the data in universally and let things like monolith, etc. sort out the incoming data feed (something trivial to anyone with minimal coding skills.)

That way it remains agnostic to the technology and can benefit everyone. At the very least I would prefer to see a simple database page that could be searched for a champion and/or add a particular key or key(s) to a champion, while I know sida does this with Monolith I feel it would ultimately be best served as a service that any user can consume and not tied to one application or one persons time.

I know everyone's time and focuses change and that there are multiple League of Legends projects that some of us are participating in or working on, hence my suggestion for a central repository/db, but unspecific to a tool or utility (I too have started to use Monolith, but for something like this I think data should be in one place and freely accessible to all.)

I'm extremely busy with University work at the moment, but once I have time I could look into making the data publicly available by splitting the source to multiple locations, one specifically for Monolith (logins etc) and one for the setting data. The problem however if anyone is allowed access is that it could, and probably would, compromise the integrity of the data (IDs, keys etc). Applications like monolith would completely explode if users were allowed to add/edit data in any format they wish.

The best option would be an API that allows other applications to query the existing Monolith data source, however like I said I currently don't have time for that. If someone would like to take on the task then feel free to contact me.
[Image: 2m34408.png]
A good developer looks both ways before crossing a one-way street.
Reply
#33
what about a second option....a meta-database that allows users to submit and/or vote/accept particular champion settings, etc. essentially a raw layer for champ settings, user submissions, testing, etc. (your case where multiple updates will happen) and then that would become the world-accessible settings and library for apps/people to readily consume...

On top of that, add a user abstraction or voting/popularity field or something, and you could tag that data as the "best" or "most used" champion settings within that database. Just spitballing here but your point of being busy with school etc. is exactly why I was pointing out a universally agnostic DB.
--------
I don't often contribute to anything....but when I do....
Bob Ross Approves of this happy little link....
Reply
#34
(11-24-2012, 05:45 AM)fragma Wrote: what about a second option....a meta-database that allows users to submit and/or vote/accept particular champion settings, etc. essentially a raw layer for champ settings, user submissions, testing, etc. (your case where multiple updates will happen) and then that would become the world-accessible settings and library for apps/people to readily consume...

On top of that, add a user abstraction or voting/popularity field or something, and you could tag that data as the "best" or "most used" champion settings within that database. Just spitballing here but your point of being busy with school etc. is exactly why I was pointing out a universally agnostic DB.

Well users can already add/modify settings if they request a login. It shouldn't matter how busy I am, people can continue to add settings without me. The only benefit I see with an external settings source is the ability for other applications to use it. For now if someone is thinking of creating an application then I'll give them access to the Monolith settings source but I'm not seeing how having access to a plain text version of what's in monolith is going to be an advantage for standard users?

Thing such as voting etc would be features of an application rather than a plain text db. I dunno if I'm just being a derp but I'm missing the point of what you're asking for.
[Image: 2m34408.png]
A good developer looks both ways before crossing a one-way street.
Reply
#35
Nah I'm probably being a derp, I"m trying to find a happy medium, something that allows folks to generically crowdsource potential configurations that are leaguebot specific only, from there the notion of an additional abstraction layer was really just pie in the sky for trying to weed out the numerous one-off champion settings folks submit from time to time that aren't nearly as effective as previously developed settings.

While I know the spreadsheet is not a good source that was what it attempted to become was a generic one-stop repository for all of the champions, that aside, ANY source that was read only for others to consume would be a great start, I was just saying a generic database similar to what was previously done on google docs, that was continuous and MUCH easier to use/input data (as well as export it) would be fantastic and welcome.

A 'popularity' tracking/comment/voting feature that possibly was available to all as a function of that data would also be useful to folks attempting to find the most prevalent and useful champion settings vs. someone who submitted a series of 'test' settings that were never refined. Either way the goal is the same, a generic source for formulas and information that can be utilized by current and future applications for Leaguebot through export/API functionality.

My notion of filters wasn't much more than a suggestion and community benefit so that we could capture EVERYTHING current and legacy, but possibly only show what's valued or popular.
--------
I don't often contribute to anything....but when I do....
Bob Ross Approves of this happy little link....
Reply
#36
[Image: 2J7am.png]
What is the id/pw sida? D:
Reply
#37
[Image: zspu4adu.jpg]

Confirmed!

Gruß

Valdorian
---
---
[Image: 8j6g4vms.jpg]
Reply
#38
Just click cancel, but weird.
Reply
#39
Lol wtf. The site I got the images from must have added that crap.
[Image: 2m34408.png]
A good developer looks both ways before crossing a one-way street.
Reply




Users browsing this thread: 1 Guest(s)