Warzone 2100 Forums

aubergine wrote:For stuff I don't want to save I create a global function and then use it as if it were an object

I was considering pre/post events for las sat strikes and save, but was worried it might be overkill. I guess it's more semantically correct to separate them out, but I usually just use events to trigger code elsewhere (eg. trigger code within an OO structure), for example:

Code: Select all

function eventGameSave(before) {
  if (before) { // generate saveable data objects
    PersistanceMgr.prepareForSave();
  } else { // clear down saveable data objects
    PersistanceMgr.tidyAfterSave();
  }
}

function eventGamePreSave(before) {
    PersistanceMgr.prepareForSave();
}

function eventGamePostSave(before) {
    PersistanceMgr.tidyAfterSave();
  }

events.PreSave.bind(PersistanceMgr.prepareForSave);
events.PostSave.bind(PersistanceMgr.tidyAfterSave);

I like the idea of an eventLoad() but at what point would it be called - before or after eventGameInit / eventStartLevel?

I currently handle the load scenario like this:

Code: Select all

function eventStartLevel() {
  if (typeof loaded != "undefined") PersistanceMgr.gameLoaded();
  eval(null,"var loaded = true;"); // if game is saved then loaded, we'll detect this next time evnetStartLevel runs
}

define it as global variable and check if it is True

// var loaded // in main scope
if (!loaded) {
loaded = True
}

aubergine wrote:objectExists(gameObject)

A function that returns true if gameObject exists, or false if it doesn't.

There are still scenarios where I really, really desire to temporarily cache some game objects to avoid doing masses of repeat processing on a subsequent game tick. Obviously, those objects could get killed before I get round to acting on them, so a way to find if an object exists without causing exceptions (which are slow and have to be trapped) would be most welcome.

aubergine wrote:There is already objFromId(), which is a useful function in it's own right, but I'd like in addition the objectExists(gameObject) function (or maybe just pass in it's id as sometimes that's all i'll have) to simply check whether the object is still present.

aubergine wrote:Ah, cool. Last time I used it it threw an exception if object didn't exist.

aubergine wrote: Ability to dump short strings to log file
I always imagined debug() would do this, but it seems not. I'd like the ability to do something like log("short string") and have it go directly to the log file.

aubergine wrote:The reason I want to be able to put stuff in to log file, without throwing exceptions, is so that once my AI is out in the wild people can send me their logs and I can see what my AI has been up to (as no doubt it will do lots of stupid things that I'll want to rectify).