This will be cool to see. I hope there is a good mode architecture like P-ROC has. Hell, I wish that was available in Visual Pinball.

But yes, documentation can make or break an API. It might be powerful, robust, awesome,but if it can't be taught, nobody can utilize it.

Huh? The way for creating modes in P-ROC is done with individual switch hits in its own class. That's not available in Visual Pinball. I even tried making a hack for it, but not sure if you can directly call a method(through a string) in a class in VP.

Python runs circles around Visual Basic. Trust me, I have to work in VB every day, where I would much rather be in Python.

Features like ball save, ball lock & such are the building blocks for features of a pin. I could envision a language or GUI where a pin rule set could be created with little to no programming knowledge. You have a standup target? Tell me what you want the point value to be.

In terms of documentation, I tried to bolster P-ROC's wiki, but didn't get further than many stub pages. I wanted to document everything possible, from coding best practices to cab construction & variances. Then I ran out of steam. Was hoping others would join me in the missing gaps to reverse engineer pinball and show you how to program P-ROC boards for your dream machine.

If you are starting from scratch, here's an idea: take pictures from beginning to where you are at right now. Start with a picture of the "main" board, then the next pic show the power connection to the next board, another pic with the data connections and so forth. Nice bird's eye view. Pictures are worth a thousand words here, just like you can't explain brain surgery over the phone.

For P-ROC, getting a single light to flash is the equivalent of "hello world" in programming. Then one are off to a good start.