philippj

OmegaSC version v0.45 offers further improvements to the recovery system and additional RPT parsing Omega now is DayZ 1.0 compatible

The server under the official tab are the official servers "maintained" by BI. It's not possible for a community server to appear on that list. Currently only GSPs have the option to host public shard servers which will possibly not change.

Even though the chat appears to be global via RCon the messages are not global. Only the one logged-in admin can send into the actual global chat.

May I? https://git-scm.com/

That is wrong. BEC (BattlEye Extended Controls) is a software that utilizes the BattlEye Server RCon protocol to achieve certain things. The issue is most likely client side eg. Firewall/Routing or general connectivity issues. Antivirus software also be something to look at.

You really want to use a freaking outdated piece of software? I got my own, intelligent backup/recovery solution for the current issues with the gameserver. SQLite is used for the player database only. The persistence is stored in bin files. Also "billions" of devices use SQLite for miniscule amount of data but no enterprise software uses SQLite as actual data backend for a large infrastructure. Please do proper research on the topic before starting a revolt. There is no issue whatsoever with the gameserver using SQLite.

The hive is not out yet for the general public. Only legacy GSPs and BI has it. Currently the players are saved in a SQLite database. Persistence in binary files in whatever format. If an application actually crashes - not stopping and not in a graceful way - files which are opened, may get corrupted and there is no shutdown procedure either. Such a crash should never happen and can be circumvented with various methods. Fact is the DayZ server crashes and sometimes data gets corrupted.

You are running BEC and didn't disable the global chat restriction. With that shit enabled you get kicked for writing in the global chat and since the game currently has no other chat channels then global, everyone gets kicked when sending chat messages.

Are there plans to move the persistence to an actual database?

Use the GitHub version. It is possible to target players with spaces in their names for quite some time now.

OmegaSC version 0.32 has been release including a lot of updates including and a persistence recovery mode. Omega has been enhanced with various features including hived whitelisting.

None that i know of

Thhe executing player is searched by a simple name check. Set your in-game name via launch parameters to something that is not survivor and you are good to go

You can access the inventory of the spawned object with GetInventory() and create items in it with GetInventory().CreateInInventory()

Are you talking about the target player or the executing player not being recognized correctly? When targeting a specific player you have to include his survivor index, if the target has not set his name via startup parameters. eg. /kill Survivor (1)