When a QoL feature is implemented it does not necessarily make it required. The game currently has a "send to camp" feature but you don't actually have to use it. You can role-play that your characters must go to camp to unload stuff and move each item 1 at a time. For those wanting less of the tedium (which means less immersive in this case) and a more convenient way to manage inventory there are QoL features.
The question is if this even is QoL feature ...
I mean, by definition QoL should leave rules intact after implementation ...
Its actualy kinda funny that curent "send to camp" is actualy QoL feature, IF its is used by person who wanted to store something in camp but forgets to do that when he was there ... our person would then need to tediously go back to camp, find a container, place item there and travel back to the world ... boring ...
So Larian implemented this covenient feature that allows him to do the same with just a few clicks. > QoL improvement ... since there is no limitation to travel between camp and rest of the world (if there should be is different topic tho) no rule was broken ...
Theoreticaly, even tho it is a little questionable ...
We can also claim that this feature is kinda QoL in case, when you find really nice loot at end of the dungeon, but you are allready overburdened ...
Technicaly you should have go to camp (or vendor), make room, return back and then finaly loot the item ... now you can simply send the item into camp and save yourself that tedious and boring travels.
Problem starts when player starts to use this feature as mobile unlimited inventory. :-/
That is the point, where feature become exploit.
If you will send to camp litteraly every item you find, whole reason of carry weight is sudently gone.
That is the reason (at least in my eyes) why is so tedious to send to camp items one-by-one ... to outweight its benefits ... its certainly covenient on one side, but also quite tedious on the other ... if we would be able to use this smoothly, it would seriously break the system, since simply removing carry weight completely would make the same outcome, with even less work (both for us and developers btw). :-/
