PLUGIN-List regarding serverside/clientside-questions

[J.R.]

Here is a list of some plugin.dll´s by ADOXA and other authors and the way to use them in FL-Mods regarding the client- and serverside settings.
Maybe somebody will find it useful…
To answer a sometimes upcoming question in advance: SOME of the plugin.inis DONT work when encrypted ! So DONT bini-compress them as long it is not mentioned/indicated in this list !

FLHook.dll has to be loaded and configured serverside only in dacomsrv.ini.

jflp.dll has to be loaded and configured clientside only in dacom.ini.

HudShift.dll has to be loaded clientside only in dacom.ini. The offsets are defined in a hudshift.ini in DATA/INTERFACE Folder.

chatlog.dll has to be loaded clientside only in dacom.ini.

numeric.dll has to be loaded clientside only in dacom.ini.

NoNavMap.dll has to be loaded clientside only in dacom.ini. The systems are defined in a DATA/UNIVERSE/nonavmap.ini.

Ammolimit.dll MUST be loaded clientside in dacom.ini AND serverside in dacomsrv.ini. The limits are defined in DATA/EQUIPMENT/weaponequip.ini which CAN be bini-compressed !

PersistentDestructibles.dll has to be loaded clientside only in dacom.ini.

EquipDrag.dll MUST be loaded clientside in dacom.ini AND serverside in dacomsrv.ini.

Cloak.dll has to be loaded clientside only in dacom.ini. But the settings can be configured serverside with FlHook.
If you are going to rename your “Freelancer.exe” the name of the renamed “freelancer.exe” in cloak.dll MUST be written in lower case to work !!! HOW-TO –-> https://the-starport.net/freelancer/forum/viewtopic.php?post_id=60696#forumpost60696

Criticalhit.dll MUST be loaded clientside in dacom.ini AND serverside in dacomsrv.ini. The hit-chances are defined in DATA/EQUIPMENT/weaponequip.ini which CAN be bini-compressed !

TurretZoom.dll has to be loaded and configured clientside only in dacom.ini.

chklootvol.dll MUST be loaded clientside in dacom.ini AND serverside in dacomsrv.ini.

MPRep.dll has to be loaded clientside only in dacom.ini.

Moors.dll MUST be loaded clientside in dacom.ini AND serverside in dacomsrv.ini.

DelayDisplay.dll has to be loaded clientside only in dacom.ini.

GroupMine.dll has to be loaded serverside only in dacomsrv.ini.

GaugeCol.dll has to be loaded clientside only in dacom.ini. The Gauge-colors are defined in a DATA/INTERFACE/gauges.ini.

TerritoryMP.dll has to be loaded serverside only in dacomsrv.ini. The systems/Territories are defined in DATA/UNIVERSE/universe.ini serverside AND clientside which CAN be bini-compressed !.

MultiUniverse.dll has to be loaded clientside only in dacom.ini. The Sectors are defined in DATA/UNIVERSE/universe.ini and an appropriate DATA/UNIVERSE/multiuniverse.ini serverside AND clientside which BOTH CAN be bini-compressed !.

ShipFilter.dll has to be loaded clientside only in dacom.ini.

RandomJumps.dll MUST be loaded clientside in dacom.ini AND serverside in dacomsrv.ini. For a MP-ONLY-MOD the Randomjumps.ini in DATA/UNIVERSE Folder is strongly recommended serverside ONLY (you can alter the Jump-destinations serverside and no client-update is needed). ATTENTION: Make sure not to provide a SP-OPTION because the presence of a clientside “Randomjumps.ini” WILL CAUSE serious issues in MP ! (Sync-Probs)

ShipRange.dll CAN be loaded clientside in dacom.ini (for SP-mod-option) and MUST be loaded serverside in dacomsrv.ini. For a MP-ONLY-MOD the Shiprange.dll AND the radarmoddb.ini in DATA/EQUIPMENT Folder is NOT needed clientside (you can alter the Scanner-ranges serverside and no client-update is needed). ATTENTION: Make sure not to provide a SP-OPTION because the presence of a clientside “radarmoddb.ini” WILL CAUSE strange issues in MP !

JumpOutPt.dll CAN be loaded clientside in dacom.ini (for SP-mod-option) and MUST be loaded serverside in dacomsrv.ini. For a MP-ONLY-MOD the JumpOutPt.dll AND the JumpOutPt.ini in DATA/UNIVERSE Folder is NOT needed clientside
(you can alter the Jumpout-points serverside and no client-update is needed). ATTENTION: Make sure not to provide a SP-OPTION because the presence of a clientside “JumpOutPt.ini” WILL CAUSE serious issues in MP ! (Sync-Probs)

Greetings J.R.

[Gold_Sear]

Thanks for the info, J.R.!

[Polarts]

I know it’s an old post and all, but I remember there being a lot more DLL plugins.

If anyone happens to know which ones are missing here, it’d be lovely.
Also, a download link will be much appreciated!

[Skotty]

Adoxa hosts them here: http://adoxa.altervista.org/freelancer/plugins.html

[Polarts]

Thanks! I’ll keep that in my bookmarks
There were other plugins tho, not by adoxa. I rermember one that allowed mounting/unmounting while in space, one that allowed having zoomable sectors on the map that capture systems inside, etc…
I’m particularly looking for the first one I mentioned, but the others could come in handy as well just for the sake of listing them all.

[Skotty]

Regarding multiple system secorts: That is Multiuniverse: https://the-starport.net/modules/newbb/viewtopic.php?start=0&topic_id=5523&viewmode=flatℴ=ASC&status=&mode=0

The other I do not know about. Might be a hack or hook.

[J.R.]

The MultiUniverse-plugin works perfect on my server.
(check out the list in the first post of this topic)
But the hack… (I believe it was a “proof of concept” by Adoxa) for mounting/unmounting equipment in space has a MAJOR downside iirc… It requires a RELOAD of the character ! Thats why i droped it instantly…

P.S.: The list above contains only a few plugins and MY experiences with “how to” … regarding serverside/clientside needed files and ini-settings.

Greetings
J.R.

[Polarts]

Does the reload requirement apply to SP as well?
Either way, if you have a link to the discussion I’d be grateful

[adoxa]

Mount/dismount equipment in space. I had another look and it looks to be pretty tied into the location, so I don’t think it’s feasible.

[Polarts]

It adds up with the fact that mission triggers won’t let you change ship/loadout in space, so makes sense.
Thanks for digging into your history for me