Flow Chart Coding

[DCurrent]

Here's a quick tip when working on OpenBOR projects or anything else that requires keeping track of logic: Create a flowchart. There's a great online tool available here that's fast, simple to use, and expands your chart size on the fly. I like to use it even though I have access to the latest MS Viso and PowerPoint.

As an example, this is a chart I used today while developing a more powerful native follow up system for OpenBOR. I wound up deciding on a different design, but it still saved me a lot of time that would otherwise be wasted on trial and error coding.



HTH,
DC

 

[msmalik681]

Very interesting way of working. I would definitely be interested in seeing more tips like this.

 

[mersox]

I love flow charts. I recently had to make one for a bonus stage, becuse there were (seemingly) too many variables, and I needed to add some focus on what was really important. I used pen and paper though, way less elegant.

 

[maxman]

I'm not familiar with the flow chart coding there, but I had seen it somewhere before. Isn't it like brainstorming ideas? It looks cool to help making basic concepts and ideas for projects.

 

[Bloodbane]

With some personal experience on scripting, I recommend creating flowchart cause it really helps describing events that should be scripted.

Isn't it like brainstorming ideas?

Nope. It's to clarify what should be done when an event occurred basically. However if the events have conditions, you'll need to list what happen if condition is true and what if not true.