Request

[old ice]

As a programmer from another realm this would concern me immediately as to what information is being tracked and managed. It'd invite actual legal conversations because of who and where plays the game but beyond that..

In 2016 I wrote a MongoDB Java patch to the game and also a MySQL/MariaDB server patch later on.

I think this circles a larger issue with server-side file controls.

I can see TIS asking legal questions here but honestly servers should be more relaxed on I/O utility. It's the clients where I can see this stuff not being accessible and they have no reason to.

Having general JDBC access to API maybe with wrapper Java classes would seriously help with advanced server modding.

[slate dome]

Yeah that makes sense. I'd be curious to know of an example of what information you'd be worried about though. I'm not sure what's stored in the player.db file or any others. Most of my work has been done around creating new tables and exposing them to lua.

The main reason I’m pushing for something like this is it would let me build systems very similar to how FiveM works... Persistent player data, server-driven features, and external-backed systems, but directly within PZ instead of relying on fully custom bridges.

Having some kind of official/controlled access layer would make that a lot cleaner and safer to build on, but I digress.

[old ice]

Steam-specific info but I don't think that PZ has any real sensitive information. I'm thinking more about generic services laws and what they can store for kids.

Stuff like that is where I went with that take.

EU / US / etc.

[slate dome]

I see

yeah cause honestly the only real thing I would need to build from is player or steam id.. past that every system i've dreamt up kinda just works

[old ice]

I originally added fuller DB support for things like cached translations from using Google Translate API and proto-factions data before the game officially supported them.

[slate dome]

aye thats quite nifty

[old ice]

I'd back a fully-realized API for DB.

I might also do this for my community API patch. Would love to see what TIS team is thinking on this feature.

Thanks for bringing it up and good luck on your project.

[slate dome]

If you get far down the line on your community API patch please let me know

I don't know if it's worth double building access to the local DBs but

like I said I've already written a simple bridge for this concept but.. More than happy to share my progress if I do any updates in the future

[old ice]

I'm not allowed to advertise it through here but I can DM you.

[slate dome]

Looks like I gotta brush up on the rules lol. But of course, DMs are always open

[little timber]

We must consider that exposing a public Java API to Lua allows for potential misuse by modders