I am making a story based game, that is going to have a huge map, with lots of assets in it. I have implemented custom optimization, that locally stores all the assets that player cant see into a replicated storage, and keeps in workspace only those in sight. But i wonder if that will be enough to guarantee nice performance with a huge map and tons of assets?
What are the best strategies for optimizing a map?
P.S. My scripts are pretty optimized too, so no need to worry about them
Try not to make unnecessary unions, if possible make them meshes. I would also look into procedural generation/rendering if the map scale is huge enough to warrant it.
If you want to load in a map, instead of loading in the entire model/object at the same time, try iterating over the map and loading in chunks of it slowly.
Like actually retrieve it. The client can’t retrieve stuff in ServerStorage, which is why it’s called Replicated storage, server and client can access replicated storage whilst server storage can only be for server.
When I say that I meant to see it. It’s more safe to store it in ServerStorage to keep it inaccessible from hackers and hacked clients. I understand the client can’t access things in ServerStorage.
For example, I previously explained this to someone else.
If you wanted to make a custom leaderboard, and you wanted to get a players avatar photo, you can setup it up to where, you have a LocalScript in StarterPlayerScripts. You can request the data stored in ServerStorage, using a remote function. Through this remote function, you request the avatar image, then load it onto the GUI. Simple.
Then you would fall off the map when he lags lol, and also let’s not forget that it’s inefficient, even though the hacker can’t access it, a hacker is determined to copy all part frames.
Performance > safety (unless it’s a big security issue)
You don’t get it? We’re storing it inside of ServerStorage so people can’t just access it while it’s inside of ServerStorage… You’re not making any sense…