Rick's Blog

That seems reasonable. It's almost possible to get it to work in the current editor by having an entity load an SBX and parent it to that object. But it doesn't work in code, tends to crash.

 

Leadwerks is in desperate need of some near game-ready tools, prefabs, greater control over painting. Things that both SDKers and drag-n-droppers can use. Something that can build and assemble joints for testing.

 

Good stuff.

Leadwerks is in desperate need of some near game-ready tools, prefabs, greater control over painting. Things that both SDKers and drag-n-droppers can use.

+1.

 

Wait +2.

Per entity dlls? That sounds interesting...

Not so much per entity, but per bahavior. One could also have multiple behavior classes in 1 dll if they wanted to maybe make a package of behaviors.

This is just... what can I say?

 

+9001

 

So in other words. You could have a controller component, a sound archives compononent, and animation component, a mesh/model component, a special collision/physics component, and then save these all as a single prefab called, BasicCharacterComponent?

 

Is that how it works?

 

Then you drag drop the prefab into your scene and just edit the parameters of each component in order to define your entity?

>Is that how it works?

 

Since Rick isn't around I'll answer.

 

Yes and many more components than you mention. The idea is each entity has a list of components and it iterates through them one at a time, during its update cycle.

@Pancakes, yep. The way you would make a basic character game object is by starting with an empty game object. Then add all those components. Then you right click that basic game object and click "Make Prefab", and from now on you can add your "Basic Character Game Object" by just a menu option of Make Prefab->Basic Character (if that's what you named it).

 

Then you drag drop the prefab into your scene and just edit the parameters of each component in order to define your entity?

 

I also introduce global game objects, so not everything has to be part of a scene. One of the issues with LE's editor is that everything is at the scene level. Most every game has global (non scene) level objects as well. For example the player object would most likely be across scenes, so instead of having to add the player object in every scene and worrying about what they had in their inventory and such things, you just make the player object a global game object, and now it'll maintain all it's data between scenes.

 

A component would then be created that could set the position of the player game object and that's what would be added to each scene and on it's OnInitialize() event it would set the player's position to where you want it for that scene, but the player object would be the same as it was last scene so you don't have to worry about inventory items they had or any other data between scenes. Nice and simple.

 

 

My first test scene/situation that I'm making is a global player object that has a controller component, fpscamera component, & health component. A scene that has a trigger component attached to a game object named death_trigger (will create a physics body). I'll set this trigger attribute of what it cares about to fire it's events to the player. Then assign the OnEnter event to link to the players health component's Kill() method, which will set it's health attribute to 0. Then link the players health component even OnDead to the fpsCamera component's Dead() function which will fall the camera to the ground and tip it sideways. Will also link OnDead to the controllers Disable() method so the player can't move anymore, and link OnDead to a timer component, which will set a chain of restarting the scene. This shows that one event can be linked to many different methods to create a complex interaction of events.

 

I'm excited

or the camera itself could be an object with it's own set of specialized components... OR there can be a director object which accepts every camera in the scene as a component this way you can save several camera presets or have cameras for cinematics set up but you'll only have to connect the player object to the director as opposed to having several different camera components connected to a single player object... Or!

 

lol there are so many ways of setting it up good luck man

Yeah, that's kind of the cool part about this is that components can really be anything

This is awsome Rick, seriously, if I was only an artist, I would definetely be using this tool to make my games. But when your done with it I will definetely test it out, I know it will become useful in my workflow.

 

Keep up the amazing work RIck.

Keep in mind that programmers will be creating components so it's not just for artists.