extDB beta

The beta is up for testing:
https://github.com/A3Wasteland/ArmA3_Wasteland.Altis/tree/extDB_beta

extDB pack with config and stuff:
https://github.com/A3Wasteland/Release_Files/raw/master/A3W_extDB_pack.zip

MySQL Workbench file:
https://github.com/A3Wasteland/Release_Files/raw/master/extDB/a3wasteland_db.mwb


Also included in the beta is an entity caching script that runs on headless clients, which works in a similar manner as the ZBE caching scripts, but optimized for A3W. It only caches vehicles and loot, not AI, because AIs don't actually cause that much lag on their own and they're prone to desync when cached.

The mission is currently compatible with extDB v21 and v25

Pretty nice.

There are a couple of issues with the auto-kick in the Anti-hack (for when player reconnects).

1. https://github.com/A3Wasteland/ArmA3_Wasteland.Altis/blob/extDB_beta/server/functions/fn_kickPlayerIfFlagged.sqf#L11

_x variable does not exist

2. fn_kickPlayerIfFlagged.sqf itself is created by during the server compile ... but it has a reference to "fn_getPlayerFlag" which is only created when the persistence framework is loaded.

Very cool. Will get into testing straight away.
Seeing as you call it beta, is it wise to use it on live server? Like in will the database setup change?

Seeing as you call it beta, is it wise to use it on live server? Like in will the database setup change?

Well I do need people to use it on a live server, lol. Beta means all the intended features are complete and the rest is only bug testing, so no, the database layout won't change in the short term.

Seeing as you call it beta, is it wise to use it on live server? Like in will the database setup change?

Well I do need people to use it on a live server, lol. Beta means all the intended features are complete and the rest is only bug testing, so no, the database layout won't change in the short term.

Allright, was already working on implementing all our own changes. Hopefully will run it today or tomorrow on live

Ok so running test version now. When I log out and in the player cannot be loaded:

Code: [Select]

12:47:24 Error in expression <, "BLACK", 0.01];
waitUntil {sleep 0.1; preloadCamera _pos};
}
else
{
9999 cutTe>
12:47:24   Error position: <preloadCamera _pos};
}
else
{
9999 cutTe>
12:47:24   Error Type String, expected Number
12:47:24 File mpmissions\__CUR_MP.Altis\persistence\client\players\setupPlayerDB.sqf, line 53


it wouldn't load the game stating found string, number expected.

That's not very precise.

it wouldn't load the game stating found string, number expected.

That's not very precise.

Edited my post sorry. Wasn't after editing was everytime I entered the game:
Note. This is with the vanilla version and my edited one.
Removing the player save from the database makes me able to connect again.

Code: [Select]

12:47:24 Error in expression <, "BLACK", 0.01];
waitUntil {sleep 0.1; preloadCamera _pos};
}
else
{
9999 cutTe>
12:47:24   Error position: <preloadCamera _pos};
}
else
{
9999 cutTe>
12:47:24   Error Type String, expected Number
12:47:24 File mpmissions\__CUR_MP.Altis\persistence\client\players\setupPlayerDB.sqf, line 53


Fixed, wasn't related to database: https://github.com/A3Wasteland/ArmA3_Wasteland.Altis/commit/9a67a46063b4172911d0255081742deae7c2dcaa

Fixed, wasn't related to database: https://github.com/A3Wasteland/ArmA3_Wasteland.Altis/commit/9a67a46063b4172911d0255081742deae7c2dcaa

Works now thanks!

DB_CUSTOM_V3 not been in last 2 versions of extDB is an oversight during dev work.
Notice the lack of mention of any removal in forum posts or in changelog.

The whole Abstract Protocols means i can easily have multiple versions of a Protocol.
So most Protocol Removals from extDB normally get atleast months notice, with Deprecated warnings in log-files.

-----------------

DB_CUSTOM_V3 was not meant to get removed till i get around to adding SQL RAW support added in + possible a regrex rule for creating SQL Prepared Statements (still need to work out details on that).

Also notice the latest extDB has version to check LOCK_STATUS / VERSION, while extension is locked.
Which you were asking for is in the latest build.


-----------------

DB_CUSTOM_V3 files are still present and still in the various build systems.

It was removal + re-added back in when i was writing code for DB_CUSTOM_V5. (used V3 files as a starting point). I just forgot a single include line + an else if statement.

-----------------

Next time, just make a forum post on Arma Forums Thread or better still on
Github Issue Tracker about an problem (saves me alot of time to keep track of requests / issues)

Thanks

DB_CUSTOM_V3 was not meant to get removed

I thought it was intentional, hence why I didn't say anything.

DB_CUSTOM_V3 files are still present and still in the various build systems.

v24 release DLL still doesn't contain V3, thought.

Running on live now with own added stuff. Will see what happens performance wise. Also added the headlessclient.

Bankmoney isn't saved but both lines are uncommented (as your have in the vanilla). What could go wrong?

In applyPlayerInfo.sqf there is a TRUE added in 1.0C

Code: [Select]

case "BankMoney": { player setVariable ["bmoney", _value max 0, true] };

I removed it for test as this isn't in pre 1.0c versions for test. Still no go...
Player bankmoney save isn't instant to the database?