This week has mostly been focused on getting more of the general aspects of the editor done. Things that apply to all gamemodes.

I've now added support for all the movement types: rails, launch pads, wall runs, and fans! Rails and wall runs don't have any parameters to customize speed and stuff, cause they were just never designed for that. But launch pads and fans were! So all their properties are exposed in the inspector. There are also generic triggers for launch pads, wall runs, and fans. So that way you can make your own models for these objects, and just attach a trigger as a child. And when placing wall run triggers down, they will automatically conform to the hovered surfaces angle, for easier placement.

When I first added the inspector, I actively chose to not support multiselect. Buuuuuutttttt then I got to thinking about it a bit more, recently. And I realised it wouldn't actually be too hard... right? RIGHT?! Yes. It ended up being pretty simple. So now you can edit multiple objects from the inspector. There are some limits, however, For instance, only mutual inspectors will be shown. So if you inspect a fan and a launch pad, only the transform inspector will appear. There are also objects that have set transform constraints. For instance, you cannot rotate a rail. So multi selecting objects with different transform types is not possible... at all. But that's more to do with the gizmos in the world, rather than the inspector.

Since I added parenting, I felt a hierarchy view was quite important. So from here, you can view all the objects in the scene, and view the relationships between them. You can also do some basic organisation, like renaming objects, and moving them in the hierarchy. This all ended up being a much greater challenge than I had anticipated. Particularly with optimisation, since it needs to be able to support potentially hundreds of objects. But it can now!

This is where all your logs are stored, and categorised as: Info, Warnings, and Errors. Right now, I've got logging for the scene loading process. Using this, you can check how long it takes to load, as well as how long each of your custom models take to load. You can also clear the log, and search through it. There will also be some logs that have a little magnifying glass icon on them. This indicates that the log has a context, and clicking it will select the object that the log relates to.

For linear check point courses, you can now change the order that each point must be reached in. I've also added a handy route line that displays when you have the spawn, or a check point selected. This will visualize the order of everything. You obviously can't have multiple points with the same order value, so if there are conflicts, it will be displayed in the log.

This partially applies to the "More robust publishing / updating" point below, but now, whenever you press play, a series of checks will be done based on the level type to determine if the level is valid. So for Timed, you need 1 spawn, and at least one point. You also cannot have any order conflicts.

Some assets, particularly primitives, and other generic models, now have a material inspector. From here, you can select from a range of materials.

Here's the list from last week with striked out features that have been completed. Of course, this list does not necessarily include everything, and may have stuff that will be scrapped.

• Support for launch pads, fans, and wall runs, all of which will be completely configurable (launch pads have been partially added already)
  
• Light objects, and audio sources
  
• Ability to control the order of Timed checkpoints
  
• Editor hierarchy view
  
• Editor log
  
• Much more default assets
  
• Options to set up leaderboard history snapshots
  
• Options to set up medal and trophy times
  
• Support for Capture, Infection, and Zen Chat
  
• More robust publishing / updating (require publishers to complete the level first)
  
• Ability to view leaderboards from the level browser
  
• Documentation / manual for the editor

And that's all for this week! At the moment, I really just wanna get all the existing mechanics implemented. But once that's all done, I wanna start work on some new, and more experimental mechanics, that probably wouldn't work all too well in the base game.

Once again, thank you for your patience,
Tobey

https://test-steamproxy.haloskins.io/steamstore/app/2560140/The_Local__Supporter_Package/

[discord.gg]

Things have been a bit quiet, and that's because for the past 2 and a half weeks, I've been working on the level editor! Yes, it's in development, and its coming... whenever it's ready. I just wanna discuss what's already been made, and what's still to come. And of course, everything here is work in progress and absolutely subject to change, or could be entirely scrapped. I'm also open to suggestions, so if you've got ideas then feel free to share. The level editor is the perfect place for me to introduce some weirder mechanics.

Essentially, the entire "lifecycle" has been complete. You can create a level, edit it, publish it, update it, and people can subscribe to and play it. So the fundamentals of this update are all done! As for what types of levels you can currently make: all the Timed route styles are currently mostly supported (points, aim, points non-linear), as well as Zen (also work in progress). I do also plan on supporting Capture, and probably Infection. Orders won't be supported, and Inferno is unlikely.

