Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Cannot eat anybody #413

Open
ghost opened this issue May 9, 2016 · 16 comments
Open

Question: Cannot eat anybody #413

ghost opened this issue May 9, 2016 · 16 comments

Comments

@ghost
Copy link

ghost commented May 9, 2016

I just downloaded and installed it on Ubuntu 15.10, but no matter how large we grow, we cannot eat each other. Is there a setting I need to change?

@ghost
Copy link
Author

ghost commented May 10, 2016 via email

@ghost
Copy link
Author

ghost commented May 10, 2016

Yes, that worked! We can now eat blobs!! Thanks for the last good commit #.

@zleitzke
Copy link

Still not working for me.

@ghost
Copy link
Author

ghost commented May 11, 2016 via email

@zleitzke
Copy link

Tried it, still doesn't seem to work.

@ghost
Copy link
Author

ghost commented May 11, 2016 via email

@zleitzke
Copy link

Yes

@ghost
Copy link
Author

ghost commented May 11, 2016 via email

@zleitzke
Copy link

How would I clone that branch?

@ghost
Copy link
Author

ghost commented May 11, 2016 via email

@zleitzke
Copy link

zleitzke commented May 11, 2016

Won't install dependencies/start.

npm install
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/jscs/node_modules/vow-fs/node_modules/glob requires minimatch@'^2.0.1' but will load
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/jscs/node_modules/minimatch,
npm WARN unmet dependency which is version 3.0.0
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/babel-eslint/node_modules/babel-core/node_modules/source-map-support requires source-map@'0.1.32' but will load
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/babel-eslint/node_modules/babel-core/node_modules/source-map,
npm WARN unmet dependency which is version 0.5.6
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/eslint/node_modules/file-entry-cache/node_modules/flat-cache/node_modules/del/node_modules/globby requires glob@'^6.0.1' but will load
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/eslint/node_modules/glob,
npm WARN unmet dependency which is version 5.0.15
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/node-sass/node_modules/node-gyp requires glob@'3 || 4' but will load
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/node-sass/node_modules/glob,
npm WARN unmet dependency which is version 7.0.3
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/node-sass/node_modules/gaze/node_modules/globule/node_modules/glob requires minimatch@'0.3' but will load
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/node-sass/node_modules/gaze/node_modules/globule/node_modules/minimatch,
npm WARN unmet dependency which is version 0.2.14
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/node-sass/node_modules/request/node_modules/http-signature/node_modules/sshpk requires assert-plus@'^1.0.0' but will load
npm WARN unmet dependency /home/ubuntu/workspace/agar.io-clone/node_modules/node-sass/node_modules/request/node_modules/http-signature/node_modules/assert-plus,
npm WARN unmet dependency which is version 0.2.0
zanderl:~/workspace/agar.io-clone (es6-refactor) $ npm start
> [email protected] start /home/ubuntu/workspace/agar.io-clone
> babel-node server/index
sh: 1: babel-node: not found
npm ERR! Linux 4.2.0-c9
npm ERR! argv "/home/ubuntu/.nvm/versions/node/v4.4.3/bin/node" "/home/ubuntu/.nvm/versions/node/v4.4.3/bin/npm" "start"
npm ERR! node v4.4.3
npm ERR! npm  v2.15.1
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] start: `babel-node server/index`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] start script 'babel-node server/index'.
npm ERR! This is most likely a problem with the agar-clone package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel-node server/index
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs agar-clone
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! 
npm ERR!     npm owner ls agar-clone
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/ubuntu/workspace/agar.io-clone/npm-debug.log

@dynasty4544
Copy link

Eating won't work for me as well

abalabahaha added a commit that referenced this issue Jun 18, 2016
@geopi
Copy link

geopi commented Mar 8, 2017

Making a heavily modified version i stumbled into that bug too.

The bug I had was related to the the quadtree used for collision detection.

There is a temporary fix until a solution is found :

In server.js remove this :

 tree.clear();
        users.forEach(tree.put);
        var playerCollisions = [];

        var otherUsers =  tree.get(currentPlayer, check);

        playerCollisions.forEach(collisionCheck);

and put this instead :

        var playerCollisions = [];
         users.forEach(check);
        playerCollisions.forEach(collisionCheck);

It basically forces the detection in the whole map

Its dirty, I know.

@smarty6788
Copy link

smarty6788 commented Feb 11, 2018

I've found a fix but it includes removing the split

go to config.json and change limitSplit to "limitSplit": 1,

@johnsmitherson
Copy link

The problem I have is that smaller player is eaten only if it is in the center of bigger player, no matter what the size different. Can someone show what to change to make it that smaller player is eaten as soon it is completely under bigger player?

@aspriddell
Copy link

I made a sort of fix by finding the code in server.js (line 538) and removed the multipliers. As far as I know it is working much better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants