Lacewing BETA #5

http://www.aquadasoft.com/LacewingBanner.gif

This is an early one because there was a security vulnerability in the server. Also fixed a crash in the client.

Server, C++ library, extension

OINC MFA -> Lacewing patcher

Did you disable blast again in this release? It was working fine in beta #4

Edit: Perhaps not. I must have screwed up somewhere.

Quote:

---

Originally Posted by asker

Did you disable blast again in this release? It was working fine in beta #4

---

Blast (udp) is broken in this release

Ricky123 has uploaded the MFX files from beta #4 here (working with UDP).

There's a Save stack to file bug with beta #4.

People may be intrested in Lacewing/MooClick Server Controllers, which do just about all the expressions/actions/conditions in the MooClick and Lacewing objects.

http://sites.google.com/site/ricky123files/beta-projects/server-controller/

Freeware ftw

Quote:

---

Originally Posted by Ricky123

There's a Save stack to file bug with beta #4.

People may be intrested in Lacewing/MooClick Server Controllers, which do just about all the expressions/actions/conditions in the MooClick and Lacewing objects.

http://sites.google.com/site/ricky123files/beta-projects/server-controller/

Freeware ftw

---

This looks interesting. Care to elaborate what it is and its uses?

I was working on my game. It was working. After I've updated from first beta to this version, I'm not able to connect to the server, even if I host it on my computer. I've tried to use Beta #4, but it still doesn't work.

Are you using both the server and the client from this version?

If you are using a public server, which one are you using?

Quote:

---

Originally Posted by MechaBowser

This looks interesting. Care to elaborate what it is and its uses?

---

Object stressers do all the object's conditions, actions, and expressions. I've put this into a easy-find format, and included the server IPs (klikfarm/aquadasoft).

This could be used to check where your Lacewing app is mucking up... is the receiver being weird, or is the sender not sending properly?

It can be used for just about any Lacewing error troubleshooting. I use it quite a bit.

This uses beta #4, the one that has UDP.

One day UDP will return to Lacewing. Until that day I use Beta #4.

And then one day Jamie will make Lacewing work across sub applications as well... ;)