-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Captain Mode Game Logic Update. #89
Comments
I think there is a problem in the condition of if-elseif-else-end logic in captain mode. The original script cannot ban or pick any hero. A preliminary fix is underway. The debug console information goes too fast and I can't read any thing, is there any way to stop the console information during the strategy phase? |
You can disable various channels if they aren't interesting to you. You can tell which channel a log message is from because it will be in brackets at the beginning E.g. "[Server] Invalid action (42)". Assuming you are looking for your own print messages, they will be on the [VScript] channel, so don't disable that. Anything without a listed channel is on General.
|
The other option would be to slow down time.
Set host_timescale < 1 to go slower than realtime. You can also use dota_pause in the console or DebugPause() in the code to completely stop and give yourself a chance to catch up. |
Finally, if it's your own messages that are flooding things, and managing the ebb and flow of the time tides is likewise overwhelming, you may want to throttle printing. One way to do that would be to only print on certain frames. E.g. the code below will only print messages when the frame is exactly at the second and exactly 0.5 seconds afterward. There are 30 logic frames per game second, and they are properly aligned with seconds (i.e. they don't drift). The code below probably has some rounding issues for different numbers.
|
thanks alot, that helps! |
The ban/pick in captain mode needs to be updated.
Now there are 7 bans, instead of 5 bans.
The text was updated successfully, but these errors were encountered: