Home   Help Search Login Register  

Author Topic: $STRN_OOK? pbo incompatibilities  (Read 894 times)

0 Members and 1 Guest are viewing this topic.

Offline Mikero

  • Former Staff
  • ****
  • ook?
    • Linux Step by Step
$STRN_OOK? pbo incompatibilities
« on: 03 Dec 2005, 01:43:20 »
I've 'discovered' a really peculiar 'undocumented feature' with pbo's versus exploded folders.

Perhaps others know of this, perhaps there's a workaround, sure glad if someone enlightens me.

The 'bug' is that STR text messages cannot be found inside the stringtable.csv under certain conditions. It is _specifically_

~/opflash/missions/AMission.Eden         //works fine
~/opflash /missions/AMission.Eden.pbo // works fine
~/opflash/missions/AFolder/Amission.eden.pbo // works fine
~/opflash/missions/AFolder/Amission.eden  // fails

This is the content of a description.ext that falls over
Quote

    class STR_res2
    {
        name = "STR_res2";
        sound[] = {"say2.ogg", db-20, 1.0};
        title = $STR_res2;
    };

this is the (obvious) content of the stringtable.csv

Quote
Language,English,Comment

STR_res2, "Hi Folks",  sigh
-----
In other words, if you place your exploded mission in a subfolder of missions (or for that matter Res/Missions) you get this bug.

I think I know why pbo's are treated differently: because all pbo's including addons, are part of the engines root heirarchy and held 'in memory'.

But, this 'error' comes up more that you'd think, especially if you're in ~user/ inside the Editor!!!
----

comments welcome
Just say no to bugz