qbcore-framework / qb-multicharacter

Multi-Character System Used With QB-Core :man: :woman:
GNU General Public License v3.0
33 stars 237 forks source link

[BUG] SkipSelection Spawn #249

Open WPinzonDev opened 3 months ago

WPinzonDev commented 3 months ago

Describe the bug When setting Config.SkipSelection to true in the config.lua file of qb-multicharacter, an error occurs when trying to load a previously created character. After closing the game (without closing the server) and trying to load the character again, the screen stays black with a "loading" indicator in the bottom right corner that never goes away, preventing the character from loading properly.

To Reproduce Steps to reproduce the behavior:

Go to the config.lua file in qb-multicharacter. Set Config.SkipSelection to true. Start the game and create a character. Close the game (but not the server). Restart the game and try to load the previously created character. See the error: the screen stays black with a "loading" indicator in the bottom right corner that never disappears. Expected behavior The expected behavior is that when loading a previously created character with Config.SkipSelection set to true, the character should load correctly without the screen staying black and without the "loading" indicator being eternal.

Screenshots: Sin título

Questions:

When you last updated: I have been testing for several days and the last test was today. Are you using custom resource? which ones? No, I am only using qb-multicharacter, nothing custom. Have you renamed qb- to something custom? No. Additional context I have noticed that the issue seems to be related to setting Config.SkipSelection to true, as the problem does not occur when it is set to false and characters load correctly. This suggests that there is a specific bug with the SkipSelection functionality.

d56Wr commented 2 months ago

Confirm, same thing happens on my server. It took me way too long to find that bug :(

RichardGrant-93 commented 1 month ago

I added a print inside qb-multicharacter:client:spawnLastLocation does not seem to ever be getting called.