Details
- Panel Type
- Query Panel
- Editable By
- maradiliko (zhen maradiliko)
- Appears On
- maradiliko's Dashboard
same issue here, it's something on their end.
Crash at game end. Known but we don't know what causes it.
Same, I guess it's disabled or something :l
Short Update:
f0ca726a-1363-4a96-a511-2442d2f42531 This is my Vigor ID if this can assist at all.
Same here. I also can't access anything in the menu except for the Map and Customization
It happened also to me. I played 4 encounters but the progreess was not saving either. Also says that the server is not available after the encounter.
I have same issue.
Also can you please explain what does the following mean?
Hello R8DY2FLY.
Can you please describe the issues in greater detail?
The server crashes, I would like to ask you to please look at what this could be connected with, at least find indirect evidence)
Hello Smola.
Can you please properly describe what is the problem you are experiencing?
Regards,
Geez
Hello GlutenFreeVapes.
Currently there is no information I can share on this topic.
Regards,
Geez
Hello, @Geez would love to know if this is something that is planned or simply not in the scope for arma reforger.
Update: This seems to extend beyond just the Mi-8 and also some issues with turrets spawned with roadblocks, and the huey's guns too. The AI gets stuck on it just as players do.
For the record, getting in and out of the gunner seat (without anything else, and assuming bug doesn't happen) always messes up the players quick bar as it permanently marks slot 1 as MG.
I'm also in favor of this, it doesn't seem to be a difficult task to implement, a simple hotfix can solve this matter
Trolls always know a way to bypass restrictions, and knowing who initiated the vote will make it even more difficult for them to return to the server
Fixed in Dev build 2.17.151825.
Fixed in Dev build 151825.
Fixed in Dev build 151825.
Fixed in Dev build 151825.
Fixed in Dev build 151825.
I am having this same issue on nitrado server. How were you able to fix it?
Hello everyone.
Currently there are no plans to address this.
Regards,
Geez
Hello Vollume1808.
We do not have any administrative power over community servers, the administrators / owners are able to enforce their own rules as long as they are not in violation of our monetisation rules. If the server is in violation of such, please contact infringements@bistudio.com directly.
Regards,
Geez
Hello brudayz,
On which server has this happened and at what time? Unfortunately we do not reimburse any lost items, however we would like to possibly investigate what has happened there.
Regards,
Geez
I would love to hear it constantly too, not every now and then..
@Armor good report, it finally makes sense why I would always get handbugged against wolf AI mutants on STALKER servers after seeing your video
This was before we disabled respawning when uncon on Xbox. Since we disabled that option we have had no reports from people having this issue still. When this happened, our setup was completely vanilla. @Geez
As of 5.15.2024 this is still an ongoing issue. Any "custom loading screen" tutorials are outdated to the point that any server with a current CLS has probably figured it out themselves; but anyone making a server right now (like myself) with a CLS/using old tutorials, is facing this issue.
Hello. It would have been great to be able to make the distinction to prevent this from happening. Unfortunately, the distinction that would be made would open the door to abuse through the use of third-party software to cause a voluntary exclusion so as not to be affected by the 15-second timer. It's technically possible, but you'd have to put too much faith in what's done on the client side.
In T180657#2605683, @Haas wrote:In T180657#2605094, @Geez wrote:Hello Haas.
Can you please send us your CE configuration file?
Regards,
GeezAre you wanting all my server files or specific ones?
In T180657#2605094, @Geez wrote:Hello Haas.
Can you please send us your CE configuration file?
Regards,
Geez
Fixed in Dev build 151825.
Fixed in Dev build 151825.
Fixed in Dev build 151825.