You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
resolution_fixedtype_patch (an actual patch, not a request for one) | by Prot
Function removeTimer() - not remove timer in "this scope", but remove the timer with same name in first matched bot-player.
For example: we are create simple bot-player, who eveery second send message with his number player:
function eventStartLevel(){
queue("init", 1000);
queue("stopTimer", 5000);
}
function init(){
setTimer("debugMsg", 1000);
}
function stopTimer(){
if(me==2){
removeTimer("debugMsg");
debug("["+(Math.floor(gameTime/1000))+"] i'm #"+me+", stopTimer()");
} else {
debug("["+(Math.floor(gameTime/1000))+"] i'm #"+me+", continue");
}
}
function debugMsg(){
debug("["+(Math.floor(gameTime/1000))+"] I'm #"+me);
}
Then after 5 second we removeTimer only on second bot-player, and we see this result:
As we can see, the player 2 try to remove his timer, but timer stop on player 1 only.
Problem has in 3.1.5, 3.2.3 and master version.
I found the problem in qtscript.cpp and make this patch
Issue migrated from trac:4663 at 2022-04-16 12:56:41 -0700
The text was updated successfully, but these errors were encountered:
resolution_fixedtype_patch (an actual patch, not a request for one)| by ProtFunction removeTimer() - not remove timer in "this scope", but remove the timer with same name in first matched bot-player.
For example: we are create simple bot-player, who eveery second send message with his number player:
Then after 5 second we removeTimer only on second bot-player, and we see this result:
As we can see, the player 2 try to remove his timer, but timer stop on player 1 only.
Problem has in 3.1.5, 3.2.3 and master version.
I found the problem in qtscript.cpp and make this patch
Issue migrated from trac:4663 at 2022-04-16 12:56:41 -0700
The text was updated successfully, but these errors were encountered: