Dev's Limit Breaking 101 Techniques

content.dll	0CC985	40->00 = jump gates test reputation ~adoxa
content.dll	0CC986	0C->04 = jump holes test reputation ~adoxa
content.dll	11BCF4	-0.6f = hostile docking reputation ~adoxa

```Trade lane docking seems to ignore reputation altogether, so would have to delve deeper and do a plugin for that one.

@Aigle: Could probably do that, some day… What type of extra information do you want, though? If it's only what's defined by the ini, be better off doing customisable dynamic stats. In either case, I don't think it's a suitable discussion for this thread (it'll be a plugin, not an edit).

adoxa wrote:

content.dll	0CC985	40->00 = jump gates test reputation ~adoxa
content.dll	0CC986	0C->08 = jump holes test reputation ~adoxa
content.dll	11BCF4	-0.6f = hostile docking reputation ~adoxa

```Trade lane docking seems to ignore reputation altogether, so would have to delve deeper and do a plugin for that one.

WOW! Big amaze! Thank you adoxa!

Thanks Adoxa this is a great find.

Oops, I had jump holes wrong, updated the post (jump holes are 800, so I should have removed 8 from C, not made it 8; 400 is the airlock, btw).

Hello adoxa! Are you still just planning the plugin which adds additional hp_x_special_x slots, or there are some results?

adoxa wrote:
Oops, I had jump holes wrong, updated the post (jump holes are 800, so I should have removed 8 from C, not made it 8; 400 is the airlock, btw).

And other two is works very very very much very good! TESTED

@Nova: Long way off, sorry.

Thanks for the reply adoxa, I thought about information that covers background information like the manufacturer or the year it was introduced plus some other stuff that can’t be automatically.

Louva asked me in an IM if ships could drop out of cruise once power runs out. He’s offline atm, so I’ll post it here for all to use.

# Drop out of cruise once power reaches 0.
# Jason Hood, 18 November, 2010.

File: common.dll
03659E: 79				[ 4F ]
036618: 8B 8E 94 01 00 00 EB 14		[ 90 90 90 90 90 90 90 90 ]
036634: 6A 00 E8 A5 D5 03 00 EB B1	[ 90 90 90 90 90 90 90 90 90 ]

```He also asked if power could have an activation delay like shields, but that can wait for another day…

freelancer.exe	08AEBE	20f = drop cargo dialog timeout PART 1 ~adoxa
freelancer.exe	1D2688	20f = drop cargo dialog timeout PART 2 ~adoxa
content.dll	118130	20f = time given to drop cargo ~adoxa

Hey,

After using adoxa’s hack so that you drop out of cruise once you run out of power (which works great btw), I wanted to know if it is possible to do the same thing with sheilds? So that if you run out of juice both your engines and sheilds die.

Thanks
Ozed

I don’t see it as necessary. When shields are charged, they’re independent of the power supply, so losing power shouldn’t mean losing shields. As they’re drained, though, they only recharge if you have sufficient power.

Just wondering, is there anyway to activate the damage_per_fire line in weapon entries, i assume it is the damage done to the weapon on shooting, but it seems to have been disabled.

Thanks
Ozed

thats incorrect, damage_per_fire means the weapon does damage to the user when it is fired.

Really, i always though it would be for damaging the weapon so as to simulate wear. Either way i haven’t every seen it work.

Just wondering how you found that out?

Ozed

Dragnite_MU wrote:
thats incorrect, damage_per_fire means the weapon does damage to the user when it is fired.

hmmm, how does that work then? not getting at you, but how did you come to that conclusion?

by default - damage_per_fire = 0

changing it does not seem to do anything, like oZed, I assumed that it was some legacy code left in for simulating weapon wear…

@adoxa

adoxa wrote: shields

lol, subtle

or maybe it was the original method of how much damage a weapon dealt before they separated it into shield/hull!

Whatever the case, I’m not even sure the game reads them.

It reads (and stores) damage_per_fire, but does not (apparently) use it. As Ozed, I took it to mean damage to the weapon itself. Added to the todo…

Guess it would make sense, most weapons need some sort of maintenance. Would give players something else to think about if weapons had to be serviced, if it could be applied in such a way that the weapon simply stopped firing when it ran out of hitpoints as opposed to being destroyed, that would be good.
I highly doubt the possibility of such an approach in this game, but it would be fantastic if a weapons accuracy, range, power it uses to fire etc became less efficient the longer it goes without service.
Same could be applied to shields, recharge slower. Engines could become less efficient, take longer to accelerate, cruise charge etc. Could apply it to anything, but this game was never meant to have depth, shame.