Archived from groups: alt.games.operation-flashpoint (
More info?)
NedFox wrote:
> Markus,
>
> I started on a tool to do this, just because I'm curious if I can make
> one.. The problem I run into is unbpo-ing missions from the
> commandline.. I cannot find any tools which I can run from my program
> which will unpbo any given mission, since all rely on an
> explorer-screen to select the mission (ie. no command line parameters
> to specify the mission and automatically unpbo it).
>
> Any suggestions / tips / links ?
I was told the pbo format was described at ofpec, but someone offered me
a completed commandline depbo/debin tool at that time. So the only
thing i had to do was to call it and go through the unpacked files.
But it is for linux. Maybe it could be compiled for win too, but i am
not sure. I'll have to verify this...
Regarding the database idea i don't think implementing something like
this would be too hard, but the work of keeping it updated, ie checking
all new missions and putting them into the database, providing download
links, etc.
What i think should be in the database:
-checksum of mission, crc32 AND md5 would be best
-name of mission
-number of players
-used addons
-island
-respawn
This could so far be automated.
-type of mission
-options (in slot selection screen)
-tested with version v1.xy
-versions of addons used
This could at best be half-automated.
The reason for the checksum in addition to the mission name is that many
people modify or rename missions. Island and addons obviously help with
missions/servers using addons. So if i have addons x, y and z on my
server i obviously am interested in missions using those addons and
nothing else. Respawn seems to be a "hot" issue too, some people love
it and want to play respawn missions only, others dislike respawn
missions (me for example
😉). With options i mean stuff like limiting
playing time, or difficulty level, or intro, something like that might
be interesting to know in advance.
On a meta level it might be interesting to have:
-mission makers name
-homepage of mission maker
-maybe the option to rate missions (user/testing rating)
-name of tester
This can not be derived from the mission itself (in most cases) but is
interesting too. For one you can give credit to the mission maker. But
you also have those "i liked this mission by Blake/TJ/etc and want to
try his other missions" or the "man, tester xyz has always been dead
on, he seems to have the same taste as i, i wanna try all the he thinks
are good". Last point is obviously only good with an "official" testing
crew.
cu,
Markus