Help and FAQ - Hesterry/LSC GitHub Wiki

Help

Q: LSC isn't creating a database! A: This is mostly like because either it's in a write-protected folder, or your antivirus is blocking it for some reason. Try moving the folder to your Desktop, and putting an exception for LSC in your antivirus. Alternatively, running it as administrator should work.

Q: I get an error when trying to run LSC: 'DX11 feature level 10.0 is required to run the engine.'
A: This is an issue with a recent Nvidia driver. Clean reinstalling the driver should fix it.

Q: I messed up my settings. How can I fix them?
A: If you horribly messed up your settings, go to C:\Users\"Your User Name"\AppData\Local\LSC\Saved\SaveGames and delete the UserSettings.sav file. This will only erase your user settings (including search favorites). It will have no effect on your item database.

Other Questions

Q: How was LSC made? What language did you use?
A: I primarily used Unreal Engine's blueprint system, and a tiny bit of C++ code for reading/writing the database.

Q: Why doesn't LSC pull in-game market prices and update the item database automatically? Why do I have to do this manually?
A: Unfortunately, Pearl Abyss hasn't made any tool or API for pulling market information from the server. This means there are only two ways to get this information: 1) Use a packet sniffer to collect the data, or 2) Use software that scans the screen to "read" the data. Both of these methods are against the Black Desert Online Terms of Service. Since LSC was designed specifically to be within the TOS, automatically updating the database prices is impossible for the time being.

Q: I want to update LSC, but I don't want to lose all of my database changes!
A: Other than rare cases, you don't need to erase your database when updating the app. Simply go to the LSC application folder for the old version of the app, open the LSC SubFolder, and copy the ItemDatabase.csv file to the new version of LSC. However, keep in mind that the database is regularly updated with fixes and new entries, and you won't receive these changes if you do this. Soon I will make a patcher tool, so users will never have to lose their data.