Quote from: GrO on August 11, 2020, 09:41 AM
...terion, you're gonna try to fix it, you're able to or you just wanna leave it as it is?
if it ain't broke, don't fix it.
your pc is missing Visual C++ Redistributable Runtimes (2015-2019) - here is a link to all-in-one installer:
https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/btw, WA's warning message should be made more clear about the cause of error 0x7E to avoid confusion. ideally, it should list all missing DLL dependencies and suggest to try installing msvc runtimes, madshi's madCodeHook. If you ever stumble over similar issue, try running Dependency Walker
https://www.dependencywalker.com/ to identify missing libraries.
regarding other issues:
- you can kick players with stupid-long nicknames by pressing F1-F6 keys and replacing /msg with /kick. adding /kickX is a trivial task and the module is open source, so feel free to implement it
- a voting mechanism is a really good idea in general (for example to trigger a sudden death mode, force some player AFK, add weapon ammunition for all teams, change scheme options, etc.), but voting algorithm itself might be quite complex to implement to cover all edge cases (players quitting, rate limiting, messaging protocol). if anyone is interested, I can expose API to read json chat messages, so voting communication can be implemented
- the module kicks players instantly - it should send a message that player is being kicked, spawn a new thread that waits for 5 seconds and only then kick the player
- in my opinion this functionality should come standard with base game to avoid shitty kick module implementations like this. WA players are grown up men and let them decide whether it is just to kick players from their games