Would this be a good feature for MobaFire?
The feature idea is cool and it's neat to have something like this easily visualized with code, but from the perspective of a player who has played the role a lot I really dislike the concept of a pre-set jungle path for the following reasons:
Basically what I'm trying to say here is that jungling is too complicated of a thing to have in a cheat sheet. It's very situational what you do, where you go, and how you clear the camps; encouraging linear gameplay in this area is something I don't want to see happen, and even if that's not the intention of this planner, it's definitely going to end up being used and interpreted in that fashion because it's like trying to summarize a huge complicated flowchart in one sentence.
- For one, a specific clear order encourages players to not gank until specific camps have been cleared. On the other hand, it also encourages players to gank after specific camps have been cleared, even if lanes are not overextended. No matter how much you elaborate on this in the guide body, people WILL tl;dr the guide and do what any site cheat sheet tells them to do.
- On the same token, some players may try to jungle without optimal runes/masteries, hit 100 HP, then still try to gank because the guide told them to; they will feed then downvote the guide.
- There's not enough space in the infographic to tell players the various different choices on what to do after a gank.
- It doesn't tell players how to properly counterjungle in specific jungle matchups (e.g. take blue, then enemy red vs. slow clearers who start blue, take enemy wraiths if you know they went to double golems).
- It doesn't tell players what to do if they got counterjungled early and didn't hit the right XP levels.
Basically what I'm trying to say here is that jungling is too complicated of a thing to have in a cheat sheet. It's very situational what you do, where you go, and how you clear the camps; encouraging linear gameplay in this area is something I don't want to see happen, and even if that's not the intention of this planner, it's definitely going to end up being used and interpreted in that fashion because it's like trying to summarize a huge complicated flowchart in one sentence.
From what I understood what Jhoi was saying, she was talking about when you write about your jungle route in your guide to have something like what she posted. And your other points will always happen, with or without a visual jungle route.

If I helped you, click that +rep!
I don't like putting "jungle routes", it gives a lot of new junglers the wrong understanding of your job as a jungler :(
Sorry, to clarify, there are these tools on MobaFire:
http://www.mobafire.com/league-of-legends/item-purchase-planner
http://www.mobafire.com/league-of-legends/rune-page-planner
http://www.mobafire.com/league-of-legends/mastery-tree-planner
I'm proposing a fourth tool that allows you to display jungle paths. I didn't mean this would be in the cheat sheet :)
http://www.mobafire.com/league-of-legends/item-purchase-planner
http://www.mobafire.com/league-of-legends/rune-page-planner
http://www.mobafire.com/league-of-legends/mastery-tree-planner
I'm proposing a fourth tool that allows you to display jungle paths. I didn't mean this would be in the cheat sheet :)
Jpikachu1999 wrote:
And your other points will always happen, with or without a visual jungle route.
This is true, hmm... I suppose it can't be helped. Go for it jhoijhoi!
****!!! I voted no!!! Noooooooo
+1 Rep me if you think I help you or others or don't
Pick A Card.
... Man I used to say that stuff. It's been years.

... Man I used to say that stuff. It's been years.

You need to log in before commenting.
Here's a mock up. Doesn't have to be as intricate (I just liked the idea of adding symbols), and of course professional designers can make it look much better.
While we're on the topic of the mastery/rune/item planners, I'd just like to point out that the instructions are worded poorly and there are typos present. At the very least, these need to be rewritten, lol.