Most of my time has been spent working on the editor, and I'd say it's coming along very nicely. If you're familiar with game engines, you'll feel right at home here. The editor can be split into 3 parts: the Scene View, the Asset Browser, and the Inspector.

The Scene View is the 3D part of the editor. Here, you can drag in objects, and move, rotate, and scale them. I've also got snapping, which is particularly important for voxel models, where 1 voxel is equal to 0.1 units. You also have complete control over rails. There are no rail presets. You are free to add points, and move and bend as you please. But I can't take much credit for that. That credit goes to Sebastian Lague and his incredible "Path-Creator" package. The Local as a whole probably wouldn't exist without his work on that! And while I'm shouting out, gotta shout out "manaporkun" and their "UnityRuntimeTransformHandles" package, which is what I use to do the transform gizmos. So when you're moving objects around, or editing rails, you can thanks those two for their understanding of mesh generation, bezier curves, and quaternion maths. There's also lot's of other nice things to speed up iteration, like duplication and multiselect.

The Asset Browser is where you can... browse your assets! The level editor will come with many assets, but the real star of the show here is the ability to import custom models! So if you want to make something entirely new, you can make your level in your modelling software of choice, and just import that instead. There are some limitations to this, however. The main one being that only glTF models are supported, specifically the .glb variant. I've gone with this, simply because its the easiest to do. glTF is also an open format, and is supported by Blender out of the box, so it just made sense. The other potential limit is with materials and shaders. If you're just sticking with standard Lit PBR materials, you should be fine. But otherwise, you may run into issues. The specific package I've used for handling imports is called Unity glTFast. I've also set up a LOD system. So you can name objects in your models ending with, for example, "_LOD0", and that object will then be included in the first level of detail.

From the Asset Browser, you can also access your templates. I've spent the last couple days working on this. Starting with a hierarchy system, allowing you to make objects children of others. Rails are unfortunately excluded from this, because they are particularly complex. But they're not excluded from the Template system. This essentially just allows you to save an object, its hierarchy, and all the relevant properties, to a new asset, that can be created anytime, on the fly. This is perfect if you were to create your own launch pad model. You could import the model, add a generic launch pad trigger (that's not implemented yet, but should be soon), and then create the template. You've now got your own custom launch pad! Worth noting however, that when you spawn from a template, that spawned asset is entirely new, and has no link to the template. So changes to the template won't be applied to instances of it.

Lastly is the Inspector. If you're familiar with game engines, you'll already know what this is. It's just an area where you can edit more specific properties of the selected object. So each object will have different types of inspectors. All of them have a transform, but rails also have their own inspector, and imported models have a LOD inspector. This is also where you create templates, and set parents. There will be many other types of inspectors added as development goes on.

From the editor, you can also quickly publish, and update your workshop entry, and also play the level almost instantly. In regards to level types, at this time, changing a levels type after creation will not be possible, due to different gamemodes having different objects, and structures. But if you really want to change stuff, all projects are saved as formatted JSON, so you can modify, and fix things up manually if needed (although I wouldn't recommend it).

This is just where you can view your own projects to edit, as well as play levels that you've subscribed to. This is also where you create new projects.

This is just what allows you to play levels that you're either developing, or subscribed to. For Timed, leaderboards are automatically created when a level is played for the first time after being published. Even Ghost Data is supported. There is also some anti-tampering measures in place to stop people from just editing a level and moving all the check points to the spawn.

I'm just gonna list some things off here. But please do keep in mind that this list may include things that will end up being scrapped.

• Support for launch pads, fans, and wall runs, all of which will be completely configurable (launch pads have been partially added already)
  
• Light objects, and audio sources
  
• Ability to control the order of Timed checkpoints
  
• Editor hierarchy view
  
• Editor log
  
• Much more default assets
  
• Options to set up leaderboard history snapshots
  
• Options to set up medal and trophy times
  
• Support for Capture, Infection, and Zen Chat
  
• More robust publishing / updating (require publishers to complete the level first)
  
• Ability to view leaderboards from the level browser
  
• Documentation / manual for the editor

So that's what I've been working on. Once again, I don't know when this update will release, but I will likely be doing some more dev logs as I work on it more (probably not as big as this one, though).

Thank you for your patience,
Tobey


https://test-steamproxy.haloskins.io/steamstore/app/2560140/The_Local__Supporter_Package/

[discord.gg]