![]() ![]() It has also been requested on Unity forums too ![]() It is an alternative style of visual scripting with a big following - a quick look at the number of users of construct 2 and the number of succesful 2d games made with clickteam fusion should be a good enough indicator. ![]() So What are the advantages over our current visual script: Some actions/condition blocks can be negatedįunctions that can take parameters can be used as well, by using a special function condition block and nesting conditions/actions under its row Rows can be nested under other rows (called sub-events), can be commented, disabled or re-enabled (just like commenting code) On top of that the user can use expressions in both columns - so potentially use gdscript for more specific instructions. This clear divide makes for a very easy to learn way of setting game logic. On the left column the user can only attach conditional methods, on the right - only action methods. Both columns can be populated with logic blocks from nodes and their children that the sheet is attached to (node methods). The event sheet is pretty much a spreadsheet with two columns - a conditions column and an actions column. What is an event sheet visual script in the other engines: It is a very different approach from the one with blueprints and people learning to program are still requesting it on facebook and other godot community forums The proposal here is for a second visual scripting system, that is similar to event sheets in Construct 2 (proprietary), Multimedia fusion (proprietary) and Gdevelop (open source) We currently have a visual scripting system similar to blueprints in Unreal - connecting nodes. Here is the test repo that I added the prototype project toĮveryone is free to fork or do pull requests □ ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |