BUFFY-3.19.003 Quick Beta (Released)

Denniz

Where's my breakfast?
Hall of Fame Staff
Retired Moderator
Joined
Nov 28, 2003
Messages
11,102
Location
Dallas
Download: Beta1.BUFFY-3.19.003

Released 1/25/2010 - BUFFY-3.19.003

This is a quick beta to test the below fixes. The most important bug being the missing interface issue with non-english characters in the BugPath.

The following is the list of known BUFFY v2 bugs.
  1. Happy / Angry faces not shown in non player cities
  2. Flag hover showing 'beta2'
  3. Vedic Aryans random event linked to Polythesiem insted of Priesthood
  4. BugPath missing interface issue for non-English speakers
  5. 'wonder being build by AI' information that is leaking

Assuming nothing bad comes up we will release this version with the 1.25 update.
 
I can report that the flag hover shows ...

BUFFY 3.19.003.beta1
BUFFY 3.19.003 [Build 29]

I am assuming that the second one is from the DLL and the first one is from modname. The second one looks ok for a proper release ... just need to remember to change the python one.
 
I can report that the flag hover shows ...

BUFFY 3.19.003.beta1
BUFFY 3.19.003 [Build 29]

I am assuming that the second one is from the DLL and the first one is from modname. The second one looks ok for a proper release ... just need to remember to change the python one.
Yeah, I didn't want to have to recompile the damn thing again later since the only thing different is the Mod name. ;)
 
I have a curious question at the moment. I can't test this beta as I've experience some strange issues since installing .002. I have an issue logged over on the BUG forum. Anyway, Asset Checker is bring up errors for both .001 and .002 as I had them both installed - playing .001 for the last BOTM and playing .002 for just normal games.

My question is if there is something inherently different with .002 related to the whole BUG custom asset (CA) compatibility? In other words, is there something in .002 that installs outside the MODS folders to facilitate this BUG compatibility. (Note: I still try to switch out my CA folders when I play BUG 4.2 as CA. I have a 4.2 CA folder and a "vanilla" or "null" folder, both with Blue Marble installed and I use ruff_hi's CA switcher tool)

I'm asking to try to isolate the source of this issue and anything I might not be thinking of. Hypothetically, if you ran BUFFY and forgot to switch CA folders would this screw something up permanently - that is, not just that specific game but jack things up for subsequent games even if corrected. I actually did this for one session of the current BOTM.

Lastly, is the plan for .003 to quickly replace .002 as the official release - even prior to the next BOTM?

Thanks
 
I have a curious question at the moment. I can't test this beta as I've experience some strange issues since installing .002. I have an issue logged over on the BUG forum. Anyway, Asset Checker is bring up errors for both .001 and .002 as I had them both installed - playing .001 for the last BOTM and playing .002 for just normal games.
If you are seeing error messages for both .001 and .002 then you are probably using the version that assumes .001. So it is trying to match .001 checksums against .002. Unless you have changed .001 it should be okay. The only way to check it would be to remove .002 since assetchecker always finds the most recent mod version to check against. There is a new version that has the .002 data files. You should use that to check .002.

My question is if there is something inherently different with .002 related to the whole BUG custom asset (CA) compatibility? In other words, is there something in .002 that installs outside the MODS folders to facilitate this BUG compatibility. (Note: I still try to switch out my CA folders when I play BUG 4.2 as CA. I have a 4.2 CA folder and a "vanilla" or "null" folder, both with Blue Marble installed and I use ruff_hi's CA switcher tool)

I'm asking to try to isolate the source of this issue and anything I might not be thinking of. Hypothetically, if you ran BUFFY and forgot to switch CA folders would this screw something up permanently - that is, not just that specific game but jack things up for subsequent games even if corrected. I actually did this for one session of the current BOTM.
I will leave this to ruff or EF to answer.

Lastly, is the plan for .003 to quickly replace .002 as the official release - even prior to the next BOTM?
The plan is to release .003 on the 25th with the update (approx 6pm CST). I don't know which version the GOTM staff plans to use.
 
My question is if there is something inherently different with .002 related to the whole BUG custom asset (CA) compatibility? In other words, is there something in .002 that installs outside the MODS folders to facilitate this BUG compatibility. (Note: I still try to switch out my CA folders when I play BUG 4.2 as CA. I have a 4.2 CA folder and a "vanilla" or "null" folder, both with Blue Marble installed and I use ruff_hi's CA switcher tool)
My understanding (and EF knows this better) is that 001 hated BUG in CA and resulted in no interface issues. 002 doesn't care one way of the other.

It is all related to finding the BUG / BUFFY set up files (the xml config files). BUFFY 001 found BUGs under CA and got confused when it couldn't find BUFFY.XML. BUFFY 002 knows to ignore any config files it funds under CA (or to only look under BUFFY 002 mod folders.
 
Thanks for your response. I'm still a bit confused and not sure if I can get to the source of the problem. I probably wrote up too much info in my first post which I tend to do, especially when I don't fully comprehend something - like asset checker. I'm going to list out issues/steps tersely:

1) BUG 4.2, BUFFY .001 & BUFFY .002 installed
2) BTS is acting oddly since .002 installed
3) Ran Asset Checker - shows tons of "File Not Found" errors for 001 and 002 (the files are actually there though)
4) Uninstalled BUG 4.2, Deleted Buffy 001 and 002 MOD folders
5) Deleted current Custom Asset folder FWIW
6) Ran Asset Checker - shows tons of "File Not Found" errors for for BUFFY 001 only

Is this indicative of some unrelated issue? Or, related to my early question, is there someplace outside the MOD folder that was impacted by the BUFFY installs that I have not thought of or addressed?

thanks
 
Let's see if we can diagnose things but stepping through the releases.

Try this (assumes no mods installed):
  1. install BUFFY .001
  2. run assetchecker (v2.2)
  3. save results
  4. install BUFFY .002
  5. download and install assetchecker v2.2.1
  6. run assetchecker (v2.2.1)
  7. save results

If you have any errors send the results. (make sure you identify versions ;) )
 
hmmm...didn't realize there was a new version of assetchecker. I can't even remember where I got it.

Also, I really didn't plan on installing 001 again since it's basically defunct now and I finished up the last BOTM. I'll try this with 002 and the new asset checker and see what comes up.

thanks

edit: i figured out where assetchecker is...forgot that it's specifically for all things HOF
 
Okay...I reinstalled what hopefully is the latest version of 002 and downloaded the AC v2.2.1. Everything came back clean.

So please forgive my complete idiocy here, but basically AC checks that a version of the HOF/BUFFY mods are installed and installed correctly. Therefore, if you don't have a version installed it will return errors. Likewise, it's conceivable that using AC 2.2 and having both BUFFY 001 and 002 installed would produce some unusual results.

Of course, this doesn't necessarily explain the peculiar things I was running into while playing, it's possible that reinstalling all this stuff may solve the issue anyway. Also, it may have been a result of playing one of the forum games and running into some compatibility issue with that save. It appears I can play for now.

thanks for your help and sorry for the baffling stupidity on my part:confused::crazyeye:
 
Just a minor thing:
On the BUFFY download page it has the line BUFFY 3.19.002 can be downloaded from >> here << (2.81Mb). The link points to 3.19.003 of course, but the label confused me.
 
Back
Top Bottom