I want to get some input on how you guys tend to develop your stories in your games for I can fine-tune the web application.
For now, I currently have a Plot Element section being defined, along with Characters and Monsters. I plan on also adding prop management(items).
The Characters and monsters will allow designers to fine-tune a personality and overall description for the characters and monsters.
Future plans include some OHR engine integration. Such as being able to easily manage stats to make the game more easier or difficult with some preset stats. A possible battle simulation run via simple JavaScript to test out how a character equipped with various equipment at a specific level will fair battling with a specific monster. For the simulations I will be taking the exact math which OHR uses in the engine, placing it in JavaScript and having it run an automated battle for the designer can see the results. Battle simulations are something which CUSTOM.EXE greatly lacks, and is a great tool for debugging battle difficulty issues.
Other future plans which may or may not be added is the ability to export various lumps for characters and monsters. Once you fine-tune your battle simulations, why re-type all the stat information, it's easier to export the DT0 lump for Character exports, DT1 lump for Monster exports. As said, this may not even be implemented, as this will be a considerable amount of work, especially to keep compatible with newer versions.
I hope to have a prototype of the RPG Storyboard web application up and running within the next few weeks. Any ideas for what you would like added to make managing a storyboard easier, let me know. It will be open-beta once I release it, in hopes to squash bugs and obtain additional feature requests.
I will also be looking for artists who can make web templates(HTML/CSS) to prettify it, the open-beta will look very black/white(it's a prototype after all). The template artist will be credited for their work.
Subscribe to this thread to see the latest updates, as I will be using this as a journal for the developments and to announce the open-beta, once available.
UPDATE: Well it seems I may have an open-beta sooner than later. I put much effort into it and it's coming along nicely. I will post another update in the next 3 hours with information on where the open-beta can be accesses from.
UPDATE: Well, the basic system is now complete and is ready for your testing pleasure! I made the registration process short and sweet, so please don't spam it. Visit the URL below(not publicly available) to create an account, only a username/password is required to register. Once that is done and no error is received, you will be bumped to the login screen, re-enter in your username/password to proceed and enjoy!
http://rpg.chronoboy.com/accounts/register/
Once logged in, you will be-able to create a new RPG storyboard from the top navigation. Not the very bland HTML and lack of CSS(any help designing would be wonderful). In the creation page, don't worry about the 'Public' checkbox yet, it is not used, and all storyboards can only be seen by your logged in user, full permissions are also in effect, so don't think that sharing a URL will bypass this. Once your storyboard is created, you can go ahead and add elements to the story.
Please provide me with any feedback(besides how black/white the color scheme is). I currently have debug logging turned off, but will enable it shortly to catch any errors that you may see. If you see an "Unhandled Exception" error, for the time being give me the URL and what you were trying to do. I will have a proper error handler up soon to catch these and Email them to me.
UPDATE: Once I enable the Public option, I will be putting together an example of how a storyboard might look. I have created a few test storyboards during development to make sure the components work. I am thinking of putting together a storyboard for either Wondering Hamster or Walthros, as I have played these games quite thoroughly and it is known in the community rather well. This will mean the examples will include spoilers of the actual game and I'll need to dissect the game itself. Since Wondering Hamster is not yet complete, if James creates an account, I'll transfer the storyboard into his account for he can continue work on it, if pleases.
UPDATE: Bugs have been squished, thanks to Mewmew for finding them and pointing them out to me. A minimal theme has been applied to make it more eye pleasing.
UPDATE: There is a now a link on the top to see all the Public Storyboards, users will still need an account to view the storyboards and will be prompted to sign-in. I will be adding a form to edit your storyboard information, such as title, description, and if it's public or not.






Especially if you stop making your game for a few months, you can sort of forget where everything was.