Instead of writing a separate program, could you add a switch to the untzbot that just disables the space bot portion? Sometimes I just want to run missions without the space missions having to be run. Its a QoL issue, so either way you can do it I will be grateful as will many others :)Quote:
i could, i guess
ill release a untzcrewbot sometime, itll be practically a stripped down version of untzbot
and 'mission sniping' is 'in the works' - it was ready pre 1.2 but then 1.2 changed all of the mission rewards so that kind of broke everything, etc, so ill get around to making new images soon
I THINK and or hope that what he is looking into is a request that was sent to him awhile back on a script that would loop through all your characters and send each of them out on crewskill missions. I started to write a wrapper around his existing stuff to do just that but I got side tracked on trying to get 5.0x and 5.0x2 to work 100% of the time. So far the closest thing I have been able to do is get 5.0x to work most of the time.Quote:
Instead of writing a separate program, could you add a switch to the untzbot that just disables the space bot portion? Sometimes I just want to run missions without the space missions having to be run. Its a QoL issue, so either way you can do it I will be grateful as will many others :)
Look forward to this being released, thanks!
Are you running deathcheck? its a seperate program in the directory.Quote:
If i die it does not click leave mission why?
What!? Yeah we aren't doing that. At least I am not. I can run 5.0x just fine and most of the time there are no issues. But when I run 5.0x2 is where I get the issue. In space, away from the crew bot.Quote:
I am using 5.0x w/ the 5.0x2 event files.
It's not related, the current version of the bot is just fuxored. For alot of people it worked for a while but has just suddenly died on us. So far I have tried re-downloading the new version(didn't help), gotten updates for Autoit(didn't help). I have no idea why the error persists or what even brought it on, but it's f*#%ing annoying and so far we haven't heard shit from thephilz regarding it either.Quote:
Wasn't getting:
"Line 6462, ERROR Variable Used without being decleard"
Yesterday, but added memory today (went from 4G to 16G) and started getting this error.
May or may not be related, but if it's any help, just thought I would point it out.
Deathcheck is in the UntzBot directory. It is used to check to see if your ship gets blown up in the middle of the mission, and exit you automatically if you have been destroyed. That is what you were asking about.Quote:
I must start deathcheck and the bot? for what is deathcheck?
Yeah, i never downloaded 5.0x2. I had just downloaded the pre-release sync files he had put up. I need to take a look at the new version to see if I have the same issues everyone else is. But with 5.0x workig with the x2 files, I don't see myself doing that soon.Quote:
What!? Yeah we aren't doing that. At least I am not. I can run 5.0x just fine and most of the time there are no issues. But when I run 5.0x2 is where I get the issue. In space, away from the crew bot.
OK I took all the files and folders (except UntzBot50x2.exe and DeathCheck50x2.exe) and copied them into my UntzBot50x folder and.... everything works fine now, I've even running EventSync which I never do.
PS
There is no good reason why I didn't just copy UntzBot50x.exe and DeathCheck50x.exe into my UntzBot50x2 folder. I just did things backawards is all.
open up the script, change something likeQuote:
How do i add a line in a event script to use the EMP discharge. aka button number 4.