torndeco

Object positions for terrain builder is different to object positions ingame :(

Sorry cleaned up my dropbox yesterday. Reuploaded + new link https://www.dropbox.com/s/22lnppb7pbc1pyc/Chern_Fixed.7z?dl=0

Resizing the map envolves more work. Basically it means checking the terrain cells don't go over 6 materials per cell. And making adjustments to the satellite image / mask if it does I want to avoid this, unless there is decent larger terrain to add. Funny thing is the Utes object positions aren't altered all. They are exported straight from Utes + imported to Chernarus. It basically looks like someone at BIS was looking at putting Utes into that location at some point. Thanks for info about the barracks will look at them tomorrow.

Just a minor update Berezino: 2 Shipping Containers behind shop rotated, so open doors aren't glitching through a wall. Fixed floating Land_A_Office01 Few other small fixes

I will look at connecting the islands, makes more sense but no promises. My main issue is getting talented enough to alter the Satellite Image :) Note: It is possible to drive over atm in a hatchback / hunter etc I will take a look at the height of the UUS Khe Sanh, am pushing update later today sometime with some fixes. Not 100% sure if i will leave it in or just remove it. That way people can add it via missions if needed etc

You should look at altis life github and look at there changes. It is currently using extDB3 Goodluck

There is very little difference between SQL_RAW_V2 + SQL. Its is just slightly different setup stage For example 9:ADD_DATABASE:<DATABASE>:<DATABASE_NAME> 9:ADD_DATABASE_PROTOCOL:<DATABASE_NAME>:SQL:SQL:TEXT 0:TEST:SELECT * FROM PLAYERS Atm i don't have any SQF code like EXTDB2_fnc_init written. Look at the examples at https://bitbucket.org/torndeco/extdb3/src/96421b87ca61f8075daa57f6c8c64389318e788e/sqf_examples/sqf/?at=default Also if you get stuck you could look at altis life rpg they switched from extDB2 SQL_RAW_V2 -> extDB3 SQL

https://bitbucket.org/torndeco/extdb3/wiki/extDB3 - SQL

There is a bug with callExtension on arma3server for linux with 1.68. [10:53 PM] Torndeco: Ok workaround is to rename extensions , it isn't nice but ohwell [10:54 PM] Torndeco: For example /home/user/arma3/extension.so -> /home/user/arma3\extension.so (dont forget to escape the backslash) [10:55 PM] Torndeco: Depending on extensions you will may need to relocate config files etc Hopefully BIS will release a fix soon

Just linked you to sqf post with example code sqf. Its up to you change the setup stage. Like i said its very similar. If you get stuck look at altis life repo for changes etc Goodluck

Nope you can stil do raw SQL Querys if you like. Example how to do it, its almost the same. https://bitbucket.org/torndeco/extdb3/wiki/Contents Note: If it is a life server, its is prob worth looking at https://github.com/AsYetUntitled/Framework aswell

I am sorry i only support extDB3. Not to mention there are outstanding bugs in extDB that can crash a server and some performance bugs with extDB2. It is relatively easy enough to port extDB SQL Protocol to extDB3, which is what the life servers were using. If you are unable to update your mission or addon, am afraid you will need to use the 32bit server. Players can still connect to the server using 64bit clients

@guzzenvonlidl Arma extensions really don't have limit on input. Its only the returned string back to arma which has a limit, arma 3 last i checked was 10k. Sounds like you are using _msg = format which has an 8k limit on it. Use joinString or str commands instead

Version 1.027 https://bitbucket.org/torndeco/extdb3/downloads Fixed issue were some systems locale number formatting uses different char instead of . for floats / decimal numbers etc This basically means if you had for example German locale on the system for number formatting it was returning [1,[1,0]] Instead of [1,[1.0]] Changelog Fixed 9:LOCAL_TIME + 9:UTC_TIME offset not working i.e 9:LOCAL_TIME:-2 etc Fixed some systems locale number formating using , instead of . for floats.

The main thing with extDB3 that confuses people is there is a setup stage. This is to make it flexible, but is also confusing aswell. "extDB3" callExtension "9:ADD_DATABASE:DB"; // This will connect to a database using the settings from [DB] in extdb3-conf.ini // Next there are two different methods of sending queries etc // There is normal SQL Queries, (not secure if someone manages to remote execute code on armaserver) // Or there is prepared statements etc that are predefined in .ini file. // So we have database setup, we just need to tell the extension which method we are using. "extDB3" callExtension "9:ADD_DATABASE_PROTOCOL:DB:SQL:SQL_QUERY"; // This will use database connection DB + the method/protocol SQL, and we are calling it SQL_QUERY. "extDB3" callExtension "9:LOCK"; // Then we are going to lock the extension. This is security incase someone remote executes code on server. // It basically disables the setup stage. //"extDB3" callExtension "9:LOCK:1234"; //"extDB3" callExtension "9:UNLOCK:1234"; //"extDB3" callExtension "9:RESET"; // Note if you use a password, then you can unlock + reset the extension later. // Useful for testing or restarting / loading different missions. Ok the extension is finally setup and we can actually do a SQL Query (SYNC / BLOCKING) _result = "extDB3" callExtension "0:SQL_QUERY:SELECT * FROM PLAYERS"; _result = call compile _result; Note: SQL_QUERY / DB names above can pretty much be whatever you like. Some frameworks even randomize this. It is also possible to connect to multiple databases at same time aswell. Also all the error messages return to arma from the extension are generic. To get proper info you need to check @extDB3/logs for more detailed info I also updated / simplified the sqf examples at https://bitbucket.org/torndeco/extdb3/src/08a15a65b9e5b7a0807fb31166434962ce2daddd/sqf_examples/sqf/?at=default ----------------------------------- Above is just some rough examples to get you started etc... There is also a test program in the optional directory. It is basically a commandline version of the extension. It is so you can type in the commands and see the returned output, without having to use arma. Makes it easier to understand intially imo, versus typing sqf code etc... After you get that part figured out. You should have a mess around with retreiving multiple part messages ExileServer code / AltisLife / a3wasteland and afew other frameworks will have this implemented. And look at https://bitbucket.org/torndeco/extdb3/wiki/extDB3 - General --------------------------------- Few other things you might not know or be like why. Few things arma callExtensions are blocking... That is why its generally better to tell an extension todo something. It returns an id + you poll the id until the job is done. This is normally what people refer to async extension. This way you don't block arma engine for long period of time. Arma callExtensions can only return so much (2k chars in arma2, or 10k chars in arma3). That is why there is multi-part messages, to handle when your returned output is longer than the limit.

