Dev's Limit Breaking 101 Techniques

NeXoSE wrote:

http://adoxa.110mb.com/freelancer/tools.html#flcolors
http://the-starport.net/freelancer/download/singlefile.php?cid=5&lid=2404

BTW: i still cannot send email to you, please give another one address.

I was change those color, I mean is (see the picture at the arrow):

I want to change those blue color fonts.

Try the rich fonts file.

http://the-starport.net/freelancer/forum/viewtopic.php?post_id=24258#forumpost24258

Search for the colour hex codes, to find the blue.

robocop wrote:
Does anyone have a hack that would narrow the window of the player jumpin point when using jumpgates/jump holes?

Right now a player spawns at a random point within +/- 550m of the jumpin point when jumping into a system. I’d like to narrow that window to 50m, or even tighter for a specific jump. I’m going to guess it’s an all or nothing deal, i.e. if you do it for one it will work that way for all, but I can deal with that.

Up
guys no one has found it?

server.dll	0231BF	-350f = jump gate/hole z-axis entry point adjustment ~adoxa
server.dll	0876C0	500d = jump gate/hole x- & y-axis entry point adjustment ~adoxa

Is this an all or nothing ‘fix’ or can it be tied to the jump_out_hp?

In other words, changing this entry in server.dll would make the jump out points tighter across the board, ie. every jumpgate, every jumphole, etc. I can deal with that, it’s better than what we have now.

It would be cool though to have it tied to the jump_out_hp for even a specific hole. My purpose for this would be to have players be able to jump INSIDE the lair core instead of possibly inside but more probably outside.

can`t be a ini entry from a plugin ?

adoxa thank you! thank you! thank you!

Works like charm!
Again, thanks adoxa.

Jump Out Point allows each [Object] to have its own parameters (via a separate file, not within the [Object]).

outstanding !

sumanuti wrote:
Works like charm!
Again, thanks adoxa.

I like the video. Is that in single-player or multi-player?
How’d you get out after undocking?

I was never able to get the generator/shield thing to work. ie. Kill the generators, the shield drops.

adoxa wrote:
server.dll 0876C0 500d = jump gate/hole x- & y-axis entry point adjustment ~adoxa

I found this value when I switched the viewer to DOUBLE FLOAT (IEEE, 64bits). Is that correct? It stretches from 0x0876c0 to 0x0876c7. It’s also a single value. How do you adjust for each (x and y) axis?

Thanks much for doing this Adoxa.

robocop wrote:

sumanuti wrote:
Works like charm!
Again, thanks adoxa.

I like the video. Is that in single-player or multi-player?

MP - the Dyson Destroy is next mission!

How’d you get out after undocking?

Before HARD! Now EASY!

I was never able to get the generator/shield thing to work. ie. Kill the generators, the shield drops.

One stuff kills with fuse other stuff that wears a SHIELD.

Wow nice, thanks.

@robocop: The original value is indeed double, used for both the x and y axes. Since I wanted separate values, the plugin makes patches to convert the double into single, thus also making room for another value.

All right, if I’m reading the info correctly I need to:

• copy the plugin (jumpoutpt.dll and accompanying files) to the EXE folder
• add the jumpoutpt.dll reference to the library in dacom.ini and dacomsrv.ini and
• create a JumpOutPt.ini file in DATA\UNIVERSE with the following contents (example shown, not actual):

[JumpOutPt]
;default = 500, 500, -350 ; original values
Li02_to_Li01 = 500, 500, -350, 0 ; always on the right
Li03_to_Li01 = 500, 500, -350, 90 ; always on the top

Does EVERY hole need to be addressed, or only the ones that are changed from default?

robocop wrote:
All right, if I’m reading the info correctly I need to:

• copy the plugin (jumpoutpt.dll and accompanying files) to the EXE folder
• add the jumpoutpt.dll reference to the library in dacom.ini and dacomsrv.ini and
• create a JumpOutPt.ini file in DATA\UNIVERSE with the following contents (example shown, not actual):

[JumpOutPt]
;default = 500, 500, -350 ; original values
Li02_to_Li01 = 500, 500, -350, 0 ; always on the right
Li03_to_Li01 = 500, 500, -350, 90 ; always on the top

dacom.ini is not needed.
Change only from a server side, no mod update is needed.
Think so?

Does EVERY hole need to be addressed, or only the ones that are changed from default?

correct answer!

very good
thanks.

sumanuti wrote:
dacom.ini is not needed.
Change only from a server side, no mod update is needed.
Think so?

I’m not sure about that, the directions specifically state both. I’ll try it either way to see.

You need dacom.ini (client) for single-player or dacomsrv.ini (server) for multiplayer.