Screeps api Offline#

We've developed an authentication tokens system to make this process easier for you. However, if you want to use undocumented HTTP endpoints which our server uses to communicate with the client, that's fine. Just an ideaвЂ¦ I guess there are a lot of possibilities.Screeps doesn't have a documented public Web API. Like it could refill faster by killing other creeps ^^ when and how it increases/reloads or how API call costs are calculated. This offers a lot of more options, regarding its implementation, e.g.

It could also be an option to introduce another currency, to be used for API calls to limit its use. IвЂ™d consider it more like Atavus calls it вЂњunfairвЂќ.ДЄnd in no way should the usage of given functions result in something like 'banning' (well, again except regarding exploits, explicit abuse.) Some things may be missing as well.Д«ut I wouldnвЂ™t call using powerful implementationsВ of given functions abusive, as it has that вЂњillegalвЂќ touch. So I am with W4rl0ck вЂ“ maybe we need a discussion about what should and what should not be possible to do with the API in terms of what it offers. This would mean there is no such thing like abusive use, except when using exploits or the like.Д«ut IвЂ™m unsure as well if this is what game developers had in mind when creating the API or if its consequences could be foreseen. And finally this means it becomes/is (an advanced) part of the game. Offering such an API, it must be assumed to be used. I think it is important to mention that this is a game for developers (or aspiring ones). I don't think that any other data tool like portal or markets is as threatening to the core gameplay as unlimited visibility of creeps on the map. I propose that communication creep population from the web API and introducing this information to the game without human intervention should result in a ban. Some of these services mirror functionality which could be gained by having a large network of allies in the game, but other services can remove gameplay constraints and provide an advantage which can only be repaired by hiding information from the best advertisement for the game: the ability to spectate the living world. information leakage is the most significant use of the web API 'not as intended' by the developers and the thing I think we should be addressing.ДЄlready we have both public and private services which scrape the web API in order to gain new information and reveal tactical information about the game world.

Screeps api Offline#

Offline pathfinding is hardly an issue and using it is just a crutch which limits the abilities of a script.ДЈ.

Getting that AI to perform well is a challenge because of the limitations placed on user scripts: limited CPU and 12MB of persistent storage. I consider offline training of an AI to be a primary motivation for experimenting in this game. This means at minimum a 2 tick latency for commands.Дў. Offline command execution should be ok because of the 2 levels of uncertainty: the results of the correct context for a command are not knowable by an external script, and commands are not executed until the following tick. When we discussed the Terms of Service and multi-account play previously I was heartened by Artem's response, to paraphrase: there are no new rules other than the rules as written but don't try to circumvent these rules with code.ДЎ.