sortacore / mmf2exts Goto Github PK

For example this works;

While this does not;

This was opensourced very very long ago. I think I have an old version saved on my laptop, but there may be a newer version available. Perhaps we can get in contact with Dynasoft and have him host it on GitHub.

For some reason, there's resource compiler error:
RC : fatal error RC1109: error creating .\Release/
I've been through the resource file's code, searched all the files in the project, and checked the project configuration - no mention of Release folder anywhere, just Release_Small. And I did that four times.

https://github.com/jaquadro/XLua
Will fix in reorganize when I get home.

Kind of nice to see an old fellow extension developer. I brushed into him with NBTExplorer and didn't realize it was him until I found his XLua repo.

@clickteam-plugin is the MMF2 extension hub, eventually this repo should be transferred to @clickteam-plugin.

This issue may be in the client as well.
At some point during server hosting – can be as quick as twenty minutes, or as late as days later – the server's UDP will stop transmitting the UDP part of the connect handshake (namely responding to UDPHello with UDPWelcome).
Since on Lacewing Relay clients, the UDPWelcome message is what triggers On Connect, this is a significant problem. And since UDP allows packets to be dropped, the client just keeps resending UDPHello, not erroring.

Current clients on the server are unaffected; they stay connected.
New clients, even without UDP confirmed, can still communicate over TCP, as the servers will accept TCP messages (assuming On Connect Request is OK'd) even if UDP has not been confirmed yet. So a client could set name and so forth before it receives On Connect - but naturally they will be unable to use UDP for receiving or sending until the handshake is finished.

This issue (or a similar one) is present in pylacewing as well. The client either gets Connection Denied, or UDPWelcome is never sent.

So far the only workaround is to have a client connecting to the server every so often. If after a certain number of seconds no On Connect is made, then the server needs rebooting. I've set up both Darkwire servers to be checked every ten minutes.

It might be caused by a client disconnecting, but it's hard to tell, because it appears to be a race or low-probability condition of some kind, which tend not to manifest when logging is added.

Some extensions are out of date with the latest versions of their respective SDKs/libraries or do not compile under all or most of VC++2008, VC++2010, VC++2012, and clang.

The windows SDK is very behind the times - in fact so behind that it uses the stdafx precompiled header.

(In bitset)
I've recently gotten this message and even after reinstalling this repo, I still get the same error. This is on line 275 and occurs for Android. I have built extensions before and only recently this has been appearing.

After that's done other bugs may be considered. Unfortunately, liblacewing has discontinued Relay.

On Connect will only trigger once on connect, and any later connections will not be noted.
This is due to On Connect only happening when a UDP connection is finalised, after TCP. TCP notes its own connection fine, but UDP for some reason never properly acknowledges subsequent connections, causing On Connect to only work the first time.

Hi. how we can use combo box in properties?
is there any sample?

Many extensions are hosted directly in this repository. Since the original authors cannot host them, they should be hosted by the @clickteam-plugin organization.

I'm working on this in the reorganize branch.

Due to comments in the JSON being disallowed in later versions of EDIF, the following extensions are no longer functional in the EDIF SDK:

• DarkSocket
• MyCharSet
• PortAudio
• RangeHandler
• SHA-1
• StringReplacer

However DarkEDIF supports comments, so the extensions should be converted to that.

All edittime settings work fine bar this one. If the text is retrieved, it is a Uni/ANSI mess generally.
However, adding tabs via actions works fine, so there is a workaround.

Already added, this is just a marker.