I'd still like to give it a shot. Is there anyway I can do it locally without triggering anti cheat? I assume modifying the ini for the actual cloaking device to use the other effect instead would most definitely trigger anticheat.
The main issue is the Osiris effect being too small for other battleships. The effect does not adjust to the ship size or shape, so on larger ships like the Rheinland battleship, you won't see much of the effect as most of it will be inside the ship model.
Also, general rule of thumb regarding the client-side changes and anticheat: Don't touch any .ini files, as the majority of them are watched by the anticheat and since even if 1 line is watched, any alteration in the file will cause a trigger and either a kick or autoban, it's usually not a good idea.
If you really want to give it a shot, though, you can try finding the actual effect files for Marduk cloaking and replace it with Osiris cloaking files. I'm not sure if that'll work, but having tried it on guns and engines and somesuch before, there's a good chance that it does. (Note that even this option might trigger the anticheat, so you'd better try it on a local server with the latest version of the FLhook with disco plugins before going on GC with it)
(04-17-2013, 04:53 AM)aerelm Wrote: The main issue is the Osiris effect being too small for other battleships. The effect does not adjust to the ship size or shape, so on larger ships like the Rheinland battleship, you won't see much of the effect as most of it will be inside the ship model.
Also, general rule of thumb regarding the client-side changes and anticheat: Don't touch any .ini files, as the majority of them are watched by the anticheat and since even if 1 line is watched, any alteration in the file will cause a trigger and either a kick or autoban, it's usually not a good idea.
If you really want to give it a shot, though, you can try finding the actual effect files for Marduk cloaking and replace it with Osiris cloaking files. I'm not sure if that'll work, but having tried it on guns and engines and somesuch before, there's a good chance that it does. (Note tha t even this option might trigger the anticheat, so you'd better try it on a local server with the latest version of the FLhook with disco plugins before going on GC with it)
I was actually just about to edit my post.
I started up a test server, using FLHook 2.0.0 that launches when you launch the server from Launchpad
on dsy_cloak_3 in weapon_equip.ini, no fuss from Anticheat on local server. I suspect that might be that FLHook is reading the same files that I'm editing for Freelancer though.
I changed the inis after FLHook and the server were loaded, but it never kicked me. Cloaked and uncloaked multiple times on it, took away the character admin to be sure that that was not protecting it.
I figured there would be some sizing issues with the effect, but I'm just looking for something different from the Nomad cloak effect right now. Indeed, some of it is rather comical.
On an Osiris, the cloak in effect is a bit too low and to the rear, probably because of where the countermeasure slot is, but the cloak out effect is spot on.
On larger ships like a Nephilim though, the effect falls...a bit short, heh. Cloak in gets the rear half of the ship.
Cloak out is slightly better but nowhere near the whole ship.
Even though it doesn't trigger anticheat on my local server with FLHook, I'm still wary about doing it on the actual server. Is the anticheat on the server the same as what comes with FLhook in Launchpad?
(It's been awhile since I delved into Freelancer ini files, I used to do this back in the day...)
Addendum: I copied the Discovery Installation folder and launched FLHook/Server from there, confirmed it was loading the weapon_equip.ini from there with ProcMon, then launched the client from the original folder with the changed cloak weapon_equip.ini, still no peep from anticheat.
(04-17-2013, 04:53 AM)aerelm Wrote: The main issue is the Osiris effect being too small for other battleships. The effect does not adjust to the ship size or shape, so on larger ships like the Rheinland battleship, you won't see much of the effect as most of it will be inside the ship model.
Also, general rule of thumb regarding the client-side changes and anticheat: Don't touch any .ini files, as the majority of them are watched by the anticheat and since even if 1 line is watched, any alteration in the file will cause a trigger and either a kick or autoban, it's usually not a good idea.
If you really want to give it a shot, though, you can try finding the actual effect files for Marduk cloaking and replace it with Osiris cloaking files. I'm not sure if that'll work, but having tried it on guns and engines and somesuch before, there's a good chance that it does. (Note that even this option might trigger the anticheat, so you'd better try it on a local server with the latest version of the FLhook with disco plugins before going on GC with it)
Actually your wrong, changing the INIs coding that dictates special effects has no bearing on anticheat as I have done it before without problem.
So I can change the Cloak Effect to desired one, I can change the colour of engine flames like the Bret BS I have has a Kusari BS Flame and it looks great such changes do not effect anti cheat as they are not interfering with game mechanics if I tried the change the lines that dictate cruise charging time then that would trigger anticheat.
Engine Equip ini has lines that dictate which flame colour you have aswell as physical things like cruise charge time etc.
Since just changing the Engine Colour Line will not trigger anticheat but changing the cruise charging time line will and both lines are in the same INI indicates to me that anti cheat scans all INIs for cheats and it has a list of lines per ini which it is looking for changes within to be counted as a cheat.
There are some complete inis that cannot be changed in any way without it being counted as a cheat, as all lines within that ini are put on the anti cheat list for e.g. Shiparch.ini cannot be changed at all.
However any special effect you make is only seen client side other players will see the effects they have programmed in.