Game Ideas

It would be good to upload my gamemode inside the game, its lame to open the browser and zip files for it

For now, huge asset pack are uploading in .zip, i think it can be better to be in .pak file instead because this will allow to support extra features such as : Better compression with oodle (not sure if it is supported in the basic asset cooking) Integrated with unreal Encryption of the .pak file (bult-in into unreal) A way to use encryption: When the user upload a assetpack that wants to be encrypted, on the nanos assets website, there is the encryption key that the user can put into his server. It will function like a vault api key, and the user when updating his asset pack, can choose to regenerate randomly a new key. This key will be used to decrypt the asset pack so only his server can use this asset pack. The rest of my idea is based on my other idea here : https://feedback.nanos.world/ideas/p/vault-assets-pack-as-collection-of-assets For the compression, the .pak file could be used to store all the references of a asset (So a static mesh name pak file will also include the materials, textures, ...) For the encyrption, there will be no need to seperate each assets in the pack individually since theses assets will not be used in any other asset collections since it is encrypted. Here is some ressources i found online that could help for review: https://forums.unrealengine.com/t/load-assets-from-mounted-pak-files There is also "UnrealPak.exe" for the use case.

Lots of package will likely get outdated after some time it has been uploaded by the maintainer, so editing (forking) a package should be relatively easy by default (unless the maintainer doesn't want it to be). So here is a list of ideas : Package License: Like in a github repository (screenshot below), each package could specify a type of licence, and this type of licence will have a short display that will tell the user what he can do with the package (Will also list if he can fork the package or not) Package forking: Forking a package should relatively be easy, especially if a github repository is mentioned. It should be also easy to to search for forks of a package so a user can search more easily some modified versions of a package. I don't have some ideas right now of how it can be implemented, but i will update this discussion if i find some. Inspiration from other game: Some Publishers and IP Holders will likely don't want a Package/Asset to have their name on it especially if they don't have any relations to it. So one way could be to add another filed into package, that will be different to tags called "Inspired from", it will be a repository of games, movies, animes. So developers will be able to specify from wich game their Asset/Package is inspired from. So if a user wants to have a Star wars experience, instead of searching only for games that has part of the title star wars, it will search on "Inspired from" the Star wars Saga, and every package/asset based on that will be display even if the name does not include it.

For each package/ asset pack so we can modify a single file instead of uploading the full file all over again A new zip would be created/Clients will download only the files that changed from starting from the last zip upload

(being able to downgrade packages or asset packs) But what I have in mind is asset packs creators being able to upload HQ and optimized versions of an asset pack without conflicts

The user don’t need to see those. A tag could be used to identify them. (Example : Rounds) The implementation stays the same you just have to hide them. (Do not hide them from the New game tab though)

There will be always duplications on the Vault, especially from server makers that will upload their assets into a seperate pack like "MyServerName Content Pack #1" even though the same assets are present in different Asset packs on the vault. And also the fact that on a asset pack, almost no server will use 100% of the assets in a pack, so the storage used becomes useless. One of the solutions could be that the asset pack will act as a collection of assets and not a pack of assets. In other words, one asset that is the same will be replicated in any other Asset packs, so the user will not have duplicates. Example : User1 upload Assets a1,b1,c1,d1. User 2 upload Assets a2,b2, c2, d2. Before User 2 finishes uploading since b2, c2 are same as b1, c1, then User can choose wether or not to use the asset already on vault or force to use his own. Then the Vault will change the reference of theses asset to the pack that has been uploaded by User1. So when User3 will join the server of User2, he will have theses assets to download : a2, b1, c1, d2. And after if User3 want to join server of User1, he will only have to download a1, d1. Changes + Solutions: I don't know all of them, but one of wich should be on Asset.toml, and that it the Unreal path should also been mention for each assets, so that the Vault can automatically edit the AssetUnrealBasepath if a reference is modified (Deletetion, not same, ...) Also the use of Symbolic link will probably be handy. For all the references of asset, there is the tool called "AssetAudit" that can list all the depencies of a Asset, so theses informations can be stored on a txt file that has the same name as a Asset (material, static mesh, ...) so it will know all references of this asset. This has advantages: Vault is smarter 😎 Way less duplicate assets Less usage of storage And disadvantages Will need a "Nanos World Unreal engine plugin" to make sure the assets cooked have the exact same parameters (a slight difference for example in compression, game will consider as a whole new asset). And for other stuff like references, ... Lots of different folders References madness There is probably lot of imperfections on my ideas, so you can comment below 🙂

Display images title in game and on the website

Generate Delta files for Vault updates (ex : 0.1.0 -> 0.1.2, 0.1.1 -> 0.1.2) so we don't have to download 2gb when the Assets.toml got updated. When the delta is too big just don't create a Delta file and download everything again