Welcome!

I'm coming for you. :D

It will be coming out as soon as the Alpha Beta Pruning has been implemented. So, I've got good news and bad news. The good news is that I'm in the process of rewriting this bot from the ground up. So not only will it be fully functional again, but I should also be able to finish a few extra...

Special mining is for things like lava flow, motherload and shooting stars. Those were never implemented. There is no paid version of the script.

The admins and owners of the site do not really write bots, you'll need to convince the Both Authors to write them. The only issue is that RM has pretty high expectations for premium bots and it's quite a bit of work to not only write a great product from the start, but also to maintain it.

I think that since all of the calls are going to end up being to the API in the end, they will originate from the caller's thread id like normal. It's really just storing a reference to the enum's task, and if you look at the example, it's a very simple one that doesn't store any data in the...

I thought RM used different VMs for each bot instance, which is how the API is static in the first place.

Yes, with a little bit of helper code, each file is only about 30-40 lines of code for this simple example. For static trees (ones that will never have any nodes swapped based on the game type or anything else) it works very well and is cleanly readable. Check it out now that it was pulled into...

Updated with @Qosmiof2 example in the main post.

I added an example implementation using enums to define the branches and leaves. Hopefully @Qosmiof2 will pull them into his repo soon, if not, feel free to check out my fork.

Thanks for making this. I'm going to use it as my example for balancing trees. Also I think there is a bit cleaner way to build the tree using lambda functions that doesn't require as many files. I think it's the perfect size for a springboard example just to get author's feet wet. Also, I...

Yeah, makes me sad. On a side note @Cloud what about priority/expedited approval for premium scripts?

One one extra revision needs to be compiled. If it fails for any reason, then no beta will be available. I don't see the security concern at all. You should already have automated detection in place to detection things like the Reflection packages being used. It would be a use at your own risk...

I'd like to see it open to all users so I can get the most people throwing test cases and runtime at my bot.

I think it's also a use at your own risk feature, which is why there would be a big warning when a user selects the feature.

Maybe there could be a trusted author rank that would be allowed to use this. There are a few of us who commit consistently good code, and the bot would still need to be approved when it becomes the current version.

Can you please add a checkbox for users that will enable a "Beta Mode" for a Bot? What is beta mode? Beta mode would be a version of the bot that is compiled from the head of the author's SVN repo instead of from the revision that they have pushed into the queue. Why do I want this? I want to...

Support. Please get my shitty outdated script off the front page! @Arbiter plz.

Can you also add the option for a quick interact? This option would obviously not be used for every interaction, but it would provide a way to designate that the Bot needs a short, almost straight line mouse path. When I was writing a combat bot a while ago the interaction's slow response time...

I finished the API write up, but then hit back and lost it. I don't feel like rewriting it all right now, but I put the links to the API back in and there are moderate descriptions on those pages for anyone interested. I would love to see any specific questions that you guys have so I can be...