Trying to run this without the .exe about among-us-proxy

[TreeOfSelf]

I managed to get it running and working by manually npm install every missing module, however, it seems there is some built in limitation in the .exe, because all my clients past 10 were getting an error. I wonder if we can get around this somehow?

[NickCis]

Hi there!,

You should run the npm install on the root folder repository and also do a bootstrap:

npm install
npm run bootstrap

Then you can run the command line util from the packages/among-us-proxy folder: node src/main.js. I must highlight that you'll probably want to use the electro ui as it also spins up an ngrok instance in order to expose the necessary ports (run npm start from packages/gui).

Regarding the limit, how did you host a server with the player limit increase?. I don't know if the game checks the number that is sent in the discovery message (I would bet that it doesn't, you can try with different hardcoded values changing it from the broadcasted message).

Server's may send a disconnect message to clients (are the 0x09 message codes), this message can contain a description of why they are disconnecting you.

As the proxy sits in the middle of the game and the server, you can modify messages in that layer, e.g.: making believe the client that there are less users connected. But, I won't think that this would really work. Can you give a in depth explanation about what you are trying to achieve?

[TreeOfSelf]

I am trying to connect over 10 players, you can easily set the lobby to show a max player limit of over 10, either by editing the memory address or by editing the file gameHostOptions under AppData\LocalLow\Innersloth\Among Us Its jus a HEX value in there. The problem is, if I run faker.js say, 20 times? The first 9 will connect fine, but then they start displaying this:

[NickCis]

I really don't know what that 01 00 01 04 00 01 01 00 00 00 message means. As far as I understand the sever should have answered with a 01 ... 07 message.

I should research about the topic (also, there are some bugs on the fake.js script that create a bad connection).

If you want to check what a real client is doing, you can use the proxy as a man in the middle by using the among-us protocol (under the packages/among-us-proxy folder:

node src/main.js guest among-us://<server-ip> --debug

[TreeOfSelf]

Sounds good, I will look into it more. Thanks for your help! It would be huge if we could accomplish this.

[NickCis]

Please explain me how can I increase the user limit so I can also perform some tests :).

[TreeOfSelf]

https://filebin.net/7o0i22t9oenbk2rq/gameHostOptions?t=iyg7sw8o

Put this file in your AppData\LocalLow\Innersloth\Among Us

Now, when you create a local server it will be set to a 100 player limit.
NOTE you will NOT be able to create a normal game through the host menu in online play UNTIL you click 1-10 on the player limit option. The game will simply crash. Clicking 1-10 will revert the config back to normal.

[NickCis]

Ok, I'll try that, can you explain how are you editing that file?

[TreeOfSelf]

https://hexed.it/ I uploaded it into here, then I went and hosted a game and changed the max player limit, I saw which hexadecimal value changed .

64 in decimal form = 100

[TreeOfSelf]

Upon further experiments it would seem some sort of hardcoded check is built into the game's .dll/.exe files and this may be out of the scope of this project. Thanks for listening , feel free to close this.

[NickCis]

Ok, I'll close it.

You could try the impostor project which aims to build an oss Among us replacement (being compatible with current protocol). Maybe it can achieve what you were trying to do!