A lacewing modification suggestion

In addition to having Name and ID, it would make a huge difference if there was 1 or more options available to send more information on connects.

For starters, it would greatly simplify determining which object to create when the user logs on. EX: on user connects and Class =dog, create object dog, add username, add id.

EX2: on user joins send message on channel 1, on message received from channel 1 & Class =cat, create object cat, add username, add object

EX3: on user connects and class=twins, create twin1 & twin 2, etc…

I'm not sure how hard this would be to do, but the less static information that has to be sent and parsed, the better :)

We're considering this-- currently, me and Jamie are working a lot on Lacewing, so it might get implemented ;)

That would be massive! :)

I think that just having a Connect String when conenctiong to the server and a Join String when joining a channel would provide enough flexability. :)

Probably more like a string table.

else you could prefix the usernames with Dog|username or something

"else you could prefix the usernames with Dog|username or something"

started to do that. the real problem seems to be that the parser can't handle it when everyone sends a message at the same time after the user joins. (at least in flash)

Why is everyone sending a message at the same time?

Because when the person joins, everyone sends their info to that person.

What do you mean "thier info"? What exactly is being sent? Are you using On Peer Conenct -> Send? Or are you talking about something else?