Steam installieren
Anmelden
|
Sprache
简体中文 (Vereinfachtes Chinesisch)
繁體中文 (Traditionelles Chinesisch)
日本語 (Japanisch)
한국어 (Koreanisch)
ไทย (Thai)
Български (Bulgarisch)
Čeština (Tschechisch)
Dansk (Dänisch)
English (Englisch)
Español – España (Spanisch – Spanien)
Español – Latinoamérica (Lateinamerikanisches Spanisch)
Ελληνικά (Griechisch)
Français (Französisch)
Italiano (Italienisch)
Bahasa Indonesia (Indonesisch)
Magyar (Ungarisch)
Nederlands (Niederländisch)
Norsk (Norwegisch)
Polski (Polnisch)
Português – Portugal (Portugiesisch – Portugal)
Português – Brasil (Portugiesisch – Brasilien)
Română (Rumänisch)
Русский (Russisch)
Suomi (Finnisch)
Svenska (Schwedisch)
Türkçe (Türkisch)
Tiếng Việt (Vietnamesisch)
Українська (Ukrainisch)
Ein Übersetzungsproblem melden
but it doesn't seem to work. I'm not a total expert, so, I might very well be overlooking something.
I pulled up my old scripts and I forgot how much time I put into this. I actually wrote an entire watchdog routine that would automatically launch the game and log you in during siege hours. This was because on my PVP server people generally didn't siege you if you were online. There's fail-safes in place to make sure you weren't already playing, etc. I also changed hotkey assignments depending on if you were in combat or not. It's very elaborate, but again, I haven't played in so long I couldn't tell you the methodology here without actually reinstalling the game to check.
You can dissect this and pull out the part that remedied the mouse wheel limitations.
It looks like I used a subroutine baked into a WheelUp/Down call to get around it.
Thankfully I annotated my work so maybe you can make sense of it.
The script was too large to paste the text of it here, so I uploaded it to github (top link):
https://github.com/Kornstalx/V-Rising-Server-Watchdog
Ok, thanks for replying and sharing the info.