ue5-style-guide VS GASContent

Doesn’t matter what you use, as long as it’s consistant. Epic changed their recommendations for skeletal meshes and skeletons between UE 4 and 5, hence the inconsistency. Michael Allar’s UE style guide is a common, long standing one. Personally I use whatever Epic’s current standard is, or what my team is using. It’s also fine to not prefix stuff, but it helps for consistency and searchability. It’s honestly more important to name things well, with cascading specificity: assetprefix_assettype_assetsubtype00 e.g. SM_Rock_Desert01, SM_Foliage_Bush_Dry_Small01 etc.

If you are a large visualization project, you probably aren't coding a game engine, so you'd use whatever the visualizer uses. They typically treat code as data too.

1. https://github.com/Allar/ue5-style-guide (Unreal Engine game engines organization)

other than the usual https://github.com/Allar/ue5-style-guide

From what I can tell there are small number of assets like that, and since it is made by people who worked on the Nexon project they would probably name it just like normal... not to mention they just follow the UE style guide.

If anyone wants to read it, here is the most used style guide that Iron Mace appears to be following (for the most part) in their project: https://github.com/Allar/ue5-style-guide

The guides, including Unreal's own, are usually based on Allar's Style Guide - https://github.com/Allar/ue5-style-guide

A good way to not have to think about project organisation is by using a style guide

Some devs recommended me to read this (Allar's style guide) before starting my next project.

If you've waited so long to where you have to move immense amounts of content all at once, you've failed at project maintenance & organization. If this is a result of initial attempts to get things sorted then yeah it's going to take a while. This is a great time to reflect on how things got this way and how to prevent big moves like this from being needed again in the future. Perhaps you should employ the Allar Style Guide if you have nothing else to go on.

Here is the most useful collection of documentation and project examples I've ever found in the internet: https://github.com/Pantong51/GASContent

It is on the fair bit complex side of things, tho. Which if you are a beginner/blueprint-only, isn't going to fun. You would need a basic level of c++ and a good understanding of blueprints, plus the documentation for that system is shoddy. Here is a collection of resources for learning about GAS, if you wanna give it a go.