Darkwire Software
Home       Products       News       Contact us

Lacewing Relay Server List

The following server list is brought to you by Darkwire Software.
These server statuses are refreshed every time you load this page.

6th September 2017: Bluewing Server b9
and Bluewing Client b76 released!
Also see LB's LacewingHelp PDF now in downloads below. Explains Lacewing, including binary messages.


Server Name/Version Server Address Status
Darkwire Server I (Windows - SWF support) server1.dark-wire.com:6121
Darkwire Server II (pylacewing) server2.dark-wire.com:6122
Costa VPS (Windows - SWF support) costa.servegame.com:6121
Shadow Soft shadsoft.no-ip.org:6121
LB-Stuff Server lacewing.maycontaincode.com:6121
VillyNet Server villy.net:6121
leDev Server ledev.org:6121
leDev pylacewing Server ledev.org:6122
Klikfarm Server server.klikfarm.com:6121


Any server that supports Windows clients implicitly supports Android clients - they connect the same way. All servers above support Windows, Android, and Flash clients.
For the plain-text list of servers, suitable for use with the Get object, please see here.
To view your own IP, use this link.

This list was last refreshed at (whenever you opened this page).

Downloads and source code

The Lacewing extensions themselves can be downloaded here (Relay), and here (Blue Client), and here (Blue Server).

The liblacewing project is open-source; more details can be found here.
Bluewing is open-source too, as part of Darkwire's extension repository, and can be found here.

Also note there is a Python implementation (of the server only), capable of being run on Unix-based systems, including Linux and Debian. Details and a setup tutorial are available here.
If you have problems with a *nix setup, try contacting users Phi or Mathias on Discord.

Also, there is a tutorial for using Lacewing Relay Client in MMF2/CTF2.5! For a small Lacewing chat, download here. For a detailed Lacewing breakdown from LB, download LacewingHelp.pdf. Includes binary message tutorial.

As always, if you need support, contact Phi on Clickteam Discord.

What's the story behind liblacewing, Lacewing Relay, and Bluewing?

Whilst working using the Moo branch, a developer (James McLaughlin) got a bit miffed with the bugs and glitches from the discontinued extensions, and wrote a new networking extension to replace the Moo branch (MooClick, MooSock, MooGame, etc). He called this extension OINC (OINC Internet/Network Client); carrying on the farmyard animal sounds convention (moo, oinc).

Then unfortunately, he had a hard drive crash, and lost most of his source code.
Having essentially to redo all of his work, he renamed the new extension Lacewing.

After working further, he decided to make Lacewing an extension compatible with not just games, but any other protocol type. To do this, he separated Lacewing extension into two projects:
• Lacewing Relay (the protocol from the extension, much like MooClick/MooGame)
• liblacewing (any protocol, much like MooSock)

At some point, a developer called Mathias (aka Mat^2 or Mat²) created a Python implementation of the Lacewing Relay Server. He named this pylacewing.

Lacewing Relay relied on liblacewing to work. However, work on Lacewing Relay was halted, but work on liblacewing continued. After several bugfixes and changes to liblacewing, Jamie became too busy to reimplement the newer liblacewing into Relay and update the Fusion extension.

Thus, Bluewing Client was born, after another developer (Phi) became rather irritated with the bugs in the not-so-recent Lacewing Relay Client and decided to rewrite the extension from scratch; a process he completed in two days, as it was just wrapping around the liblacewing code again.

What is Bluewing?

Bluewing (aka Lacewing Blue) is a continuation of Lacewing Relay, with optional multi-threading, stricter usage, and a few extra features that the regular Lacewing Relay doesn't have.
In addition, Bluewing has less bugs, and uses a newer version of liblacewing.