Potential Games LLC

The cleanest way to close a Java GUI application is to dispose of all top-level resources (JFrame instances, for example) and allow the AWT/Swing thread to close itself. Calling System.exit(0) or Runtime.getRuntime().halt(0) is often prescribed, but not recommended, as it could preempt proper shutdown procedures in your application. If your Java GUI application uses DISPOSE_ON_CLOSE mode, check that your process is exiting cleanly. If it is not, the most likely culprit is that the AWT Event Dispatch Thread is still active. This is well-known AWT/Swing behavior, but there is a scenario in which Java will refuse to shut down this thread, even with all resources closed and disposed. Read the rest of this entry »

Potential Games is excited to announce the (not yet public) next major milestone release of our (name yet to be announced) Potential RPG. Development of the Potential Platform, our MMORPG client-server, database, and user interface engine, dominated the Alpha phase. Potential RPG BetaAlpha, destined to become Beta, is the first (alpha) gameplay release directly targeting the final game design. BetaAlpha shall focus on gameplay enhancements, as well as any necessary improvements to the Potential Platform. At this stage, Potential RPG remains a closed alpha game, for approved Alpha Playtesters only. The prospective roadmap:

1. Alpha (closed playtesting)
2. BetaAlpha (closed playtesting)
3. BetaBeta (controlled invitation playtesting)
4. Beta (invitation/open playtesting)
5. Public Release!