next »

[eigenbom]

Prinsessa is right about the extra enum, but also, using a get<Foo> returns a Foo&, and so u don't need to dynamic_cast on the caller side. It's all based on static polymorphism (if I remember the term properly).

And that, of course. Unfortunately I haven't managed to bind identical functionality to AngelScript, so you still have to do some sort of bulky cast<Emitter @>(get(type("Emitter")) in scripts ATM.

Egh, sounds a little messy.

[eigenbom]

A small snapshot of me working on Moonman:

[Kurt]

woah neat, mind telling me what you did to get that visualized? would maybe motivate me to put some work in 

[eigenbom]

sure, its a tool called Gource

[zath]

Your git commit animation looks like a neat enemy concept for the Rain World!

[kcbanner]

That EC system sounds great. I implemented something similar but without the concepts of systems, the components received events directly. That because a bit unwieldy do the amount of even handlers and such, looks like I need to take a lesson from your book!

[eigenbom]

That EC system sounds great. I implemented something similar but without the concepts of systems, the components received events directly. That because a bit unwieldy do the amount of even handlers and such, looks like I need to take a lesson from your book!

There's practically a 1-to-1 correspondence between components and systems anyway, as the components are typically used to store properties or state realted to one aspect of the game. E.g., the SpriteSystem uses the Sprite component to track what frame an animation is in. I also have protected parts of a Component and friend them to Systems, just to make it clear that some data is for certain systems only. As for event handlers, I have an onEvent(EventType,void* data) in every single system. So I'm not sure separating the concepts of Component and System will clean things up that much.

[Octopus Tophat]

A small snapshot of me working on Moonman:

As much as I understand computers and programming, I've never understood what the hell these visualizations are supposed to mean. I've seen a lot of them too.
Are they based on files or something?
What the bawls.

[eigenbom]

As much as I understand computers and programming, I've never understood what the hell these visualizations are supposed to mean. I've seen a lot of them too.
Are they based on files or something?
What the bawls.

They are operations on files in directories, as seen by the revision control system. So when I add a new file, it appears as a dot in one of those sprouts. So all the red items in the second image are files in the data/item directory.

[Octopus Tophat]

Ah ok.
Is that little green guy just an average of the locations that are being added?

[eigenbom]

Ah ok.
Is that little green guy just an average of the locations that are being added?

Yeah more or less. When you have multiple people working on a project, you see one little person for each programmer.

[oahda]

None of the posts above helped me understand even in the slightest what that animation is supposed to be.

HALP

[oldblood]

Wow, thats insanely cool. I'm tempted to do it for my own project now... maybe one day haha.

Other than just being a super cool visualization, does it actually assist with any aspects of version control?

None of the posts above helped me understand even in the slightest what that animation is supposed to be.

HALP

I guess in basic terms, it's a visualization of each commit being made to the game in a time-lapse. So you're seeing the game literally grow in different areas as the commits of work are being made by the developer.

...That may be a terrible summary...

[eigenbom]

That's a good explanation oldblood. You have e.g., 1 second per day, or whatever the time scale is. When the dev edits a file the dev sprite goes over to it and zaps it. The lines show the directory structure.

Doesn't help with anything, but the full thing shows off some interesting events, like big refactors, or when i add a new resource type and start populating it, or that time when I removed boost from my version control , which sent the spring system careening wildly (as boost has 1000s of files). Don't ask me why I ever committed it to my repo .. but I've learnt the lesson since to keep most of my deps out of the repo.

It's all file-based though, so it's not a great visualisation. Imagine if we could run a tool to do this: check out the source for each day in development, start the game and auto-play it for a minute or so, take a screenshot or mini-gif, then repeat for the entire history. Now that'd be awesome.

[eigenbom]

Update: The world generator now knows about the sizes of things, which means that when it is placing something (a painting, a door, a chest, etc.) it can make sure that it doesn't overlap an existing object. Its a very useful functionality, and means, for instance, that I can "fill a room" with things, like paintings. More importantly, the generator can select a rectangular region and delete all the things that overlap it, in order to make room for an important object, like an door to a subregion.



Speak of doors, they are now more flexible, and can be any height. Which means you may see some of these little doors hidden in the game somewhere. Horizontal doors (trapdoors) are also now possible, and block fluid as you'd expect.





Forest Arc 1 is pretty much finished, and will be pushed out in an alpha update very soon. It's a few steps back in terms of "stuff", but is a necessary step to start designing how the items and resources will flow throughout the game. This has involved a lot of code but also spreadsheets, to figure out the strengths of items, resistances of enemies and blocks, and so on. Here is one of the small spreadsheets I was using to figure out the resistances of some of the simpler animals:



With the help of my friend Alex McDonald, today we brought a few of the new creatures to life, giving them walk cycles and simple behaviours:

[eigenbom]

[happymonster]

Scary!

[AbsintheGames]

*pic*

So lifelike.

[sam_suite]

spookier than SOMA

[RujiK]

Them doors for midgets are awesome! You gotta have some important gnomes disappear into them at some point!
"Come back here gnome!! Ahh, he went in the little door!"