The healthbar image is just a simple 256x8px gradient image which is warped by the game to imitate a flame effect.

I've attached a template pack to create your own health bars. Load "template/gradient template without palette.bmp" in Photoshop and draw something on the gradient. Then use Image -> Mode -> Indexed Colors. In the "palette" combo box select "Custom..." palette, then click "Load" and specify "template/photoshop palette gfx0.act". Then click "OK" and play around with dithering (None/Pattern/Diffusion/Noise) method and levels. Then save the image as "fire-whatever-gfx0.img.bmp". Repeat this step with gfx1.act for colorblind palette.

Next, put your "fire-whatever-gfx0.img.bmp" and "fire-whatever-gfx1.img.bmp" next to "healthbars.dir.txt". Open "healthbars.dir.txt" in notepad, add those two files to the list and save the file.
Launch "SpriteEditor.exe", then click "Reconstruct from log" button and specify "healthbars.dir.txt" file.  The files will be converted to IMG format. Simply copy the img files to your WA/healthbars/ directory and edit wkFlamingHealthBars.ini file to use the new images.

Important note: Do not use gfx0 (normal colors) and gfx1 (colorblind colors) images at the same time. If you do so, you will reach the palette colors limit and the images will turn white.

...I've tested it more and it doesn't print all lines from the text files. In my files the 1st line is empty, so I assume it shows 3 first lines of each file (the picture attached)

This is an intentional limitation of the module to minimize the risk of being automatically muted by other players, as WA has built-in anti-flood mechanism. If you send multiple in-game chat messages in short time period, you will be automatically muted without any warning and your chat messages will be ignored by other players until the round ends or other players use /unignore command.

Try this:
a) disable the module and replace one of existing themes (for example: tentacle) with your terrain.
b) enable the module, but run it with only Win95 theme enabled

I've quickly tested your theme - it works fine with replays on my machine (and looks quite good).
Please attach a sample replay and output of /terrains command in lobby so I can match the exact same setup as you.

For reference, here is what it shows on my machine:
terion is using wkTerrain38_v2: Candy  Dinos  Domestic  Tetris  Win95
and I've attached a sample replay

Here is a static build of wkTerrain38_v2 - use it if you experience WormKit error 7E

I am truly sorry for causing  trouble to you and the entire worms community.

Shoddy workmanship and then refusing to accept responsibility for the problem is.

I agree that my works are on the lower end of code quality spectrum and my wording could've been better. Though I think that through discussion in this thread issues with the module were corrected and the most recent release of the module seems to work properly.
In my previous posts I have identified numerous problems with the module and wormkit ecosystem in general and in the following post I've released a corrected version that fixed problems on my end. While still a shoddy workmanship, I wouldn't call it refusing responsibility.
My works are and will remain open source, so if anyone wants to improve them, anyone is free to do so and I would love to see an active open source worms community in near future.

Yes. So, please try to not release software which causes confusing error messages.

Clearly, I'm no expert on windows api but I think that LoadLibraryA triggers this error before my module runs a single code instruction, so there is not much that I can do from technical standpoint. I should've stated in OP that this module requires MSVC runtimes, but some users would ignore it regardless (just like GrO did a few posts back when I instructed him to install runtimes).

Though from technical standpoint your works are excellent and take into consideration every possibility (I didn't even think of the case with loading exports from WA.exe), I think that they need to be adjusted for real world cases, such as this thread and make some assumptions to make it more clear to end users.

You may observe a non-negligible performance gain by avoiding the WinAPI overhead.

I am well aware of that and I've already changed that code before your posts when feedback about issues reached me.

- in my opinion this functionality should come standard with base game to avoid shitty kick module implementations like this.

And I still support this opinion. WormKit modules are inherently low quality hacks and need to reinvent the wheel to provide basic functionality, which can be properly implemented within matter of minutes in the base game. If there was a proper API to deal with the game's memory or proper open source examples, things could've been a bit better.
I know that your WormKit modules are available on github, but they work on hooking Windows API level or the most important parts of them are closed source, thus entire module's code is useless for other developers.

When map data is sent to players, the terrain texture is specified as an id number in the terrain list instead of a terrain name. This makes it quite difficult to synchronize the terrain when players have mismatched lists - for example terrain #30 for one player might be "Dinos" and for other player "Candy".

Some ideas:
a) Negotiate a common subset of terrains that everyone has installed - I can force the game to print the list of installed terrains when joining the lobby. The host would automatically read those lists and keep track of all terrains installed by all players and find a common subset, then send a common terrain list to all players who will temporarily disable specific terrains. This approach would require the least amount of hacking, but will not work with replays and might introduce problems in some edge cases.

b) Hook the protocol, so a text name of the terrain is sent before map data. If the terrain id in map data is bigger than standard terrain ids, the terrain name will be fetched from the text name instead of terrain list. Lots of hacking involved, still won't work with replays.

c) Change the protocol message to use a text name instead of ids - even more hacking, will break compatibility with all other WA versions and people without wkterrain.

d) Ask game maintainers to make this feature a standard part of the game.