Full Games List
Featured Games
New Games
Reviews
Media
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
Profile
Locker
Play ListsGARAGE'S PROFILE
Close
Search
Filter
All
User Statuses
Content creation (technical)
Moderator / developer response needed ...
I'd like to publish a tool soon which might help debugging larger storylines. Since it's going to be a quite powerfull viewer it might be not approriate for publishing openly.
So: I'd like to have your opinion(s) first ...
BTW: no, it's not done yet, but I have an early preview version ready which would enable you to evaluate it's "powers" ...
PS: it's that JS thingy I had been talking about a while ago.
I'd like to publish a tool soon which might help debugging larger storylines. Since it's going to be a quite powerfull viewer it might be not approriate for publishing openly.
So: I'd like to have your opinion(s) first ...
BTW: no, it's not done yet, but I have an early preview version ready which would enable you to evaluate it's "powers" ...
PS: it's that JS thingy I had been talking about a while ago.
Content creation (technical)
author=MarrendAs I recall we had that conversation before ... a few month ago. And I think n_stories is actively relying on this.
I think you're right, though, I have not consulted Mr. Help File on this matter. However, as I recall, characters that have not been INTRODUCEd can appear in BRACHes.
By the way, Mr. Helpfile tutoring on ITRODUCE stories:
author=Mr. HelpfileEmphasis added.
Because this story introduces a new character to the player, there is one more line we need to include. After the line which declares the story, add the line "INTRODUCE = 10". This lets the game know that our custom character is introduced in this story event. This is important. Characters will not appear in any story events unless they have first appeared in a story event designated as an Introduce story. However, characters may appear in branches of stories whether or not they have appeared in an Introduce story.
Content creation (technical)
I think there's minor glitch in Nami/Nami_story.txt:
This seems to be intended as the second story for Nami (ID = 39). She doesn't appear in the main branch so the game will probably not check for her being introduced thus this one might play before her introduction ...
STORY 1001
PLACE = Courtyard
ID = 0
(There's that girl from before. She's sitting on a bench all alone...)
A: Sit down next to her.
B: Talk to her.
C: Ignore her and keep walking.
This seems to be intended as the second story for Nami (ID = 39). She doesn't appear in the main branch so the game will probably not check for her being introduced thus this one might play before her introduction ...
Content creation (technical)
Funny things part #3:
Story\Built-in\game_stories_8.txt, line 3305:
Yup. No condition ... loads just fine. Well, it's about Keika ;)
Story\WolfypackElizaMain.txt, STORY 40:
Mixing and and or ...
Story\Robin\robin_story_1.txt, line 1088 and 1111:
Mixing or and and in a conditional branch (same c-jump is used in two places).
Story\YAK\YAK intro_story.txt, line 7:
The trailing comma doesn't trouble Heartache 101 ...
BTW: line 209:
Same here.
*EDIT*: how can I remove one of my own posts?
Story\Built-in\game_stories_8.txt, line 3305:
CONDITION =
Story\WolfypackElizaMain.txt, STORY 40:
CONDITION = 38 DONE OR 39 DONE AND 74 LIKE
Story\Robin\robin_story_1.txt, line 1088 and 1111:
C: 4 DONE IN game_stories_5 AND 5 NOT FRIENDLY OR 29 DONE IN game_stories_1 AND 5 NOT FRIENDLY
Story\YAK\YAK intro_story.txt, line 7:
Introduce = 48,42,
BTW: line 209:
Introduce = 49,50,
*EDIT*: how can I remove one of my own posts?
Content creation (artistic)
Content creation (technical)
author=MarrendI think you wanted something like that (would fit the comments near that condition too):
That one Emiko CONDITION was, literally, the worst CONDITION to figure out. I don't remember reading the part about parenthesis, though. Might have helped things out a bit.
Though, funnily enough, I think that story still works? I have no idea! Like, the only play-tests I've done with her was when the "22 DONE" portion of the CONDITION was true!
CONDITION = 22 DONE OR (20 DONE AND 25 NEUTRAL) OR (9 DONE AND 25 LIKE) OR (12 DONE AND 25 FRIENDLY) OR (7 DONE AND 25 LIKE)
Stuff like that isn't too easy to debug in the first place. Plus it's probably not the only possible story at any point in time and it's not even PRIO = High, so it's hard to tell the exact reason why it triggered. And to make it even worse: your conditions are far from being independend from each other. Half of them are satisfied just by getting Emiko to LIKE.
And those stories are probably interdepend with each other too.
*EDIT*: my example-CONDITION above should be correctly formed. Chains like A OR B OR C OR D OR E would not need parenthesis.
Content creation (technical)
At the risk of been seen as picky, my homemade Javascript based parser is more-or-less able to parse the "offical content" now so he starts finding ... "funny things":
Profiles\YAK\YAK_profile.txt
starts with a line containing nothing but a single "=".
Jup. The game just loads this file with out complaining. Seems the profile-parser is reaaallly fogiving ;)
Story\Emiko\emiko_story.txt, line 985
contains the following CONDITION:
This is ambigious since the precendece of OR ./. AND is explictly undefined.
Story\Emi\emi_stories.txt, near line 1727:
There's an ERASE CENTER after the JUMP; this is probably dead code (= unreachable). NB: That's not really an error.
Story\Wolfypack\ElizaMain.txt, line 1574:
There's no ID = 17, neither in wolfy_pack.txt nor game_profiles.txt (those two are loaded by the story-file).
And according to the official ID-List:
(I think someone mentioned the stray ID=17 in this tread half a year ago or so)
Profiles\YAK\YAK_profile.txt
starts with a line containing nothing but a single "=".
Jup. The game just loads this file with out complaining. Seems the profile-parser is reaaallly fogiving ;)
Story\Emiko\emiko_story.txt, line 985
contains the following CONDITION:
CONDITION = 22 DONE OR 20 DONE AND 25 NEUTRAL OR 9 DONE AND 25 LIKE OR 12 DONE AND 25 FRIENDLY OR 7 DONE AND 25 LIKE
author=Mr. Helpfile(Emphasis added).
A condition can contain both Logical Or and Logical And provided parenthesis are used. The parenthesis are required in such a case; Heartache 101 will not evaluate the condition correctly without them.
Story\Emi\emi_stories.txt, near line 1727:
ID = 9
ERASE CENTER
JUMP TO 31
ERASE CENTER
Story\Wolfypack\ElizaMain.txt, line 1574:
ID = 17
And according to the official ID-List:
author=ID-Listthis char does not appear anywhere else in "WolfPack".
ID 17 = Torako Koizumi {Neckochi, unpublished}
(I think someone mentioned the stray ID=17 in this tread half a year ago or so)
Content creation (artistic)
Content creation (technical)
author=MarrendYep. NOT WEDENESDAY OR NOT THURSDAY is probably interpreted as (NOT WEDNESDAY) OR (NOT THRUSDAY).
Awkward! Oh well.
That reminds me, I wanted to research Emiko's CONDITIONs in regards to when she's at work.
*Edit: At least, that's what I recall was a potential issue? The "NOT WEDNESDAY OR NOT THURSDAY" condition possibly returning true on both Wednesdays and Thursdays?
According to boolean algebra A OR B is TRUE if at least ONE of A or B is true.
NOT WEDNESDAY is true on each day but a WEDNESDAY, NOT THURSDAY is true on each day but a THURSDAY.
So: if it's any other day then a WEDNESDAY, the first condition is TRUE (and thus the OR). On the other hand if it is a WEDNESDAY, it can't be a THURSDAY. Thus the second condition is true, and thus the OR is true, too.
Thing is: you have stories with "CONDITION = WEDNEYSDAY OR THURSDAY" in the same location too. So even if the "NOT WEDNESDAY..." stuff doesn't work out, there is no guarantee, that you notice it immediately - since you will have two PRIO = High stories battling for the players attention. (And at least I tend to lose track of the weekdays anyway, so it's hard to nail it).
*EDIT*: According to boolean logic the correct negation of CONDITION = WEDNESDAY OR THURSDAY would be CONDITION = NOT WEDNESDAY AND NOT THURSDAY
(Spoken language is not mathematically presice).
PS: Trust me, I studied computer science for ages ;)
Games - Tester
Games - Other
