'88 Flak's FLHook

I’m glad to announce the final release of 1.6.5! Sorry it took so long :).
If you are using the death penalty feature, I strongly recommend upgrading to this version, as it fixes a pretty bad exploit related to the DP.
Download: 7z, zip

Full changelog:

• Fixed getting account dir failing on some computers (http://the-starport.net/f/index.php?topic=853.0)
• Added ship repairing based on type of ship or presence of mounted item (see [ItemRepair] and [ShipRepair] in ini)
• Added blowfish encryption option for the socket connection
• Fixed addcargo kicking upon launch when adding items not sold at base (bug introduced in 1.6.1 when addcargo was partially rewritten)
• Added new admin command addcargom that adds mounted cargo
• Added list of items to automatically mount upon ship purchase (see [AutoMount] in ini)
• Fixed docking restrictions cargo being removed when player canceled dock
• Fixed cash being deducted when attempt to buy item was blocked ([ItemRestrictions] in ini)
• Added list of items that cannot exist in space (see [NoSpaceItems] in ini)
• Added list of items that are automatically marked when they spawn (see [AutoMarkItems] in ini)
• Added setting to drop the shields of a ship when starting to warm up the cloak
• Changed autobuy to run when player launches to space (so player can sell loot before autobuy tries to buy items)
• Fixed DP not being charged if player launches in a system on the no DP list and then dies in a system not on the list
• Fixed DP not being charged if player turns off the DP notices (bug introduced in 1.6.3)
• Fixed players being able to remark a ship once it has started to cloak
• Fixed a mobile docking bug where players would follow the carrier’s jumps if the carrier died and the players had not launched

Alright, I’ve taken a look and it seems I forgot to re-implement the event in the rewritten death message code. However, due to the fact that the new death messages focus on providing more than one reason for deaths and more detailed death by NPC messages, the standard death message event format doesn’t make sense for the new code. So I was wondering if I could get some feedback from those who might use the socket events on what they’d like it to look like.

I would likely put in at a minimum the “victim” and “by” fields. While the “victim” field would be the same, the “by” field might have a list of factions/players like the new death messages. I also might add a new field called “causes” that lists the weapons that were used by the factions/players like in the death messages. Thoughts or suggestions on how it could be made differently?

Ooops, I forgot to change the socket connection password read file - it was trying to find them in the main config file instead of the general one. The latest 1.6.7 dev build fixes it.

Also, I would not recommend using 1.6.6, since it has a nasty bug that can cause the server to randomly crash. Said bug should be fixed in the above dev build, however.

It’s completely server-side, no client-side setup needed.

There was a bug in the previous dev build that caused players to be kicked on character selection for cheating; download dev build 12 for the fix.

@khayman: If the socket has been activated then you should see messages in FLHook’s console indicating that FLHook is ready to recieve connections -

socket(ascii): socket connection listening
socket(unicode): socket connection listening
socket(encrypted-ascii): socket connection listening
socket(encrypted-unicode): socket connection listening

If not then FLHook isn’t reading your socket connection settings. Otherwise you can test that the connection actually works using the telnet utility. Open the run dialog (on the start menu in XP, use the search field in Vista and 7) and enter```
telnet localhost

> Welcome to FLHack, please authenticate</port>

For the cloak feature you do actually need a client-side DLL, sorry about that. I can’t seem to find w0dk4’s original mod, but you can get the DLL in the plugin version’s cloak plugin.

Actually I realize now that this actually isn’t documented in the readme either, I’ll go update that as well.

Sure.

dacom.ini:

[Libraries]
;;;dosfile.dll
ReadFile.dll	;optimized read-only version of dosfile.dll
x86math.dll
EngBase.dll
system.dll
RP8.dll
SoundStreamer.dll
SoundManager.dll
Deformable2.dll
Thorn.dll
Shading.dll
RendComp.dll
alchemy.dll
ximage.dll
.\flmaterials.dll
;;;ClientHookTest.dll ;88 Flak Client Hook Test
cloak.dll ;Cloaking
MultiIntro.dll ;Multiple Intros
DelayDisplay.dll ;Cooldown Display
MultiCruise.dll ;Multiple Cruise Speeds
8waystrafe.dll ;Adoxa's 8-Way Strafe
;;;SwitchSys.dll ;Instant System Switch (for Mobile Docking)
;libcurl.dll ;GLS Workaround
;gls_workaround.dll ;GLS Workaround

dacomsrv.ini:

[Libraries]
readfile.dll
engbase.dll
x86math.dll
rendcomp.dll
system.dll
Thorn.dll
DebugLib.dll
rp8.dll
shading.dll
FLHook.dll ;FLHook (required by 88 Flak)
MultiCruise.dll ;Multiple Cruise Speeds (required by 88 Flak)

Both are taken from 88 Flak - feel free to download the entire mod if you need an example of a working config.