What macros?why not use macros instead?
Not sure that will help, while it is related, it also states that "wait is disabled".
Not sure why you people repeat it over and over again.Wait is disabled
As I said, "wait" isn't disabled, but if we imagine for one second it can work asynchronously, without blocking user input -- what's the reason to disable it?for a reason btw
He probably meant mouse macros.What macros?
When you write a bind in-game (/bind key "commands") with "wait", you will get a message "Sorry, wait is disabled server-side". However, if you write it in a script file (I use autoexec.cfg), and (maybe) also use vstrs, then the block doesn't work and I really have no idea what can be done here to block it. I wasn't the one to have blocked it in the first place tho so this should be taken care of by them.Not sure that will help, while it is related, it also states that "wait is disabled".
Anyway, I think OP is already have that program from Helix, so now his issue should be solved.
I'm almost certain there's some deep reason in the JKA engine why input block during wait is needed. Not like it's impossible tho.but if we imagine for one second it can work asynchronously, without blocking user input -- what's the reason to disable it?
Just to mention - me being a part of the dev team has no relation to this script. That is, no "MBII dev" knowledge is needed in order to write it.And Helix, who is a member of the development team, has wrote the program that implement async delaying, and he distributes it on request.
Yes, I will most likely use Pipex' C implementation (originally the app is not C) and search for the ways to make it cross platform before actually OSing it.He also said he's going to make it open-source.
Once again, what mouse macros?He probably meant mouse macros.
lol I didn't use /bind at all, I was testing it directly with autoexec.cfg lmaoWhen you write a bind in-game (/bind key "commands") with "wait", you will get a message "Sorry, wait is disabled server-side". However, if you write it in a script file (I use autoexec.cfg), and (maybe) also use vstrs, then the block doesn't work and I really have no idea what can be done here to block it.
No no no, you probably didn't get what I was talking about.I'm almost certain there's some deep reason in the JKA engine why input block during wait is needed. Not like it's impossible tho.
Oh come on, we both know that they're tracking what dev team members do, and they forbid things they don't like.Just to mention - me being a part of the dev team has no relation to this script.
Sorry, I just assumed it by this your sentence: "I wrote an external application which sends the commands to the game console directly, every 2000 ms. It's indeed an unlimited pool of possibilities but requires knowledge of the programming / scripting languages. Pm me if interested."I also don't distribute it on request.
What's an interesting list...Kimmy, Alice, Tempest, Pipex, Penekowski, Gr1meZ
Maybe I should wrote it... But I already have too many things to do irl =\Not gonna happen in few months tho.
Bullshit. I wrote the app for my own amusement and none from the dev team needs approval from others to use self-written apps (yes, im srs). Don't start this exaggerated slander.Oh come on, we both know that they're tracking what dev team members do, and they forbid things they don't like.
I made this thread after I assumed the last one was done. I would've removed it if I could.This thread is a duplicate of the one we already have, it isn't even supposed to exists.
Except the day when my bot was saying black racist one-liner jokes (per request! the command was !imracist) on BG server and I was muted by vis After like 30 mins of arguing.
ok, third-party software/hardware.P.P.S Answering "what mouse macros?" X7--Oscar
This thread already has some valuable replies, it should be merged with Delaying/Repeating scripts , not removed. Only moderators can delete/merge threads.I made this thread after I assumed the last one was done. I would've removed it if I could.