its laggy when you fix?, i'm mod of slithere.com can we share this bot too?

In the README and the script itself, defence mode is indicated as being triggered by "D", but the in-game overlay says "[" triggers it, which is not true.

See: http://i.imgur.com/6vQq7Gs.png and http://i.imgur.com/x7Zg8Ix.png

This bot needs a way to avoid other snakes.

Cluster food together that is within one snake radius from the cluster center and calculate distance from that to optimize calculations and fix priorities.

Todo list:

• Calculate our snake's width
• Use width to make clusters
• Add value to clusters and do calculations on clusters as a whole.
• Have bot target clusters

Okay here's a mockup for how I would do this:

Algorithm to check if point is within circle: (x - center_x)^2 + (y - center_y)^2 < pickup_radius^2

1. Start with all of the points in the unassigned group.
2. Pick one point and look at all the others in the unassigned group and see whether they are within 1 snake pickup radius (I think this is bigger than the visual radius.)
   1. If yes, start a group, and continue on with all the other points to see if they fit in this group (based on starting point), and if they fit in, move them from the unassigned group into this new one.
   2. But, if no point matches the criteria for a starting point, use the starting point as a cluster of one.
3. At the end we will have grouped the points by radius.
4. Sum the sizes of the food in the cluster.
5. Find the distance of the cluster by finding the weighted center of the cluster and check distance from there.

After this, I think we should calculate clusters separately from calculating which one to target, clustering only once per few seconds.

Alternatively, we can base our code of off Apostolique's bot:

window.clusterFood = function(foodList, pickupRadius) {
        var clusters = [];
        var addedCluster = false;
        //1: x
        //2: y
        //3: size or value
        //4: Angle, not set here.
        for (var i = 0; i < foodList.length; i++) {
            for (var j = 0; j < clusters.length; j++) {
                if (window.getDistance(foodList[i][0], foodList[i][1], clusters[j][0], clusters[j][1]) < pickupRadius) {
                    clusters[j][0] = (foodList[i][0] + clusters[j][0]) / 2;
                    clusters[j][1] = (foodList[i][1] + clusters[j][1]) / 2;
                    clusters[j][2] += foodList[i][2];
                    addedCluster = true;
                    break;
                }
            }
            if (!addedCluster) {
                clusters.push([foodList[i][0], foodList[i][1], foodList[i][2], 0]);
            }
            addedCluster = false;
        }
        return clusters;
    };

Todo list:

• Bot should have settings such as
  • To enable/disable console logging
  • Preferred graphics quality
  • Which distance formula to use when we implement the new one
  • Which name to use
  • Whether or not to "autorespawn"
• We need the bot to not instantly join the game the second the page loads.
• Settings should be saved locally so they are persistent.
• Settings should be edited visually on the main screen or offer clear controls.
• Saving code implemented
• Loading code implemented

This code unlocks skins without needing a share on twitter or facebook.
window.localStorage.setItem("edttsg", "1");

It's only my problem?

Green = enabled
Red = disabled

Instead of pointing at food, have the visual line lead to the Prey it is chasing.

• Add FPS check every several seconds.
• When below ~20, switch to low graphics settings on the fly and disable unneeded features. Maybe slow down the bot clock a few milliseconds.
• When above ~40, switch back (gap is needed between the two triggers so it doesn't turn on and off madly.) Or maybe have multiple intermediate graphics levels.
• Be able to toggle this function.

Slight offset when converting from canvas to screen so issue lies in :

window.screenToCanvas = function(x, y) {
    var canvasX = window.csc * x * window.canvasRatio[0] - window.csc * parseInt(window.mc.style.left);
    var canvasY = window.csc * y * window.canvasRatio[1] - window.csc * parseInt(window.mc.style.top);
    return [canvasX, canvasY];
};

This small offset causes issues with the visual element and other things. Variables which stores offset is unknown.

How to avoid collisions with other worms?

The bot should not try to hunt preys without enough length. So I suggest setting a minimum length of about 200.

Very annoying and stupid feature
Even when i enable(disable?) the bot, it's still on boost mode

just remove it. there's no point to it.

So I will have the user script install and go to slither.io and the bot won't start. Some times it can 5 - 6 reloads for the bot to start
INFO
Chrome
0.6.0
I have no idea what caused it

Okay, so at a certain range, the snake will lose more than it gains when hunting down prey.

• Find the length lost per distance when boosting
• Use that measure to see if it is worth it to go after it.

You know, instead of just trying to sprint across the map.

It looks like zooming out in the game (with the bot and collision detection enabled),
increases the radius of detection. I'm not sure if this behaviour is intended.

Below are two screenshots of the problem, the first one at the standard zoom level.
Sorry for the bad quality, if necessary I can provide better ones tomorrow.

• Use sessionStorage orlocalStorage to keep a high score list for previous lives of the bot.
• Show leaderboard visually on screen

Am I the only one to notice huge lags ? It's fine in the beggining, and gets worse over time

Bot should prioritize big food since it is better in every way.

• Maybe half its distance when calculating nearest food to give bot a preference?

But first, we need to be able to discern big food from the rest.

need more careful enemy avoidance while it is boosting after pray

I have noticed that the bot will occasionally just start over. No death, no main menu screen, it just restarts.

Bot should treat snake bodies and the map border as obstacles, but treat heads as active threats.

Maybe have a mimicry form of self defense?

I propose that we use https://waffle.io/ErmiyaEskandary/Slither.io-bot
based on the ideas of http://www.ianbicking.org/blog/2014/03/use-github-issues-to-organize-a-project.html

Of course, we will still use slacker for the main means of group communication, this helps organize and focus our open source group we have going here.

Thoughts on waffle.io?

Stopped after 3 respawns

I think we should use gitter so that anyone can join and voice what they think about the bot and also we will not have the invite issues of slack

When enemies are near, we could just turn in a perfect circle until they give up. This could prove successful as we can go in a perfect circle using programming but they can't - and eventually they will give up.

Solution, make handler for enter?

Can't wait to see how this will turn out in due time...

https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame

requestAnimationFrame(window.loop);

// target the user's browser.
(function() {
  var requestAnimationFrame = window.requestAnimationFrame || 
                              window.mozRequestAnimationFrame || 
                              window.webkitRequestAnimationFrame ||
                              window.msRequestAnimationFrame;

  window.requestAnimationFrame = requestAnimationFrame;
})();

This will build the snake bodies in the low rendering mode, it may be of use. I would really like to communicate with you guys on slack or skype...something.

window.hmm = function (){
    var b = window.mc.getContext("2d");
    for (h = window.snakes.length - 1; 0 <= h; h--) {

    if (c = window.snakes[h], c.iiv) {
        f = c.xx + c.fx;
        w = c.yy + c.fy;
        px = f;
        py = w;
        E = c.ehang;
        var t = c.sc,
            x = 29 * t,
            D = c.cfl;
        e = c.pts[c.pts.length - 1];
        if (1 == render_mode) {
            b.save();
            b.beginPath();
            b.moveTo(window.mww2 + (px - window.view_xx) * window.gsc, window.mhh2 + (py - window.view_yy) * window.gsc);
            z = !1;
            for (var y = c.pts.length - 1; 0 <= y; y--) {
                e = c.pts[y];
                lpx = px;
                lpy = py;
                px = e.xx;
                py = e.yy;
                var B = e.fx,
                    q = e.fy;
                0 < D && (px += B, py += q, lax = ax, lay = ay, ax = (px + lpx) / 2, ay = (py + lpy) / 2, z || (lax = ax, lay = ay), 1 > D && (u = 1 - D, lpx += (lax - lpx) * u, lpy += (lay - lpy) * u, ax += (lax - ax) * u, ay += (lay - ay) * u), z ? D-- : D -= c.chl + c.fchl, z ? b.quadraticCurveTo(window.mww2 + (lpx - window.view_xx) * window.gsc, window.mhh2 + (lpy - window.view_yy) * window.gsc,
                    window.mww2 + (ax - window.view_xx) * window.gsc, window.mhh2 + (ay - view_yy) * window.gsc) : (b.lineTo(window.mww2 + (ax - window.view_xx) * window.gsc, window.mhh2 + (ay - window.view_yy) * window.gsc), z = !0));
            }
            b.save();
            b.lineJoin = "round";
            b.lineCap = "round";
            is_firefox ? (c.sp > c.fsp && (y = c.alive_amt * (1 - c.dead_amt) * Math.max(0, Math.min(1, (c.sp - c.ssp) / (c.msp - c.ssp))), b.save(), b.strokeStyle = c.cs, b.globalAlpha = .3 * y, b.lineWidth = (x + 6) * window.gsc, b.stroke(), b.lineWidth = (x + 9) * window.gsc, b.stroke(), b.lineWidth = (x + 12) * window.gsc, b.stroke(), b.restore()), b.globalAlpha = 1 * c.alive_amt * (1 - c.dead_amt), b.strokeStyle = "#000000", b.lineWidth = (x + 5) *
               window.gsc) : (c.sp > c.fsp && (y = c.alive_amt * (1 - c.dead_amt) * Math.max(0, Math.min(1, (c.sp - c.ssp) / (c.msp - c.ssp))), b.save(), b.lineWidth = (x - 2) * window.gsc, b.shadowBlur = 30 * window.gsc, b.shadowColor = "rgba(" + c.rr + "," + c.gg + "," + c.bb + ", " + Math.round(1E4 * y) / 1E4 + ")", b.stroke(), b.stroke(), b.restore()), b.globalAlpha = .4 * c.alive_amt * (1 - c.dead_amt), b.strokeStyle = "#000000", b.lineWidth = (x + 5) * window.gsc, b.stroke(), b.strokeStyle = c.cs, b.lineWidth = x * window.gsc, b.strokeStyle = "#000000", b.globalAlpha = 1 * c.alive_amt * (1 - c.dead_amt));
            b.stroke();
            b.strokeStyle = c.cs;
            b.globalAlpha =
                .8 * c.alive_amt * (1 - c.dead_amt);
            b.lineWidth = x * window.gsc;
            b.stroke();
            b.restore();
            b.strokeStyle = c.cs;
            c.dead && (q = (.5 + .5 * Math.abs(Math.sin(5 * Math.PI * c.dead_amt))) * Math.sin(Math.PI * c.dead_amt), b.save(), b.lineJoin = "round", b.lineCap = "round", b.globalCompositeOperation = "lighter", b.lineWidth = (x - 3) * window.gsc, b.globalAlpha = q, b.strokeStyle = "#FFCC99", b.stroke(), b.restore());
            b.restore()
        }
        }
    }
};

Hello

1. Please restore the auto startup play game.
2. Replace or add options: "Defense mode - bot turns around in a perfect circle"
   do not turn in a perfect circle always head protrudes - better add "auto distance" from others (and prevents collisions).
3. To facilitate enable fast switching bot disable / enable the right mouse button - not key "T" (replace - key / button).
4. "Fast Boost" - Always possible under the left mouse button (independently / regardless - bot enabled).
5. Save / Remember selected skin + options.

I'm sorry for my language english is not good. Thank you in advance if possible to change the.
Thank you for your work. Regards. GL&HF ;)

Bot gets stuck trying to eat a single piece.

Potential solutions:

• Ignore food closer than n units to the left or right (Do we have currentBotAngle detection?) since these food will most likely be within our turning radius.
• Solve issue #13
• If we solve #23 then the bot would be very unlikely to get stuck on one.

I dont think this would be that difficult right? i have seen it in some other mods and its pretty nice

Bot can use connect() function to rejoin the game after a death.
TODO: Add this functionality.

Move based on angles instead of rectilinear (cartesian) coordinates.

So if snake is [0,0] and food is relative [3,4]: convert the rectangular (cartesian) coordinates to polar using arccos(3/sqroot( 3^2 + 4^2)) to return the angle theta of the food relative to the snake.

The pythagorean theorem is part of the equation
var distance = Math.sqrt(Math.pow(xDistance, 2) + Math.pow(yDistance, 2));
var angle = 1/(Match.cos(xDistance / window.distance));

Todo list:

• Calculate angle from bot of each food
• Be able to move in direction of an angle
• Implement this as replacement

If the user types in window.nick_holder, the settings shouldn't be toggled.

Essentially, add a predictor that makes the bot eat its current target at an angle that will make it easy to eat the next one.

Since snakes can't turn on a dime, this is needed to eat long chains of food without extreme wiggles.

Can we make a count of how many kills we cause?

Perhaps add that to the leaderboard of #38 ?

What do you guys think of:

• We currently use (distance / size) to calculate priority
• Instead, we use (distance / size^2) in order to further prioritize larger food. I tested this and it is much better at not just ignoring the huge food from a dead snake.
• Perhaps have this feature included with a "high" setting?

When I enable this extension, it causes Slither.io to crash to 1spf and causes a massive CPU usage spike.