Scott_NZ

Try making Arma2NET.log readonly.

What version of Arma2NET are you using?

You can redistribute the @Arma2NET folder, per the license: http://www.apache.org/licenses/LICENSE-2.0.html

The Mono .dll is only intended for Mono for Windows. It's not going to work on Linux natively (Wine might work but I can't help you with that). https://github.com/ScottNZ/Arma2NET/tree/linux has what I'm up to regarding Linux support, but it isn't quite finished. If you read over the last few pages in this thread you should find some instructions on how to get it working in some fashion.

If it all works you can try running it on an Arma 3 server. Try placing the .so in the server root folder and have an Addins subfolder with the usual things inside there.

If you want to test the current Linux code, make sure you have a recent enough version of 32-bit Mono (can try 64-bit but I doubt it will work on the Linux server later) and MonoDevelop and then do the following: 1. git clone https://github.com/ScottNZ/Arma2NET.git 2. cd Arma2NET 3. git checkout linux 4. Build Arma2Net.sln with a reasonably recent version of MonoDevelop, or edit the .sln and .csproj files with a text editor to downgrade the version if you want to use an old version. You'll have to upgrade MD or downgrade the .sln if the .sln opens in the MD text editor instead of actually opening as a sln. It'll probably partly fail (but Arma2Net.Addins should still build, which is what we're after) since I have a C++/CLI project in there which MonoDevelop isn't going to understand. 5. Copy the built Arma2Net.Addins.dll and the DateTime etc addins into the Linux directory, keeping the folder structure, so have Arma2Net.Addins.dll in there and an Addins folder, with a DateTimeAddin subfolder and DateTimeAddin.dll inside the subfolder. 6. Use 'make' in the Linux directory to build Arma2Net.so and RVExtensionTest 7. Test by using ./RVExtensionTest and then trying eg 'DateTime now' in the prompt.

I've been focusing on implementing Linux support over this, but progress has been slow without testers.

No. It's a hard limit imposed by the game itself. If you want to return results larger than what it allows you'll have to split your results up into chunks and return each chunk separately.

Do you need argument parsing as well?

There's a basic example of an async addin here. MethodAddin is on the roadmap.

Yes. You can export multiple addins from the same assembly if you need more granularity, or have a look at the source for AsyncAddinInvocationMethod and adapt it to your needs.

You can easily assign an integer identifier yourself when calling and return it later as part of a result string.

Probably something like: "Arma2Net" callExtension "Foo" where Foo is an addin that uses AsyncAddinInvocationMethod. It's invoked asynchronously, and the result is added to a queue when it's finished. You can then use "Arma2Net" callExtension "Foo getresult" to get a result at the front of the queue. It's also removed from the queue at that stage. I also recently added an option for just throwing away results instead of queueing them, and an option for clearing all the results.

It's missing a few things like the Format class (can still borrow it from the old A2N if you need it atm) but if people are happy with this I could go ahead and prepare it for a proper release. I also noticed that some people have forked A2N and made their own additions. If they want to get them pushed back upstream that would be awesome too.

Can you paste your Arma2NET logs and Arma2MySQL logs (if applicable)?