Should be fixed on current dev-branch, if not then next. Its fixed internally

it's floor, not floot

pastebin example to make it work https://pastebin.com/kDxdaSHP

If the tickets do not already exist, feel free yes! Thanks for your eyes o7

Thanks for getting back! Im sorry if i was impatient ^^ Ill wait longer.
I have found a lot more similar problems, should i create a related task for all of them?

In T183037#2642395, @dedmen wrote:

Maybe we can just detect and only save on exit, if the file is already there.

toJSON/fromJSON are in 2.18

We do not want to spam empty/unused namespace files on every game shutdown. That's why it only saves if you manually save.
Though. It would expect that after the first manual save, we consider it "enabled" and also save on shutdown. Because the file is already there anyways, so we wouldn't spam unused files in that case.
Maybe we can just detect and only save on exit, if the file is already there.

I fixed it now.
You can either remoteExec it, or change some other state of the vehicle to force it to update.

That explains the variability in sync time then... Any chance it can get it like animateSource does, or suggestions to force a sync? (I guess remoteExecing it)

The answer is simple.
There is no door state synchronization :D
It is sent when other things are synchronized, but for the door state itself, there is no check if it needs sync. So changing it doesn't trigger a sync

It looks like a bug in the code thats correct but intentionally left out from autosaving so that it only saves when you request it. It autoloads when exists though. It has been explained on wiki

Hi, no worries about asking :) it may take a bit of time reviewing/sorting the ticket, as sometimes lots of reports have to be processed - there is also the fact that this is Summer time and holidays may slow down things. Worry not, thou art not ignored/forgotten!

Are some requests beinh ignored, or does it simply take some time until a dev can take a look? (Sorry, first time here)

In T183037#2641505, @BIS_fnc_KK wrote:

It does not save by itself, you need to run saveMissionProfileNamespace https://community.bistudio.com/wiki/saveMissionProfileNamespace

It does not save by itself, you need to run saveMissionProfileNamespace https://community.bistudio.com/wiki/saveMissionProfileNamespace

Is it alot of work to make the setObjectTextureGlobal command also work with vests, headgear and weapons missionside?

Thanks, should be fixed with next data update

This seems to be related to the magazine being deleted when fired - if the magazine is modified to be deleteIfEmpty = 0; the effect plays