Congrats!

Oh dear: twitter post 1 twitter post 2

SPCS refers, I believe, to Stanford Pre-Collegiate Studies, as per here.

While I actively encourage people to read my code, understand my code, learn from my code and even use my code (in small portions), what I can't stand is people passing my code off as their own. As much as I appreciate the complements given to DrussGT and my GoTo surfing algorithm, the fact that even the class names remain the same doesn't give me much hope as to their contents.

I don't want to ruin somebody's life over copying code, particularly when dealing with a prestigious opportunity like SPCS seems to be. That being said, I'd really like Linio to be open source, and to be honest I'd prefer if my buffering systems, targeting weights, two-wave goto surfing and precise intersection code was understood and re-implemented, rather than copied. I'm sure those of you who have bots lower in the rankings feel annoyed as well.

I admit that this bot is structurally based on DrussGT, yet I did do my own tinkering with it. I am doing a reimplementation of it and will post it when it is ready. I apologize for taking the code without previously asking for permission.

What tinkering did you do to Druss-GT L1ni0.

Much better! That post is on-topic, properly capitalized, and it has punctuation at the end of its sentence. Though Druss-GT should be DrussGT, instead of the period you should have a question mark (?) at the end of your sentence since you are asking a question, and when you are addressing someone, you should put a comma before or after their name, so "What tinkering did you do to [DrussGT] L1ni0[?]" should be "What tinkering did you do to [DrussGT], L1ni0[?]"

And just in case you think I submitted Linio as my SPCS final project. I did not. I could send you the code I used for my project. It was, I guarantee, completely my own.

Thanks for the quick response. If you wrote your own bot for the SPCS, why not release that as well?

And don't worry about not asking permission, that isn't what I care about. What's important to me is that 1) you make your bot open source - any compiled version you release needs to be accompanied by source code, so that any improvements or changes you make can be easily identified - and 2) you give credit.

Those are the issues that concern me. However, there are others further down in the ranks, who have spent years of work achieving their ranking (much like I have). To be honest I'm not sure it's fair on them to take a tweaked, finished solution which has been completely integrated between gun and movement, reshuffle how some of the code is laid out, change some class names and call it your own.

To be honest, it really does bother me quite a lot. It took me almost 8 years (of on and off again work) to get to here I am now in the rumble. That is quite a chunk of time.

But I am surprised I managed to recognize what someone elses robot was based off from only on the class structure and names, given that it wasn't based on one of my robots.

I agree, this bot is a clone, it infringes Skilgannon's copyright, and should be removed from the rumble.

I've removed it until such time that it follows the License set forth by Skilgannon. I also expect with this, that any bot you release that makes it into the top 30 to 50 will be heavily scrutinized.

I would like to see your code from SPCS.