For me, Byte Sized Heroes is a passion project. It's not a "I'm going to work really hard at this and make lotsa money" project, it's a "I'm going to work really hard to help the progression of indie development, especially in areas where certain game engines need more open sourced project to reference and learn from, in the same way Game Maker always was back in the day, hailing from the evolution from Klik N Play in indie development".
That's surely a long-winded goal. TL;DR: I wanna make free shit.
The Level Building
In the editor, everything is a simple click and drag interface. Objects that can be clicked and dragged into the game include characters, enemies, obstacles, utilities, and the like, and will all be organized in categories, characters can be given lines of dialogue when spoken to in the overworld, but can also be modified dynamically in the Map or Story Scripts; Enemies can function the same way, but have set attack animations and patterns; Obstacles are like map tiles that consist of animations like machines, waterfalls, etc., with Scriptable functionality; and Utilities consist of things that modify how the game runs such as controlling camera movement like snapping it in place or keeping it from moving past certain points or even slightly pull the camera to it, setting objectives (including welding the objective to a physically dynamic pick up, or trigger zone), of course Trigger Zone which triggers an event either when touched by the player or the entire time they're within it's area, Scene Volumes that change animations of certain objects visible in runtime (such as adding snow, or dripping rain); and much more.
Map Scripts are scripts that will run every time you enter the current map.
Story Scripts contain a flow chart of individual script sheets identified by thumbnails and names, these names are used to transition from one Story Script node to the next in the chart, which happens when specified. This allows the person building the Script to easily create branching paths, because when the Script Node "Switch to Story Node *Node Name Here*" is used, it will create a the node and link in the Story Scripts editor and will branch off for each "Switch to Story Node" node created. Because you can call a function when players make choices, this could be used to make a story with branching paths.
Lastly, Game Mode Scripts are used to determine the score. The creator of the Game Mode adds the amount of teams in the match. For instance, for a free-for-all kind of Game Mode, you'd add a team each time a player spawns. Otherwise, you'd create to teams right off the bat, and split them up based on different traits of the player, such if they're in a party together, or their skill levels. After the teams are decided, they objective for scoring is then chosen. We'd determine if, when a player is killed, the other player is on the opposite team, and if they are and we're playing a Deathmatch kind of Game Mode, add a score for that killing player's team.
There will be reference Scripts one could build from inside the editor for every script used in Byte Sized Heroes.
This is important in reference to Construct 2, because when using animations, all the other animation frames would be kept in memory. Because one object is cloned to create each placed object in the world, the game would hold ALL of the animations of the game in memory, all the time. That is a A LOT of information. Instead, the game will keep only the animations that will be used in memory, and animations can be added to this "Memory Pool" as we will call it through scripting, by using the "Preload Animation" script, so as to be able to use it exactly when needed.
Map data including where these objects are placed are typically saved in a folder specific to the browser the game is being played in, but all the information can be exported in JSON format, and reloaded into the editor later. All information exported and loaded in this fashion will always be forward compatible, so nobody will ever have to update their projects for new versions of the game.
Based off this information, you can easily assume that modders will be able to create mod packages that include new sprites and animations for the game to be used in scripts for other modders, and because Script sheets can be exported to seperate JSON files as well, they can also be imported to include in other modder's packages.
This workflow would allow people the ability to utilize tools like Github to push and pull updates as a team, as well as the ability for modders to collaboratively add other mods to their own.