Not without a lot of hex hacking, Alcander did it with the freelimits patch but a lot of people have problems with it freezing the flserver.exe & freelancer.exe

**shuffles of with a new headache**

there are unlisted cruise properties that might be of some interest, although they produce the same end-cruising-speed they give the effect of one engine being slower to accelerate/ slower to correct course in cruise.
cruise_accel_time = the higher, the longer it takes to accelerate
cruise_drag = set it to 0 to make changing course in cruise impossible, hehe

I didn't know cruise_drag yet, thanks!

I presume it should be in data\constants.ini under [EngineEquipConsts ?
But then, how does it affect an individual engine?

And what is it's default value?

its an {Engine} property and therefore unique to the {Engine} archetype
default is 599 i guess, since cruise handles the same as impulse and the standard drag is 599

So, maybe i can change the "cruise_drag" to change cruise speed?
Hm, I think I´ll try that out.

well there is another way to achieve per ship, unique cruise speeds.

Every actual engine that is mounted internally on a ship gets cruise. EG:

You add one engine, the default that lets you go the 80. Now, create a new engine and only let it give a top speed of 20 (25% the base default). This will givve you the base cruise speed plus the 25% increase that will not be available to ships that do not have this 'extra' engine added. This is because in effect you are also adding a second cruise engine too.

Roland "Hobbes" Orr
Mod Dev Team: Monkey Universe
Founder: http://www.samuraistudios.net

OK, I´ve tried out the cruise_drag thingy, didn´t work.
That idea with adding another engine sounds good, but then you have to add one to every single loadout.