I’m a non programmer, if I submitted a bot that’s too complicated or that is supposed to do something that isn’t a possible move, would I be contacted and get a chance to change it, provided I submit it early enough?
Could you provide one or more examples of too complicated descriptions, just so I know for which level of complexity I should aim? I’m not clear on how you would consider a bot that has a decision three with different options and processes but no part that’s hard to program, for example. (To avoid giving hints or good ideas, they can be filled with completely stupid instructions or be for bots that try to do some other stuff)
If you’re worried whether something is too complicated then the best solution is to PM me with your most complicated dream bot and I’ll tell you how much of it I’m willing to code.
An example of something that is too complicated is Zach_M_Davis’s AbstractSpyTreeBot which runs a simulation of its opponent. Another example of something too complicated is is a neural network trained on your opponent’s past history. Such bots are perfectly legal if you code them yourself to reasonable speed constraints but I will not write one for you.
A hard-coded decision tree with several unambiguously-specified simple options is well within reason if that is all there is to it and you write a good specification. For example, using regular expressions to analyze your opponent’s source code if fine.
I’m sorry to ask for another detail, but I’m not 100% sure if simulator-bots such as AbstractSpyTreeBot are legal if you can program them yourself. Your reply seems to state so, but I didn’t wanted to assume.
Simulator bots are legal for programmers to write provided they never crash, slow the game to a crawl, etc. Any bot (even a non-simulator) that does will be disqualified.
I have not yet read the AbstractSpyTreeBot source code in detail nor run it myself. A cursory glance suggests it’s within the rules.
I’m a non programmer, if I submitted a bot that’s too complicated or that is supposed to do something that isn’t a possible move, would I be contacted and get a chance to change it, provided I submit it early enough?
Could you provide one or more examples of too complicated descriptions, just so I know for which level of complexity I should aim? I’m not clear on how you would consider a bot that has a decision three with different options and processes but no part that’s hard to program, for example. (To avoid giving hints or good ideas, they can be filled with completely stupid instructions or be for bots that try to do some other stuff)
If you’re worried whether something is too complicated then the best solution is to PM me with your most complicated dream bot and I’ll tell you how much of it I’m willing to code.
An example of something that is too complicated is Zach_M_Davis’s AbstractSpyTreeBot which runs a simulation of its opponent. Another example of something too complicated is is a neural network trained on your opponent’s past history. Such bots are perfectly legal if you code them yourself to reasonable speed constraints but I will not write one for you.
A hard-coded decision tree with several unambiguously-specified simple options is well within reason if that is all there is to it and you write a good specification. For example, using regular expressions to analyze your opponent’s source code if fine.
That sounds perfect, thank you.
I’m sorry to ask for another detail, but I’m not 100% sure if simulator-bots such as AbstractSpyTreeBot are legal if you can program them yourself. Your reply seems to state so, but I didn’t wanted to assume.
Simulator bots are legal for programmers to write provided they never crash, slow the game to a crawl, etc. Any bot (even a non-simulator) that does will be disqualified.
I have not yet read the
AbstractSpyTreeBotsource code in detail nor run it myself. A cursory glance suggests it’s within the rules.