Recent content by Caesium

Nice idea, the overlay screen, but how to trigger/disable it?

Why don't you read the BtS-Version from the xml and then trigger with python, which version of event signs has to be used? The version is found in GlobalDefines.xml <Define> <DefineName>CIV4_VERSION</DefineName> <iDefineIntVal>317</iDefineIntVal> </Define> In 3.13, I think, this will...

At the first and at second glance there is no more error.

The error shows up in the logfile, even with 1601.

This is my link: "D:\Civilization 4\Beyond the Sword\Civ4BeyondSword.exe" -mod="BUG Mod" (just added >>-mod="BUG Mod"<< to a copy of the standard bts-link) I just doubleclick this shortcut and the attached message appears.

While loading the game during checking python.

I am able to play BUG, but, when starting the game (doubleklicking on desktop) while checking Python this error shows up (only once, then never while playing, only if you restart/relaunch the game itself, it comes up again).

Not on every system the following path is the correct path to my documents. "C:/Documents and Settings/[UserName]/My Documents/My Games/Beyond the Sword" For me, for example, this is: "E:\Eigene Dateien\My Games\Beyond the Sword"

It doesn't only show up with my merge. It also shows up, if I take BUG and try to start it as a standalone mod (svn 1586). I wasn't able to test your latest svn yet. Just tested 1596, there's this message also.

Can't await the moment you release your next version with bbai 0.45 ;)

For me it happens, when starting BtS playing BUG as a mod.

I cannot answer this question, because I'm just posting bugs, which my beta testers had while testing my mod. :) Thanks a lot :) I'm using your code, but with a growing number of .py files things like this will happen much more often, I think.

An old bug returned with your latest changes: ..\WARLORDS\ASSETS\PYTHON\SYSTEM\xmllib.py:9: DeprecationWarning: The xmllib module is obsolete. Use xml.sax instead. ERR: Call function onEvent failed. Can't find module CvEventInterface

Your "Go To and Sentry" (Hotkey: X) doesn't work for me. I merged it into my sdk, but its effect is the same as the standard "Go To" - the unit doesn't sentry (no enemy visible).

Just have look at post #1.