DO NOT play around with that. Get everything backed up ASAP when you start getting warning hints about a hard drive. Be glad you even got a warning before it broke.
The VN part of Honey is, as you would expect, dialog heavy, and it's been quite a pain to set up. Even for simple dialog, if you wish for anything more complex than a simple message background+line of text that doesn't go beyond that single message, it requires a lot of variable and organizational work, as you said. Best advice I can give is to setup a whole event page dedicated just to that, and you call that page whenever you need dialog around - and then, you comment like crazy to find your way around each individual dialog event!
Dialogue systems are difficult, for me, and it's good to make a proper system for it and also to think about what you want to do later on.
<?xml version="1.0" encoding="UTF-8">
<DialogueSets>
<Dialogue>
<Name>Example</Name>
<LineCount>1</LineCount>
<WheelTrigger>Example</WheelTrigger>
<Line id="0">
<Speaker>SomePerson</Speaker>
<Portrait>SomePerson_Neutral.png</Portrait>
<Duration>5</Duration>
<Sound>ExampleLine.wav</Sound>
<Text>This is a line of dialogue.</Text>
<Line>
</Dialogue>
</DialogueSets><?xml version="1.0" encoding="UTF-8">
<DialogueWheelSets>
<DialogueWheel>
<Name>Example</Name>
<Option id="0">
<Name>ExampleChoice</Name>
<DialogueSet>ExampleDialogue</DialogueSet>
<Text>This is an example dialogue choice.</Text>
</Option>
</DialogueWheel>
</DialogueWheelSets>Will do this today. Thanks!
I repo about every 30 minutes or major change if sooner, nightly local and remote. I'm truthfully worried more about finding time to swap and reinstall everything than I am with the drive failing, TBH. Time is hard to come by at year's end with my day job. Sleep is even harder to come byDO NOT play around with that. Get everything backed up ASAP when you start getting warning hints about a hard drive. Be glad you even got a warning before it broke.
Still hard at work this last week on things. The majority of the work has been in code restructuring some things that were becoming unmanageable -- I know not not fun AND not much visual to show off for all the hard work.
We did added some more visual detail to a few of our ships though:
Ashodin said:
Abe Bly said:
However last time I tried it broke the 
Decided to post some gifs! If you guys don't mind.
lol... yeah the two games would make a very interesting baby
I'll be in the corner.
The VN part of Honey is, as you would expect, dialog heavy, and it's been quite a pain to set up. Even for simple dialog, if you wish for anything more complex than a simple message background+line of text that doesn't go beyond that single message, it requires a lot of variable and organizational work, as you said. Best advice I can give is to setup a whole event page dedicated just to that, and you call that page whenever you need dialog around - and then, you comment like crazy to find your way around each individual dialog event!
For Honey, just for the mechanical workings of the VN segment, no plot event and the likes, I have to use about 700 different events (I'm speaking dialog events only here - for the function calls that make everything work, there are only 5 or so). Of course, that's for a VN which heavily rely on multiple choices, so for a JRPG, if you're only looking for "normal" dialog with minimal player input, you should be able to manage with a lot less, with the caveat that unless you variable like mad, each individual message would be a different event, or close to it. Of course, that's using my system - if anybody's got anything better using C2's visual script, I'll be interested too - though it's already far too deep in the rabbit hole to change for Honey at this point - but for next time :-D
EDIT: I should clarify that my take on things only apply if you intend to use C2's visual scripting. If you can do external scripting or use other languages, as shown below, there are far better and more efficient ways to get a dialog system done :-D
And just to show something new, since I'm not posting much these days because it's only animation, animation and more animation :
Yeah that is how I would approach it to. Lately I have been using the Functions for calling and displaying dialogue. Its usefull since you can call different parameters, next line of dialogue or using that to call a different dialogue option based on a Global Variable.
For example I once had a Global Variable for a certain mood of a character. If the mood was "Happy" it would call a different text within the function.
The functions are quite usefull and you can organize pretty well with it.
I also used Arrays once for storing dialogue and setting the text to the location (in the array) and dialogue I needed. But that was quite a hassle and difficult to adjust later on.
But uh my explanation is not the best
Went back and added more challenge to 1-2's first area.
After a long time with very little time spent on my project, I am finally going to try, once and for all, to seriously work on my game and try to get one or two to market.
Odds say I will fail horribly, and I am not near as talented as the many awesome artists and animators here. But, I figure you might as well chase your dream once in life, while you still have the chance.
Here's the first floor of my first dungeon!
Some notes:
1. There's a small "puzzle" in that you need to step on a panel to open another doors. Doors are color coded to indicate which panel they go with.
2. I use a statue with a red orb to give a general subtle direction to the exit of the floor. Not sure if this will persist for all dungeons.
3. The enemies in the dungeon will consist of spirits and skeletons.
4. This dungeon was created to be a dungeon (for training purposes), and not house prisoners.
Here's two Gif's of the entrance:
Inside the dungeon:
Probably won't post anything new till far after the dungeon.
Any chance I can get some feed back on the dungeon design?
