[BDS-19490] my BDS system crashes upon all slash commands Created: 16/Jul/24  Updated: 27/Jul/24  Resolved: 27/Jul/24

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.21.3
Fix Version/s: None

Type: Bug
Reporter: imagebearer Assignee: Unassigned
Resolution: Awaiting Response Votes: 0
Labels: None
Environment:

i7 9700@3.6 GHZ
64 Gig Memory
running Windows 10 pro


Confirmation Status: Unconfirmed

 Description   

the bedrock game plays and everyone can log in great.

but once someone tries a slash command it drops everyone.

i run 5 players at a time on 64 Gigs of memory, never an issue.

i have had this server since v1.17.11.01

i have never had issues like this till this update.

i have had issues with behavior packs before (alot of red errors upon boot) but never gave the game any issues.



 Comments   
Comment by [Mod] Jarl-Penguin [ 27/Jul/24 ]

You can find the server logs in AppData/Roaming/internalStorage/Dedicated_Server.txt. Please attach them to the report.

This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

Comment by imagebearer [ 24/Jul/24 ]

i re-installed the entire server saving my backup file and same issue is happening on brand new install. any ideas what this could be?

Comment by imagebearer [ 24/Jul/24 ]

both of my worlds same crash scenarios. crashes upon any forward slash commands

Comment by imagebearer [ 24/Jul/24 ]

this is a 3 year old world, yes it happens on every forward slash command. i dont know where to find any type of crash logs

Comment by [Mod] Greymagic27 [ 17/Jul/24 ]

Are any game logs produced such as crash logs or server logs you can attach?
Does this happen on a new fresh world?
Does this happen with every command?

Generated at Sat Jan 11 08:25:45 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.