First off, I just want to say I'm posting from a forums-only account because I have no idea how to log in using my steam account.
I'm looking to learn C# or something over the summer and the pet project I chose out of my brainstorm is going to be based on Spiral Knights.
The first one I plan on pumping out won't need any type of parser... just manual fields to help track your mist energy regeneration. Just maths and such. I already have it working in excel but want to give it a neat GUI and whatnot... but that's not the point. As I think more on this idea, I realize that I could make this mini app a lot more useful if
a) I could get it to call information from the game automatically (for your Mist Energy level)
b) Get it to sync with a group of friends so you and a friend (would have to be a mutual thing) could see each other's current energy and play together when you have enough (probably only more useful for newer players, but the point of developing this is because I can, not necessarily because it is useful to everyone)
After accepting the idea of integrating this type of thing with the game, I started to think... What about a mini-armory type of deal where you can check your arsenal/inventory out of the game (not only gear equipped, but materials and tokens too)? Tracking your Crowns? Tracking your Crystal + Mist Energy?
Taking it even FURTHER, why not just work on a full-on parser that can track which gate terminal you take in the arcade, which maps you end up going in, and how many crowns you gain and how much energy you spend?
So, what I want to know from SK Tech Support... If I was going to work on something like this, are there any tools/resources from your end that would help me? Would running a parser that checks server data (assuming it's server data since mist energy is updated in real time) be a bannable thing that I shouldn't pursue? ... Really anything you can tell me about "Yeah, okay, that'd be cool" or "No, that's against our ToS" would be helpful.
Thanks in advance!
"No, that's against our ToS" - I think that's the statement you'll be looking at right now. Mostly points 6.1 and 6.13 I'd say.