For the past while now, I have been working on a guide to speedrunning Medabots Infinity. Although I intend to do a run of the game at some point (after improving the guide a ton [already started on that]), I'm mostly doing this because I want to see others running it.

Am I doing this for the wrong reason, or am I prying open the doors to a game that otherwise would have next to no info on it, and bringing it into the realm of possibility?

https://docs.google.com/document/d/1j7OueNrlEtLnxGiUUwWrRjLTMw3SEtNPjVLUtntr-2o

As long as you're trying to make a guide that's useful and accurate, I don't think the reason why you're doing it matters.

On a side note, it's important to realize that, as with any endeavor to make a speedgame more popular, this most likely won't result in more people running the game. Guides are always a great thing to have for people who are already interested in running it (and become more important as the run gets more optimized and complex), but if nobody wants to run the game, nobody's gonna run the game, guide or no guide. It's unfortunate, but it's just the reality of speedrunning small or obscure games.

I have no experience trying to develop a community but I can at least comment on the guide itself. I think a guide like this depends on the audience and the game. If you are trying to sell it to new people you should probably just make a speedrun so people can see it. I have never heard of the game personally. However even for people familiar with the game a guide like this should go into a lot of detail especially on the time saving explanations. For instance, you say an enemy can be stun locked but do not describe how to go about doing that. I would say that is a very important detail. You state how things are across from each other but do not describe exactly how that is or what order is the fastest. Sometimes you describe what to do like "get a headshot", but in 3d games how to do that can require more detail like where on the map you should have your character, when they should be there, what weapon to use, etc. I do like maps, I think those are important so that is a good thing to have. But having a video is worth a thousand words.

@theripper999 I understand what you're saying, but to address a couple things (and to highlight a couple things that I'll change):

thank you, I will add in that the damage animations are too long for those ones. For clarification, there is no trick to it, it's just shooting as fast as you can. the animations take that long.

as for split 9, that's why I included the map (and started to for the rest), the major points of interest are numbered in order. the mission (1) is required to open the door (2) that way you can press the last button to get to the goal (3). I will clarify that in the guide, but with the number of splits I didn't want to be too wordy.

as for the term "head shot" notice how I also mention left arm and right arm. that is because in this game there are 3 weapons equipped on your bot at a time, left arm, right arm, and head. when I say headshot, I'm not saying where on the opponent to hit, I'm saying which weapon to select. As for which weapon that is, the guide always uses the default, because as it says in the beginning (and I will clarify, thank you for pointing this problem out) there needs to be more research into the damage that each weapon deals, when you can get each weapon, and if it's worth the time to get them. On top of all the other variables (like lvl, and the stats of the opponent, which cannot be searched unless someone looks into the code of the game, etc.) there are just too many to test before the first run even happens.

I will keep your suggestions in mind, and I will make a video that explains a few things, but RN my main focus is on getting maps for each split, and refining any of the inaccurate observations (due to a lack of sample sizes).i.e. how AI behaves.