What are the differences between the three lacewing extensions?

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    Alright I used to be decently knowledgeable about lacewing (back when there was only one extension). I haven't coded with lacewing in awhile and finally decided to download the latest build which is #20. I've noticed that there are three lacewing extensions; The "Lacewing Relay Client" (which i assume was the old lacewing extension that I was using before), "Lacewing Relay Server", and "Lacewing Webserver". Could somebody tell me the differences between all three? With the lacewing relay server, would it allow me to create my own server exe client and control it? And what about the webserver extension, could it host an http webserver? More insight on this would be grateful, thanks.

    Custom A* Pathfinding in MMF2: Please login to see this link.
    Random Tile World Generation: Please login to see this link.

    There's actually four now, but that extra one's just a deriative.

    The change to #20 involved Lacewing's code being moved from "Communication using Lacewing protocol" to "Communication". "Relay" is the assigned name for that protocol, the one supporting subchannels, client names, peer IDs, etc.

    So now:

    • Lacewing Relay Client is the client for the Relay protocol.
    • Lacewing Relay Server is the server for the Relay protocol.
    • Lacewing Webserver (note lack of Relay) is a HTTP protocol server. If read the same way, it would be Lacewing Web Server. Web of course is used mainly with HTTP.
    • There's also Bluewing, which is essentially an unofficial port of Lacewing Relay Client remade to be stricter with how you handle it. It can do all of what Lacewing Relay Client does in the same layout of a/c/e, but with a few added features.

    That's a kinda scattered response, but it should answer your question.

    Darkwire Software Lead Programmer (C++ & C#)
    Please login to see this link. | Please login to see this link. | Please login to see this link. | Please login to see this link.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login