Thread history

Fragment of a discussion from Talk:ScalarN/Version History
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
No results

3rd in 1v1 now too, crazy progress you've made with ScalarN!

Skilgannon (talk)14:14, 3 October 2018

Hear hear, not only third, but making big steps towards 2nd place ! I now also know (by comparing versions 147 to 138) that my bot is rather vulnerable for AS guns . . .

GrubbmGait (talk)14:50, 3 October 2018

My suggestion is, add BulletShadow! I was ignoring the value of BulletShadow for a long time, and that's why ScalarN easily passed ScalarBot ;)

Xor (talk)15:13, 3 October 2018
 

Thanks ;) And most credit goes to DrussGT and Diamond where their state-of-the-art techniques are explained in detail, without which building a good bot will get much harder. And I would also like to write more details about ScalarN once it's stabilized ;)

One thing I learned from ScalarN is that you always get what you put. With knn gun, multiple tree knn wave-surfing and bullet shadow, ScalarN soon gets similar performance with Diamond (even with totally different attributes, decays, kernel functions, etc.). And with 100+ vcs buffers, DrussGT is constantly doing better than Diamond ;) I can still remember how hard I tuned ScalarBot to work against PatternMatchers but nothing works, because the lack of Diamond's style BulletShadow. Adding a correctly implemented new feature gives you much more score than tuning day and night. A major upgrade gives you much more than doing hard around yourself. And life is also just like this.

Xor (talk)15:11, 3 October 2018

so true, to quote from GresSuffurds main page: the drive to change instead of tweak

GrubbmGait (talk)15:29, 3 October 2018