Multiple non-conflicting mods

[Bobingabout]

what exactly are you talking about, because it looks like you are not all on the same page here...

[Marshall]

The YR scripted video files (.ipb) will only play correctly on the exact same mod that they were recorded on. Never tested myself, but I imagine running on a different mod would cause weird behaviour, no behaviour, internal errors, or a mix of all three.

Launch Base will ensure video files are saved and read from the correct mod folder, but won't stop problems resulting from a mod being updated. So I suggested the possibility of making the installers automatically remove old video files - but Renegade points out that this will confuse and annoy some people.

[Renegade]

The YR scripted video files (.ipb) will only play correctly on the exact same mod that they were recorded on. Never tested myself, but I imagine running on a different mod would cause weird behaviour, no behaviour, internal errors, or a mix of all three.

It results in the same mess every scripted sequence with changed base rules ends up in: It instructs your units to do the exact same stuff as when recorded, but it doesn't make any sense, because it's not the same anymore.

e.g. if, in the original game, two Grizzlies tried to defend their base against three Prism Tanks, got owned, you died, and, as a result, you increased the Grizzly's firepower, then, the next time you'd play the "video", the same battle would be started, but your Grizzlies would 0wn the Prisms, they'd never destroy your base, and everybody would just sit on the map and be confused why the game hasn't ended yet.

Launch Base will ensure video files are saved and read from the correct mod folder, but won't stop problems resulting from a mod being updated. So I suggested the possibility of making the installers automatically remove old video files - but Renegade points out that this will confuse and annoy some people.

How about big, unignorable warning messages and indicators?
e.g. filename: some_video_mental_omega_1.53.ipb
installed mod version: 1.61

________________________________________
WARNING!
The video you are trying to play was recorded with an older version of this mod. It will most likely not play correctly, and could, potentially, start an endless game or even crash.

Are you very sure you want to play this video?
[ Yes ] [ No ]
________________________________________
________________________________________
Please confirm that you have read the previous message.
[ I did ] [ I didn't ]
________________________________________

if(!confirm) goto firstMessage;

[Bobingabout]

[quote=Marshall]
Are you very sure you want to play this video?
[ Yes ] [ No ]
________________________________________
________________________________________
Please confirm that you have read the previous message.
[ I did ] [ I didn't ]
________________________________________

you tend to swap them around so people have to even think about ignoring it, else they could simply double click.

[Marshall]

I had been planning on letting the user choose the filename of the video when YR closes. But perhaps a date, time, mod version would be quicker. Users could then choose to rename the file manually - in which case need to get program to accept unformatted filenames too.

[DCoder]

Update: my DLL can now successfully extract audio.bag (and random other files I tried).

[Marshall]

Shweet. DCoder, without you this project would be nothing.
I really need to get a move on and finish the install-maker, then we'd be fast approaching a beta test.

[Renegade]

you tend to swap them around so people have to even think about ignoring it, else they could simply double click.

The point was less to actually make them read it, but to cut complaint threads short:

"OMFG MY VIDEO DOESNT WROK ANY MORE!!!"
"You specifically confirmed you had read the notice about the dangers of playing videos from older versions. Closed."

[Marshall]

A note on how to use shortcuts to mods:

LaunchBase.exe -game mymod
Will automatically launch the mod contained in the "mymod" folder, and close Launch Base when YR closes.

LaunchBase.exe -play
Auto displays Play Video dialog when launching a mod, even if option is turned off.

LaunchBase.exe -play myvideo.ipb
Will cause myvideo.ipb to automatically play if it is available for the mod you are launching. If it isn't, then the Video selection dialog will be shown.

LaunchBase.exe -game mymod -play
Auto launches mymod, and auto displays Play Video dialog even if options is turned off. Closes LaunchBase when YR closes.

LaunchBase.exe -game mymod -play myvideo.ipb
Auto launches mymod, auto plays myvideo.ipb, and closes LaunchBase when YR closes.

[VK]

My opinion:
*add "record game" option
*remove "Run in window"

[Bobingabout]

*remove "Run in window"

why? i use that option sometimes.

i don't even see the point in recording the games... not unless you can play it back afterwards in windows media player, or bink, or something like that.

[Nighthawk]

Windowed mode only seems to work in 16 bit colour mode according to the error messages it gives when you try to start it if your computer is in 32 bit mode.

[Bobingabout]

i have other games like that, so, switching to 16bit colour isn't a major concern.

[Nighthawk]

It would be a lot easier if there was some option in windows to run a program in 16 bit colour, like there is a 'Run in 256 colours option'. Anyway, run in window should be kept in, but perhaps give some sort of warning that your computer needs to be set to 16 bit colour, or if it's possible, perhaps it could change the colour depth for you.

[VK]

Because it work not correctly 75%
However, I use it to debug