'88 Flak's FLHook
-
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?
-
Something strange with 1.6.6 …
It does not accept password from any Server Operator in ascii or unicode.
I have checked CD, Dam, DS Process Manager and Biocross.
-
I had the same problem
- but so i m never sure, if i need to use unicode or ASCII……
… the unicode port did accept the pass and the connection from CD,
but the performance was much worse, than known from 1.6.5
(maybe cause my test server is an antique machine). -
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.
-
**Just wondering, after looking thru the docs for this, I didn’t see any mention of how the client side is supposed to be set up?
As far as I know dacomsrv.ini is only read by the server…**
-
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 listeningIf 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>
-
**Having a little trouble with the cloak part of Flak Hook…
Added FLHook.dll to [Libraries] in dacomsrv.ini, ignore the gls workaround, tried it with and without it…**
[Libraries] readfile.dll engbase.dll x86math.dll rendcomp.dll system.dll Thorn.dll DebugLib.dll rp8.dll shading.dll gls_workaround.dll FLHook.dll
New plyr ships start with cloak_nomad cloaking device, nothing changed in the weapon_equip.ini entry, it’s the stock FL cloaking device. Also, I don’t have a goods entry for it since the players aren’t allowed to mount or unmount it.
[CloakingDevice] nickname = cloak_nomad ids_name = 1 ids_info = 1 hit_pts = 1000000000 DA_archetype = Equipment\models\weapons\no_fighter_gun.cmp material_library = Equipment\models\hardware.mat HP_child = HPConnect mass = 1 volume = 2 power_usage = 0 cloakin_time = 4 cloakout_time = 4 cloakin_fx = no_cloakeffect05 cloakout_fx = no_cloakeffect05
Started server, ship is cloaked, when typing /uc it says I don’t have a cloaking device. Log into my main server which is running FLHook 1.6.0 by Wodka, it says ‘Uncloaking’ but I stay cloaked. That was just a test to see if it would at least do something. Here is the entries from Cloak.ini in the Data folder…
[CloakDevices] cloak_nomad = 30000,10000,4000 cloak_nomad_battleship = 60000,20000,8000 cloak_nomad_srtc = 30000,10000,4000 cloak_osiris = 60000,20000,8000 cloak_solurus = 90000,30000,12000 cloak_fighter = 30000,10000,4000 cloak_gunboat = 60000,20000,8000 cloak_cruiser = 60000,20000,8000 cloak_battleship = 60000,20000,8000 cloak_nomad_gunboat = 90000,30000,12000 cloak_shadows = 60000,20000,8000
Any ideas would be appreciated. I am testing this on my quad core Vista machine. I will test it later tonight on my main server which is a single core XP machine.
-
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.
-
**Thats what I needed to know, I was already using that dll in the 1.6.0 plugin version.
Appreciate it!**
-
**Still having a bit of trouble, any chance you could post a working dacom.ini and a dacomsrv.ini [Libraries] sections?
Sorry to be so much trouble ;)**
-
i’ve had the same problem with this version of FLHook since v1.6.1 (i think, might have been 1.6.2, worked fine before), no matter how many times i messed with the files. I can swap over to the plugin version works no problem
-
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.
-
Thanks alot, I will try that. I believe that is one of the ways I already had tried it though. If it doesn’t work I will see about recompiling the source files since I really want to play with player ship docking. I have quite a few cap ships in my mod that I want to add that feature for
-
M0tah wrote:
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.
Thx M0tah! It works
-
Strange thing in 1.6.7:
rehash ```works like``` restartserver
-
That is odd. I just tested it and both commands seem to do what they’re supposed to. Could you try it with 1.6.7 dev build 19? Thanks.
-
Yep! Problem fixed, thx