How to protect pre-c5 movies?

Player Questions Started Last reply 15 posts
How to protect pre-c5 movies?

With the advent to c5 approaching many would like to protect the gameplay movies we produced in c4.

This thread should be devoted to creating a stable copy of c4 LineageII which has the minimum size necessary to allow presentation of c4 movies. I say the minimum size since I think I can safely say we would all like to be able to create such a legacy file without adding 5GB of contiuously reserved space on our hard drives.

Since many of the actual game files would become deleted the resulting file would be only useful offline.

An example of a file that I believe can be safely deleted from the legacy copy without affecting the stability of the movie playing file:

C:\Program Files\Lineage II Chronical 4 copy\crest

Further suggestions would be appreciated...
ok my first try of running this copy without being online and using the l2.exe file crashed with a gameguard error.

any suggestions?
None which wouldn't involve patching the l2.exe file (thus breaking the EULA), since if you don't do so, L2 either updates to C5 the next time you start it, or doesn't start with the error "update servers not available" or something like that.
if you login through l2.exe in systems folder it doesnt patch, so you can keep your's copy of C4 unchanged for the movies.
You must have some really important movies to go through all this trouble just to be able to watch them again o_O
I know I do.
Me too. Though probably not as important as Ellie's, I'm pretty sure..
I mean, you record stuff for a reason, right?
Recorded demos never ever really work when there are major version changes to a program.. unreal tournament/quake.. them all ;)

Fraps imo is the only way to hold onto something solid.

Recorded demos never ever really work when there are major version changes to a program.. unreal tournament/quake.. them all ;)

Fraps imo is the only way to hold onto something solid.



although this statement is not to the point of this thread it does imply something unpleasant ... c4 movies may not be able to be saved ...

any more suggestions please ...
They can be saved.... You just have to have the C4 client installed to play them back!

Really, why cann't we the player base come up with such a player. I have a basic idea of what i'm thinking of, but i don't know of any stand alone player for any recorded unreal recording.
It's just hard because I like to be able to watch replays and scan around different angels looking at stuff. Fraps limits that ...
Simply copy your L2 folder, then delete the lineage2.exe file and use l2.exe to start the game (deleting lineage2.exe makes it so you never accidently start it up like that and it starts patching and ruining the client).

The only problem is when gameguard messes up, you're out of luck, you will be unable to start the game or play replays.

Its also a good idea to just in case keep a downloaded installer of C4 handy, so you can reinstall if it goes bad.

And no you can't just "make" a replay program for Lineage 2. It would have to be a massive program and it would be illegal.
there is none.

the way the demo "replay" records is usually as efficient as you can get with minimal file size. but the whole thing is based on the fact that you NEED the entire SAME VERSION of the game to play it back, and patches applied after a recording that may DIRECTLY effect the replay will seriously mess it up. (For example if an exploit was used and recorded and then ncsoft patched it, then you installed that patch and tried to replay that replay, you'd most likely see a completely screwed up replay).

Theres simply no way around it, you can't get a standalone replayer without having the game and all the content to load it up with, your best bet is to have a full C4 installation set aside and hope that it never gets messed up.
If only NCSoft would develop a program that would revamp the c4 demos.....Changing all the File References and such so that it was able to be played on the C5 Client (Find [yyyy.staticmesh] Replace with [zzzz.staticmesh])....would take a lot of time to get it initially working but it would be nice once finished....(I'm not 100% sure if this is all that would be needed but it is my understanding of how they might have implemented the replay's recordings.)
actually that's the only really viable option ncsoft would be able to provide.. and really shouldn't take that long.

Aside from having to create the program from scratch to do it, as soon as they do it though, they'd be able to add a little bit more code every time a new update is made without much hassle.

Replay Patcher would be easiest.