Comment thread: Scripting Tutorial

Hugh

The comment system is currently broken. Please use this thread as a comment thread for this blog post.

Brute

Great guide. In my opinion, no matter how capable a system is, tutorials like these are by far the most importing thing to have. Very often I see things (like frameworks, layout languages, converter tools, publishing tools, ...) that have their functionality hidden so deep in their documentation, that you have no idea how to start.

What I did not quite get: when a blueprint is changed, all instances need to be deleted and replaced (like here and here)? I guess "instances" is not even the right word to use here. Maybe I do not get the reasoning, but it seems highly inconvenient.

OstrichGuy

Brute wrote: »

What I did not quite get: when a blueprint is changed, all instances need to be deleted and replaced (like here and here)? I guess "instances" is not even the right word to use here. Maybe I do not get the reasoning, but it seems highly inconvenient.

I feel that something like a "refresh" button may come in handy for this. At least something that deletes and recreates a blueprint for you.

dushan

Brute wrote: »

What I did not quite get: when a blueprint is changed, all instances need to be deleted and replaced (like here and here)? I guess "instances" is not even the right word to use here. Maybe I do not get the reasoning, but it seems highly inconvenient.

That's definitely a somewhat controversial design choice - we discussed it a bunch and it's a trade-off between simplicity and power. We think we can mitigate some of the lost power with clever UI (like that 'refresh' button) and the simplicity win is huge. I posted answer to a similar question elsewhere:

Our blueprints are cloned instead of instanced for simplicity and robustness. Keeping track of dependencies on blueprints is a significant cognitive load - especially when you start overriding some properties on the instanced entities and conflicting changes happen upstream in a blueprint (or perhaps another blueprint that your blueprint depends on). Add multiplayer editing to the mix and it would be pretty chaotic .

For blueprints that change often (e.g. Tile in this guide) you'd use a kind of a spawner but it's not quite ready and I didn't want to complicate things any more - hence the unnecessary deleting & recreating. We're also planning editor functionality to mass update entities from their original blueprints but it will be a user initiated action rather than automatic.

This is exactly the sort of thing that the Architect Edition is for - we want you guys to test drive our crazy ideas and if they don't work out as we hoped, we'll take the crazy down a notch .

dushan

Here's a quick follow up video:

It doesn't have the polish of Hugh's videos but the man has suffered enough

-D