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

"No Choice" Split function #599

Open
Drflash55 opened this issue Apr 19, 2016 · 9 comments
Open

"No Choice" Split function #599

Drflash55 opened this issue Apr 19, 2016 · 9 comments

Comments

@Drflash55
Copy link
Collaborator

I was thinking that the bot could have a function implemented in it's algorithm, that when there's a cell bigger than the bot, and it gets way too close (trying to split for the bot, re-merges near the bot), the bot can try to split away in the opposite direction to avoid getting killed.

Although, this can be a problem with smaller cells, as if you got popped, and another cell tries to eat the smaller pieces, it may try to split away, and thus, the bigger cell would split and put it in even more danger.

So, with this function, you should make it so that it will only split away, when it has only 1, to 4 cells. It can sort of prevent the issue above, but it's not totally perfect.

Discuss this, as I want to see your opinions as to if this is a good idea to start working on.

@FliiFe
Copy link
Collaborator

FliiFe commented Apr 20, 2016

It's very rare (from my experience) that cells are that close to your cell. However, that would be a good idea. It's still better than not doing anything.

@ermiyaeskandary
Copy link
Contributor

@FliiFe @Drflash55 Doesn't the bot avoid enemies from a certain distance which is the distance where they can split ? That would render this useless. Do you mean near the walls if you are cornered but even then, the wall code will be added soon which fixes this .

@Drflash55
Copy link
Collaborator Author

@ermiyaeskandary, there are times when just the normal speed alone, won't cut it, because someone splits for you at least twice, or three times in a row.
Also, when it's near a cell that re-merges, the person, can easily split at you as soon after it re-merges. The re-merge warning should help avoid this problem, but it can still happen.

@ermiyaeskandary
Copy link
Contributor

@Drflash55 @FliiFe Can you test this ?
@muratlahur ads have been removed.

@Drflash55
Copy link
Collaborator Author

Drflash55 commented Apr 20, 2016

@ermiyaeskandary I need the place to insert it, as to not interfere with the bot's internal coding.

EDIT: Hold on. Mura stated which line to insert it at... Testing it out soon. Does this go into user.js or launcher.js?

EDIT 2: Code was completely removed... So, I guess I won't be testing it out then... and even then, it didn't work anyways.

@ermiyaeskandary
Copy link
Contributor

ermiyaeskandary commented Apr 20, 2016

Line 137 and Line 922. Read @muratlahur comment.

Yes, I'm aware of it, and just made an edit to my comment. ~Drflash55

@Drflash55
Copy link
Collaborator Author

Drflash55 commented Apr 20, 2016

@ermiyaeskandary I've tried inserting it into bot.user.js, but my school firewall is blocking it ;).

I'm sorry, I will have to test this at home...

EDIT: Didn't work anyways... So, I guess it was nothing special that I tried doing with it.

@ermiyaeskandary
Copy link
Contributor

@Drflash55 damn
@FliiFe Can you test ?

@Drflash55
Copy link
Collaborator Author

@ermiyaeskandary Trying to use this, the bot breaks... Not sure if I should've inserted this into bot.user.js. But, launcher.user.js doesn't seem like the place to put this.

The current update shows this error as I try to use this code...
This is the error

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

3 participants