PoC Phase Complete

-
Okay, so all the key tests are done, and now I can move on to phase 3, the real program. Phase 1 was brain storming. Once it had an outcome of interest defined, the next phase was to figure out key missing knowledge to prepare for actual development (PoC's). That was the phase that just ended. I needed Proof of Concepts. Such as the 2D Physics based rocket system, the fuel line interactions, the dynamic MonoBehaviour attachment, and some initial draft of how the coding system will run/be generated.  
Concept, Man, Papers, Person, Plan, Planning, Research
source https://pixabay.com/photos/concept-man-papers-person-plan-1868728/

But now, I've moved onto actually building the real product. For this part, I need to settle down on architectural needs. I tend to strongly oppose putting a heavy architecture in place, but ignoring it is a sure fire way to over complicate everything. So I'm looking at things that absolutely need it, and how I will approach it.  

To begin with, I'm planning to build a C# IDE in game.  That means the parser needs to run, I need formatting, coloring and intellisense. So, I'll be creating a project that will depend on reflection and the parser to gather information on current code members. I'll probably try to release that separately on the asset store.

But then I also went through a few tests of how the ship will move, how the parts will connect, and how code will have to adapt to them. There is a physical later that the code will interact with the ship. That "physical" components are referenceable, and that the connections between them, such as fuel lines, are also referenceable in code. Additionally, I need to detect uses of potentially dangerous classes, methods and even namespaces, such as System.Io.File and command execution, or even network ability.  

And that's not even the game play.  Now for the real work.

Comments

Post a Comment

Popular posts from this blog

C# Parser and Code View

-
Image
I don't have any Proof of Concept in place yet on this, but I've finally started designing how the code editor UI will work, then designed some of the basic architecture needed to support how the UI would work, and finally, this lead to how I need to protect the user from dangerous code (you can write C# to format your machine, or try to steal memory from other apps like passwords), while also improving the debugging and teaching abilities. Alright, so I'm planning on having Classes exposed, as an item, then under the class view, is a list of items, like fields, properties, methods, etc. When selecting one of the members, you get details like notes, title, version history; for beginner coders I felt giving them a really easy ability to step back a version or two to something that last worked. Then show the code.  To be able to provide physical system responses, we need to detect all sort of things, like an infinite loop. In the case of an infinite loop, we don't
Read more

A Momentary Lapse of Passion

-
Image
There have been so many projects that I have lost passion for while developing, that a few years ago, I challenged myself to start paying close attention to this. To start researching the psychology of what drives me to and from a goal. In that time, I found that Game Design is actually a key value in life's success. And Codavore will survive because of this. :D I'll tell you a short story of why I lost my passion for Codavore and then how I revived it. In hopes that when you hit this runners wall, you might be able to get past it as well. source:  https://pixabay.com/photos/light-bulb-idea-creativity-socket-3104355/ 2 weeks ago, I wanted to start working on the dialogue system, as that would be a common need in this game. I had seen the start of an instructional video on how another person had created this really nice looking Dialogue Graph, and kept looking for opportunities to apply it (or similar) in my code. So my first steps into the dialogue pushed me into worki
Read more

How to Setup a Multi-Scene Unity Project for Startup

-
Image
Scene loading played an important role in this, and I believe my approach is pretty sound and proven highly useful. Let me know what you think, and what ideas you tend to apply for handling this. When developing in a multi scene project in Unity, one of the most annoying things I've worked with in the past, is the need to boot into the right place. I've worked with and developed dozens of different approaches, most of which falling into custom menu options, or resetting the default loading scene. I want to share a solution I had that is simple, small, and has worked great. General Overview Codavore is broken into several scenes BootStrap, Ui and Level/Scene/Room. Boot Strap guarantees the order of several things like my service locator and a few others. Next there is the Ui, which contains the menus and such. And finally, we have the scene with the content for the game I'm on. There is a fourth, "DontDestroyOnLoad" where Unity puts all its don't destroy object
Read more