Battlezone Forums

ai.autopilot

Yeah, i miss that.

I vote to re-enable it in bzone.exe

I never knew about that, when did it stop working?

AHadley wrote:I never knew about that, when did it stop working?

PB3 at least

It still works, but only in bz2Edit.exe

Zero Angel wrote:

AHadley wrote:I never knew about that, when did it stop working?

PB3 at least

Makes sense,that's about when I showed up.

Unfortunately the banlist.ini file gets overridden (= set back to default) with every patch. So better make a copy of it before patching the game.

Since the adviced install routine is to use a clean install, it should not matter as long as you follow that advice.

I never install 1.3 on a "clean" install

As long as you upgrade from an OLDER patch, it renames the addon/saved/logs/ folders involved, and, unless you've done something REALLY odd like put something in data/, it should work fine.

Doesnt it even do so when you install over the basegame (renaming folders)?
I recall it does, wasnt sure so simply didnt mention it.

Yes it does it on a clean install too.

But I found it doesn't do it if you install on a NEWER patch, like if you try to install PB3 over PB6.4.

Nobody wastes time trying to make software reverse compatible, downgrading or back patching is just not something people should do.

Pretty much

General BlackDragon wrote:Yes it does it on a clean install too.

But I found it doesn't do it if you install on a NEWER patch, like if you try to install PB3 over PB6.4.

I actually find that weird.
As if the code says:

if 'addon' = empty or lesser PB
properly upgrade
else if 'addon' = higher PB
screw user
end if

Why on earth would you want to code something like that and not simply deny the installer to be used on a higher PB?

That's odd behavior. I thought I coded it so that it checks for a file w/ a specific name, exactly. (No nonsense of trying to find earlier/later or greater/lesser, just equal or not). And if the current PB's check file isn't there, then rename off addon and start anew.

-- GSH

Ah, that might have been the case. IIRC I was trying to install a test build onto a slightly newer version.