[Bug] Console regressions: empty Enter errors, Tab autocomplete broken

[normal88]

Summary

Issue 1 — Empty Enter throws an error

Pressing Enter on an empty console line now throws an error instead of doing nothing.
Steps to reproduce:

• 1.Open the FXServer console.
• 2.Without typing anything, press Enter.

Log output:
[11:45:54] [error] [ fivem] Error invoking command : Command name not found ()
cfx>

Issue 2 — Resource name autocomplete no longer suggests names

Typing ensure , restart, or stop followed by the start of a resource name and pressing Tab no longer autocompletes/suggests matching resource names. This worked correctly in the previous version.
Steps to reproduce:

• 1.Open the FXServer console.
• 2.Type restart followed by a few letters of a resource name.
• 3.Press Tab.
• 4.No suggestions appear (same result with ensure and stop).

Issue type

Server

Repro rate

Always

Server build version

FXServer-early-access b96 win32

OS

Windows 11 25H2

CPU

AMD Ryzen 5 8400F

GPU

NIVIDA RTX 4060

RAM

32GB DDR5

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

In Summary.

Expected Behavior

• Pressing Enter on an empty line should silently do nothing, as in the previous version.
• Tab-completion for resource names after ensure/restart/stop should suggest matching resource names, as in the previous version.

Actual Behavior

• Pressing Enter on an empty line throws a console error every time.
• Tab autocomplete for resource names is completely non-functional after these commands.

Evidence

No response

Additional Context

Both issues are new regressions — confirmed working correctly in the previous FXServer version.

[Gogsi]

A fix for this bug has been implemented and is available in Hotfix 6. Please try again and let us know if the issue persists. Thanks for your help!

[normal88]

Yes, its fixed, Thanks!