I completely and utterly loved both of those games, but if I had to choose I’d go with Baldurs Gate 3, simply because it gave me many many more hours of gameplay while keeping things fresh enough for multiple playthroughs and is very fun multiplayer with up to 4 people, though also fun single player. Expedition 33 is a lot of fun but strictly single player and for 1 playthrough, replays are just the same but a little harder.

Highly recommend both when you can, each will consume a nice part of your life

I see, but the first example option having no code still makes it harder to translate and show the user, so my vote is for the option with a code and message in the json.

Message straight on the body is the worst possible response for an error here, it is bad design to straight up show the error from the back end to the user, usually it needs translation and/or adaptation due to message size on the front-end to show properly, and applying those on top of a message will make it stop working as soon as anyone in the backend decide to change a dot or comma anywhere. It is a bad idea to let the backend make direct impact in the front when you can because backend devs won’t even know what impact they are causing until later in testing and it will be harder to trace back and fix.

IMO you need at least a json with code and message, the front will ignore the message for everything but testing and use the code to match a translation file that will get the proper message, making it easy to translate and change as needed without having to rebuild the whole backend along with front changes. You may also have an extra parameter there in some cases when you want to return where more specifically the error occurred or an array of errors. Status usually not needed as you can get those from the http code itself.