xnite/MCSeeker
1
0
Fork 0
mirror of https://github.com/xnite/MCSeeker.git synced 2026-05-02 12:54:50 -07:00
Code Issues Packages Projects Releases Wiki Activity

Option for how many concurrent connections to use.

Browse Source 
Can increase scan efficiency with higher numbers, or you can reduce the amount of connections for use on terrible internet connections. Default is 256
This commit is contained in:
etianl
2023-01-06 01:49:31 -08:00
committed by GitHub
parent 0a73fb77af
commit f05b17ee9a
2 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@@ -18,6 +18,7 @@ Run `node ./scanner.js [options] --ip <ip range>`
* `--min-players <count>` - Minimum number of players.
* `--max-players <count>` - Maximum player count.
* `--version <glob expression>` - Glob expression to filter version (eg- `1.19.*`, or `1.1*.*`). (Default: `*`)
* `--conc <howmany>` - How many concurrent connections to use for scanning. (Default is 256)
#### Output Options
* `--show-desc` - Enable showing of server description in output.
@@ -47,5 +48,5 @@ Run `node ./scanner.js [options] --ip <ip range>`
In this example it took `3.183` seconds to scan `255` IP addresses, and find `85` MineCraft servers. At this speed, a full `/16` (`123.45.0.0 - 123.45.255.255`) will take about `13.5` minutes to scan.
## Limitations
* Fails to scan more than a /16 without kicking the bucket... so you should probably stick to that or smaller ranges.
* Fails to scan more than a /10 without kicking the bucket... so you should probably stick to that or smaller ranges.
* Working on a Minecraft bot client... doesn't work though... you can see how badly it doesn't work by using `--enable-client` flag... it is totally broken. **Don't use it**.