Dev's Limit Breaking 101 Techniques

Update: These limits are cosmetic to the console only. The server will still prompt a default player limit.

I hope this is a good place to post this. After looking around for a while, I found no information for how to change the maximum limit of players for FLServer.exe. If this was posted before, ignore this.

This should be in the same notation everyone else posted in:

flserver.exe 006A3E 80->FF = Increases player multi count to 255, GUI Limit ~Omicron 
flserver.exe 006A3F 00->00 = Multiplier for player count, GUI Limit ~Omicron 
flserver.exe 006C45 80->FF = Increases player multi count to 255, Conditional Check ~Omicron 
flserver.exe 006C46 00->00 = Multiplier for player count, Conditional Check ~Omicron

This works for version 1.1 of FLServer, however it might also work on 1.0.

The “006A3E” offset is the actual player count allowed by the GUI box when you first start the server. By default, it is set to 128.

“006A3F” appears to be a multiplier for the last value. It is set to “00” above, but setting it to “01” multiplies the last value by 2. For instance, it you have it set to 255 characters, this will allow you up to 511 characters. “02” allows 767 in this case, and “03” allows 1023. As of current, FLServer resets input values over 999 back to zero.

The next two offsets are the values used in a conditional statement when you click “okay” on the GUI prompt. Rule of thumb, set these two values to the same values of the first two.

Omicron wrote:
I hope this is a good place to post this. After looking around for a while, I found no information for how to change the maximum limit of players for FLServer.exe. If this was posted before, ignore this.

This should be in the same notation everyone else posted in:

flserver.exe 006A3E 80->FF = Increases player multi count to 255, GUI Limit ~Omicron 
flserver.exe 006A3F 00->00 = Multiplier for player count, GUI Limit ~Omicron 
flserver.exe 006C45 80->FF = Increases player multi count to 255, Conditional Check ~Omicron 
flserver.exe 006C46 00->00 = Multiplier for player count, Conditional Check ~Omicron

This works for version 1.1 of FLServer, however it might also work on 1.0.

The “006A3E” offset is the actual player count allowed by the GUI box when you first start the server. By default, it is set to 128.

“006A3F” appears to be a multiplier for the last value. It is set to “00” above, but setting it to “01” multiplies the last value by 2. For instance, it you have it set to 255 characters, this will allow you up to 511 characters. “02” allows 767 in this case, and “03” allows 1023. As of current, FLServer resets input values over 999 back to zero.

The next two offsets are the values used in a conditional statement when you click “okay” on the GUI prompt. Rule of thumb, set these two values to the same values of the first two.

Does the server is full message work with this hack? I remember once that the discovery main server using w0dk4s server limit hack was full and while trying to connect I didn’t receive the server is full msg but can’t connect to server msg.

That is something I need to research further actually. I never came close to reaching those capacities. It is quite possible though.

Once finals are over, I will look into it. Unless, of course, one of the experts on this can clarify further edits.

Well, those hacks are only for the GUI. There is a lot more involved in patching the max player slots, the most difficult one being to extend the player-connection array in remoteclient.dll which involves messing with .dll section headers, etc…

I released the 200 player hack back in the day so I cannot think of any good reason why you would want to go through the headache again…

This is a huge request, maybe it’s even impossible, I don’t know.
When you are at the equipment dealer and viewing an item’s infocard, you’ll notice two sections: the left hand section is a written text about the item, consisting of headline + text body, whereas the right hand side is an automatically generated stats listing. What I want to be able to do is basically similar to what you have with ship infocards, where you have one infocard containing all the categories, and another one containing all the corresponding values. (ship dealer side only, in space you have both in one infocard)

If it would be possible to have one part of the weapon script saying ids_info, where you could store the text, another one called ids_info1 that contains the categories, and another one saying ids_info2 where you could store the values and these ids_info1/ids_info2 replacing the part that’s auto-generated, it’d be possible to add custom information.

Maybe some of you programmers (looking to adoxa mainly ) could at least have a look at it and say what they think of this. If not, then thanks for reading anyways.

Thanks in advance!

Can i make station can be dock only for absolutely neutral(0.0-0.64) and friendly(0.65-1) players?

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.