Version 1.026 https://bitbucket.org/torndeco/extdb3/downloads Recommended update if you are using SQL_CUSTOM i.e modified ExileServers / a3wasteland. Changelog mariaDB C Connector updated + memory alloc bug fix. Added 9:getUPTime2, instead of returning <number> it returns [<number>]. This is faster with upcoming parseSimpleArray

It will help to have some knowledge of SQL Queries & SQF. Otherwise it will get confusing fairly fast. In that case i would nearly recommend (just no update for upcoming 64bit, but the source code is there) But i don't think he is been active in awhile :( ------------------- If you do know some SQL etc or think you be able to learn it... Just note @extDB3, does not implement code to talk / retreive data from the extension. This is due to several ways to implement this. extDB3 is very similar to extDB2, i tend to the number in the name if there is a breaking change. So the best thing is to look at other addons/missions that have implemented it Then if you got questions try give me a shout on arma discord (might take awhile to respond, but you will need to know some SQF/SQL) ------------------- A3Wasteland uses a mixture of defining defining SQL in .ini file & generating the rest of query in SQF. (don't recommend, is very confusing & abit more complicated queries) Exile has a good implementation, uses pretty much all prepared statements. (secure) AltisLifeRPG uses SQL Querys, but is prob alot easier when starting off. (not secure) There is also Note: There is a test command line program, that lets you test sending the extDB3 text. Can be abit easier to use initially as you don't need to be in arma.

It is very unlikely i will add SQLite at this time. To my knowledge there was never a public mission or addon that used SQLite for a backend with previous extDB/2

No i will not using the new alternative syntax, will actually be avoiding it. Its to limited (i was originally hoping for a better data structure sent to the extension). But basically the return syntax is completely different for the alternative syntax. Which means you need to document 2 different methods of sending / receiving data to the extension. There is no real advantage (possible slower due to extra memory allocs in blocking thread) and it will just result in more confusion. Anyway the seperator issue is solved by issuing SQL_CUSTOM + Input SQF Parser = true It should work fine, if there is any issue just submit issue on bitbucket.

Version 1.025 https://bitbucket.org/torndeco/extdb3/downloads Just some bug fixes and extensions should now be whitelisted by BattlEye Changelog SQL_CUSTOM: Fixed $CUSTOM_X$ SQL_CUSTOM: Fixed Support for MySQL Decimal Types Linux: Fixed Test Program Builds

Version 1.024 https://bitbucket.org/torndeco/extdb3/downloads 32bit & 64bit dlls are now packaged together. Please note that you will need to copy the tbbmalloc.dll & tbbmalloc_x64.dll to your arma3 root directory. Dlls should hopefully be whitelisted soon aswell. Changelog Updated: MariaDB C Connector Updated: Boost Updated: TBBMalloc Added: Windows 64bit dlls Added: SQL_CUSTOM SQF Parser Option (expermential) read below Input SQF Parser = false ;; Expermential ;; If enabled will use SQF Array Parser instead of : seperator for values ;; i.e 0:SQL:UpdatePlayer:["Joe",[1,2,0],0.22333,"PlayerBackpack",-3] ;; Advantage is that you don't need to strip : seperator from user inputted values

There are some expermential dlls uploaded to bitbucket at https://bitbucket.org/torndeco/extdb3/downloads This is just a debug 64bit dll version of extDB3 These are just for testing not meant for a live server. The tbbmalloc_x64.dll goes in arma3 root directory. The extDB3_x64.dll goes in your @extDB3 etc ------------- I need todo some testing, but i have encountered a segfault on a custom server. Looks like its just a bug in arma, but i just going to test something tomorrow, just to be sure. I will do proper builds & sign them once i am sure its not the extension causing it.

There will be expermential update tomorrow for people to test with the arma RC Build for 64bit I would like to use the latest Boost Library update & currently there mirror for prebuilt binary for windows is currently having issues.

Ahh crap i uploaded the wrong file :P Uploaded a new version now.

Written text to say monetization is allowed will have no real effect. People are required to ask permission beforehand atm. You have to remember BIS has setup the current system to require as little work as possible on there side. Mainly because they aren't making any money of the current system to pay for hours. Also increasing the workload means less money to spend on game development. Also people will always be people that say screw it and ignore the rules regardless. Atm its up to addon authors to decide if people want to montize. I am actually surprised no-one has made a tool to report all monetized approved servers running X client addons. ----------------------------------- Personally i think addon makers should be allowed to monitze via steam workshop if they like to. Valve / BIS / Uploader all takes a cut Person that uploads doesn't receive any money for the first months. This is done incase the money has ripped / stolen content it can be refunded. Money towards BIS can go towards Server Monitization & Addon Approval to get monitzed (if required).