I don’t know what you want from me, you wrote this topic, I gave you an answer. With 5 seconds of reading ProfileService (not ProfileServer) API you tell me it’s not good.
I shouldn’t of said anything about the queue (the queue was a recent addition, the reason it’s there is to stop the default queue from giving warnings)
The fact that you have 6 datastores per player is already a problem, you have to make 6x the calls if you would use one datastore per player.
ProfileService does this and abstracts it, so that it always loads and saves the data with haste and without data loss.
You clearly haven’t done research on ProfileService, because one of ProfileService’s biggest selling points is it’s session locking. Do research and learn what race conditions are.
If you don’t want to use it, that’s fine don’t use it, but don’t argue about it with me when you have done 5 seconds of research.