-
Notifications
You must be signed in to change notification settings - Fork 124
Conversation
return; | ||
} | ||
console.log(ids, ids[index]); | ||
return ids[index]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Expected no return value.
Thanks @houndci-bot :p |
checkforfood checks for food and eats it.
|
I presume for testing this - 3 options, which have to be and are present in the current master bot, **only need to be enabled:
(eat) may be one if the bug ^^^ is addressed or simply just remove it .... @clemens-tolboom |
@clemens-tolboom The overlay is also messed up - the scores don't fully show up |
Solved ? |
@ChadSki What options are you testing with for feature/task-execution ? |
@ChadSki 👍 |
It's only been two hours so far, but the results are not looking so great. Current medians below:
I'll keep the test running overnight, though. |
a23580a
to
d29adcb
Compare
This pull request has been open for over a month. I think it's best if development happens on the separate branch until it is truly ready for integration. |
You made me very nervous closing this PR so I pushed my code to git@github.com:clemens-tolboom/Slither.io-bot.git Note the issue summary has a separate branch https://github.com/ErmiyaEskandary/Slither.io-bot/tree/feature/task-execution but only I am working on it which s**ks Guess this is goodbye |
Nervous? The code doesn't go away, if that's what you meant -- the I like to follow your progress but pull requests are really about "I'm ready to merge, can anyone review my changes?" Since this branch isn't ready to be pulled/integrated, it shouldn't be a PR yet. It's very easy to open a PR so I would recommend doing so once everything is ready for review. |
Meta
Issue worked on
#275
Branch
https://github.com/ErmiyaEskandary/Slither.io-bot/tree/feature/task-execution
Description
As discussed in #266 but not completed yet here is my first stab.
My basic implementation uses a tasks list with priorities. I have added a few task
Motivation and Context
Problem
Adding new behaviour is difficult as this is hard coded. With A* it was still coded but easier to add new behavior. Furthermore we have a check for food triggered by a window timer which makes it harder too. It is not possible to add behaviour by another user script either.
Solution
This branch decouples the code
by replacing the parts mentioned above into a task scheduler. This allows for prioritise / (de)activate / adding tasks so the behaviour is more dynamic and alterable from outside this project (ie console).
It adds menu entries to toggle tasks to test particular behaviour.
Features
Task list
Screenshots (if appropriate):
Menu
MoveToXY
Types of changes
Checklist:
TODOs
Add surround algorithm from A* branchAdd more from A* branchReceive lots of feedbackschedule.init()
when entering game