This is a personal project. It's a city builder game with procedural terrain generation. I'm currently working on the first playable prototype and you can find a lot of code for managing. But you can navigate on the map and ask for container drop and rover drop (on the TerrainGenerator scene). You can find other prototyping stuff like shader and window editor tool.
- TerrainGenerator : Endless terrain generation (mesh creation, level of detail)
- UIScene : Contains a simple UI window test (drag'n'drop, resize, movable window)
- SampleScene : Shader test
- CoreScene : Contain manager (automaticly loaded when launching other scene)
- Check the script for endless terrain generation
- Custom property attribute for linking data to monobehaviour (Descriptor for example)
- SceneScriptBehaviour to enabling all monobehaviour on the scene after loading
- WindowUIBehaviour script for drag'n'drop, resize, move a UI window on canvas.
I use a custom script to disabling all monobehaviour on scene when it's saved. It's because when I load async the scene I don't want the game freeze on the last 10% of the loading (even if it's "async"). So I use a custom script to enable all monobehaviour after the scene is loaded. This script watch how much time is used for enabling other script and manage enable them on multiple frame to be sure the game wont freeze. If you want to see all monobehaviour activated when working on a scene you can right click on the SceneScriptBehaviour script on "SceneScriptAutoGenerated" GameObject and choose "All Visible". It's very usefull to see the UI for example.
I'm working now on the localization module (I want to make it as independant as possible) and resources on the map.