eBot-CSGO
eBot-CSGO copied to clipboard
Ebot 4.0 ETA ?
Hi, just seen you refered to a Ebot 4.0 future version, any ETA ?
He has stated that no work has begun on 4.0 (complete rewrite).
However he does have 3.2.0 threads version (core) that is unreleased. Unsure of the reason to hold it back unless monetary. Something better will come along sooner than later. This project barely works anymore, not updated, and is dead. Privately maintained probably for monetary purposes.
I'm not bashing the developer, if he is making money in any capacity selling to DreamHack or other LANs, then good on him.
But at least stop telling the community it is "coming".
I updated to the last version for the eBot-WEB part. The bot itself doesn't have any changes.
For the V4, I don't have any ETA because I'm working on several projects.
Re: Coming up next in eBot 4.0 Postby deStrO » 26 January 2016, 21:17 I'm not dead, I'm working on new project and I don't have time for eBot. I'm thinking to release the current eBot core and search for community dev to make the "web" part.
Seems a bit contradictory to what you say... So what's the truth ? Is there a core part you will share/release publicly soon or not ? What about the web part ?
As KoSoVaR says, don't let the community wait if nothing will come out...
Very contradictory. According to this page http://forum.esport-tools.net/viewtopic.php?f=6&t=221&start=30 deStrO states, "I'm thinking to release the current eBot core and search for community dev to make the "web" part.".
Is there a chance to get two versions (i.e. 3.1 or 3.2) that are properly working together without using the ancient deb package?
I'm checking currently to make a new deb package with the current working version.
I found a way to install php + threads in a unique command, I'm testing it asap and building the package if it works :)
Hey Destro, I actually spent quite some time putting the bot into docker with pthreads. Got it working but I'm just afraid the codebase I got is not stable (I tried 3.1 and directly from master). The web version is also tagged 3.0 in it's latest release so hard to tell it will work with the v3.1 or master bot.
See the dockerfile here: https://gist.github.com/204e0d97c54205d2b92b
A simple docker build and docker run like this,
docker run -d -p 127.0.0.1:12360:12360 -p 127.0.0.1:12360:12360/udp --restart=always --name ebot
-vpwd
/logs:/ebot/logs
-vpwd
/demos:/ebot/demos
-vpwd
/config:/ebot/config ebot` ebot
(probably don't need to forward the tcp port).
Put the config files in pwd
/config and you are good to go.
I then configured the web part on the docker host directly (didn't put it in a container yet).
Happy to continue that work if I get a pair of versions that work without too many bugs :)
@deStrO unrelated question but why we've got a limitation on 64 simultaneous server instances managed by ebot, and how can we overcome this ? do we really need to duplicate ebot server and ebot database ?
With an "instance" mode, a kind of multiple instance on the same database server where eBot manage match only with his instance id. It's not public. Maybe with the 4.0 it will be easier to do.
@deStrO this version is not released yet is it ? any mean to find it somewhere ? :woman: