Dreamstrata from 2 to 3 : Thoughts

Since initial animation property is now handled with a rollout, you can use it as a quick way to make comparisons if the sprite doesn't literally use animations.

An example would be a turret with multiple shot types. Rather than remembering all the shot types, you can store the names as animations and have the code check for which animation is running to determine how the turret will shoot.

Fun ways to make Construct easier to work with.

The new timeline editor is a wonderful addition which adds the required (something I probably cannot do without) convenience for creating more complex interactions in a more compact manner by eliminating the need to do transforms with the event sheet in place of keyframing with object movement within the editor.

Master key frames is an interesting concept that I've never seen in all the previous timelines I've worked with. Visualizing all your key frame placements within one single line is quite convenient.

The obsessive list of easing options is one of the best parts of this editor, because combining them within context of how fast you animate them yields numerous results within a single easing type itself.

---

With it being an experimental option, it already does production level things. However; when you have a dialog focused above an opened timeline editor, pressing the spacebar while typing text will play the timeline and will eventually crash Construct 3 when you commit to completion of the dialog, namely the `add built-in function` one because that's where I found out that it did such a thing.

Does Construct allow for complex game making? This is somewhere along the lines a question that all ambitious people have asked about Construct in general, not just 3. As a person who developed for Unreal Engine 3 back in 2013, that question is better handle with the word "How" tacked onto the front of it. How does Construct allow for complex game making?

If you have enough logic creation experience, then Construct will be somewhat of a breeze to prototype or build literal logic with. Cleaning up your mess is easy when it's all visual.

Setting aside how complex the playable characters are in the Dreamstrata project, we can look at something a bit simpler, albeit still rich enough in detail to remark on in regards to this subject. The piranha plant that I made in the past few days has plenty of interactions that cater to stuff seen in full body games published on console/pc and whatnot, if that's even a proper measurement to go by...

The piranha plant can be stunned in two ways, killed in two ways so far, shoot fireballs, and bite you. To stun the piranha plant, you either hit him with a forest club for the cheese or smack him while he's actively trying to bite you. On his active frames before he actually bites you is where you try to land the hit. It's a risk/reward play.

All of these things are written into under 40 lines of code blocks and is pretty efficient. A lot is being done with fairly little. You can do complex things with dutiful optimization on any platform. I happen to enjoy the tactile feel of visual scripting within Construct and hopefully the exporting options are being rounded up with the same level of dedication as Construct and Dreamstrata, so that this project will be able to launch to multiple places, allowing as many players to play this as possible.

I had a dream last night (no pun consciously intended) that I played a demo of this and Kill's movement was really fun

Keep up the good work :)

This post may state progress on my project, although it isn't exactly the focus of it. After concluding the Piranha plant enemy logic (a sprite mentioned earlier in this thread), the line count nearly doubled after all the polish and justifications of his/her existence.

From an organization standpoint, that's quite a bit to handle, and with the new coloring options to tack on top of the existing grouping options, it can be cleaned up to the point where you have it all under one tab of an entire event sheet. It feels like managing your Microsoft OneNote.

This is an important thing to bring up because I read from somewhere that some guy says that your projects can start to become unruly when your events start stacking up, but c'mon, seriously? The internet is dangerous sometimes, because people's opinions can become gospel if that's all you have to measure things by.

So in conclusion, my organizational skills are probably far better than the person who said that event sheets can become unruly, because my events are going to be colossal, and they are NOT going to be unruly.

After adding a fat pink bunny into the forest, I was dying when his unstoppable might was mowing me down.

During this time however, I realized that I forgot to pass his UID into the animation function and two bunnies started doing the same action. When developing AI, you should have a clone somewhere out of the play space to see if you miss any UID passing to the functions that want them.

All the while, I realized that when you open the condition dialog and type "u, i" into the search field, the Pick by Unique ID still shows up. Secret keywords in the program. I like it!