Full Games List
Featured Games
New Games
Reviews
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
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
Add Review
Subscribe
Nominate
Submit Media
RSS
This page is for discussion of the technical side of content creation. If you have a technical issue or question with regards to a character or story you are creating, talk about it here.
(The old Custom Content thread can be found here)
Helpful things:
--> Medium build girl, the .psd that was used to create the built-in characters, is available with layer names in English.
--> Kudos to SparkleFox for finding us a male tachie generator, authored by "彩 雅介" (Aya Mayabaikai?)! This one is put together as a program, but has PSD files with layer-names in Japanese. No "fan-translation" available at this time.
--> You can use any of these images for making new custom characters.
--> Notepad++ with syntax highlighting for Heartache 101 can be a big help with story creation. To set it up, go to the View menu and set User Defined Language to HeartAche. Then close View, go to the Language menu and select HeartAche. (If you already have Notepad++, here's userDefineLang.xml by itself)
--> Mr. Help File has, regrettably, forgotten to mention certain locations! They are as follows:
Beach (sunset), Grounds (sunset), Roof (sunset), Bedroom (Morning), Downtown, Studio Room.
Note that these locations must be specified via a PLACE command. To the best of my (ie: Marrend's) knowledge, they cannot be obtained via the generic "School" or "City" code.
--> If you are writing story content that includes the appearance of existing characters (built-in or custom), the following list may be of reference:
ID 0 = The Player
ID 1 = Nakajima Miki {flowerthief, Built-in content}
ID 2 = Ikeda Keika {flowerthief, Built-in content}
ID 3 = Onishi Tsubasa {flowerthief, Built-in content}
ID 4 = Kaneshiro Shihoko {flowerthief, Built-in content}
ID 5 = Kaneshiro Riho {flowerthief, Built-in content}
ID 6 = Sato Akari {flowerthief, Built-in content}
ID 7 = Hiraoka Hinami {flowerthief, Built-in content}
ID 8 = (Secret character) {flowerthief, Built-in content}
ID 9 = Watanabe Junko {Nekochi, "Junko"}
ALSO = Tsukino Emi {Silent Pheonix, "Tsukino Emi", in progress}
ID 10 = Mitsuya Masako {Marrend, "Masako"}
ID 11 = Monotami Ruri {Marrend, "Uchioniko"}
ID 12 = Nemoto Mayu {Marrend, "Uchioniko"}
ID 13 = Terakado Shoko {Marrend, "Uchioniko}
ID 14 = Shirazu Izumi {Marrend, "Uchioniko"}
ID 15 = Watanabe Aoi {Nekochi, "Junko"}
ALSO = Lambaria Yuu {KimotoDragoon, "Yuu", in progress, Caretaker: Marrend}
ID 16 = Ran Fujioka {Neckochi, unpublished}
ID 17 = Torako Koizumi {Neckochi, unpublished}
ID 18 = Yumemi Tanno {Neckochi, unpublished}
ID 19 = Umehara Joruri {Marrend, "Joruri"}
ID 20 = Sakuragawa Fuyuki {Fuyuki, "Fuyuki", cancelled}
ID 21 = 21 Ways {dude797, "21"; Caretaker: Dozen}
ID 22 = Ikari Kyouki {Dozen, unpublished}
ID 23 = (Reserved for Nekochi)
ID 24 = (Reserved for Nekochi)
ID 25 = Kuwabara Emiko {Marrend, "Emiko"}
ID 26 = Tanaka Yoko {triad2/Noone42, in progress}
ID 27 = Katanashi Seira {triad2/Noone42, in progress}
ID 28 = (Reserved for KimotoDragoon)
ID 29 = Shitazawa Arika {Dozen, unpublished}
ID 31 = Maeda Eriko {triad2, "Meada"}
ID 32 = ? Genji {triad2, "Meada"}
ID 33 = ? Ryoko {Dozen, unpublished}
ID 34 = (Reserved for Tthedragon)
ID 35 = (Reserved for Tthedragon)
ID 36 = Murakami Megumi {Render, unpublished}
ID 37 = Kawano Fujiko {Render, unpublished}
ID 38 = Matsuhara Akane {Render, unpublished}
ID 39 = Momohana Nami {GloopMaster, Unknown, in progress}
ID 40 = Konohana Midori {LordNight, "Midori", RMN only, in progress}
ID 41 = Natsume Rika {LordNight, "Midori", RMN only, in progress}
ID 42 = (Reserved for LorSquirrel)
ID 43 = Hasegawa Kanon {LordNight, "Midori", RMN only, in progress}
ID 44 = Kirihara Kana {LordNight, "Midori", RMN only, in progress}
ID 45 = (Reserved for LordNight)
ID 46 = (Reserved for LordNight)
ID 47 = (Reserved for LordNight)
ID 48 = (Reserved for LorSquirrel)
ID 49 = (Reserved for LorSquirrel)
ID 50 = (Reserved for LorSquirrel)
ID 51 = Shiromiya Kagami {BDFalcon, unpublished}
ID 52 = Tsuchitsuru Airi {BDFalcon, unpublished}
ID 53 = Kimura Shizuka {Mute, unpublished}
ID 54 = Columban Kuri {?, unpublished}
ID 55 = Shikimori Asuka {Render, "Clique", unpublished}
ID 56 = Shikimori Sanako {Render, "Clique", unpublished}
ID 57 = Nakao Yasuko {Render, "Clique", unpublished}
ID 58 = Sakaki Usagi {Render, "Clique", unpublished}
ID 59 = Waifu Mai {pegaso, "Mai", unpublished} (temporary reserve?)
ID 60 = Makoda Yuuki {Ilan14, unpublished}
ID 61 = Hisatsuki Seiryuu {BDFalcon, unpublished}
ID 62 = Torahashi Mio {BDFalcon, unpublished}
ID 63 = Eienji Rie {BDFalcon, unpublished}
ID 64 = Hamaguchi Takako {dewelar, unpublished}
ID 65 = Yoshimura Noriko {dewelar, "Noriko"}
ID 66 = Ichini Sanshi {BDFalcon, unpublished}
ID 67 = Kimura Sachiko {Mute, unpublished}
ID 68 = Hitsuragi Yuureiko {BDFalcon, unpublished}
ID 69 = Hanata Haruka {BDFalcon, unpublished}
ID 70 = Shiraki Kotone {BasedMG, "Kotone", in progress}
ID 71 = Kurokawa Sarako {BDFalcon, unpublished}
ID 72 = Kurokawa Mikari {BDFalcon, unpublished}
ID 73 = (Reserved for LorSquirrel)
ID 74 = Yamisaki Eliza {Kevincalanor, Wolfpack}
ID 75 = Yamisaki Alessa {Kevincalanor, Wolfpack}
ID 76 = Nakamura Yuriko {Kevincalanor, Wolfpack}
ID 77 = Harada Himeko {Garage, "Winggirl"}
ID 78 = Fujikawa Sayumi {Garage, "Winggirl"}
ID 79 = Fujikawa Mayumi {Garage, "Winggirl"}
ID 80 = Hashimoto Midori {Ertad, unpublished}
ID 81 = (reserved for Ertad)
ID 82 = (reserved for Ertad)
ID 83 = (reserved for Ertad)
ID 84 = (reserved for Ertad)
ID 85 = (reserved for Ertad)
ID 86 = (reserved for Ertad)
ID 87 = (reserved for Ertad)
ID 88 = (reserved for Ertad)
ID 89 = (reserved for Ertad)
ID 90 = (reserved for Ertad)
ID 91 = (reserved for Ertad)
ID 92 = Itawa Miyuki {RukasuWYZ, "Ijona on'nanoko", probably canceled}
ID 93 = Shogowa Yuka {RukasuWYZ, "Ijona on'nanoko", probably canceled}
ID 94 = Fujita Suki {RukasuWYZ, "Ijona on'nanoko", probably canceled}
ID 95 = Chihiro Sato {RukasuWYZ, "Ijona on'nanoko", probably canceled}
ID 96 = Shingoza Ayumi {RukasuWYZ, "Ijona on'nanoko", probably canceled}
ID 97 = Sawada Merika {Garage, "Winggirl - Pathways"}
ID 98 = Nagai Shika {Garage, "Winggirl - Pathways"}
ID 99 = Harada Hibiko {Garage, "Winggirl - Pathways"}
ID 100 = Robin Clark {Wowzer_, "Robin"}
ALSO = ? Takuya {Kevincalanor, "Built-off", tachie/profile only}
ID 101 = Miyazaki Kiyoka {Nedras, "First Years", unpublished}
ID 102 = Matsumoto Atsumi {Nedras, "First Years", unpublished}
ID 103 = Kagawa Yasuna {Nedras, "First Years", unpublished}
ID 104 = Azuka Ishikawa {Nedras, "First Years", unpublished}
ID 105 = Hayashito Kaede {ShinigamisApples/KiyokoKaia, unpublished}
ID 106 = Hayashi Kitsune {Garage, "Kitsune"}
ID 107 = Sasaki Riku {Garage, "Nadeshiko"}
ID 108 = Yamaguchi Ayame {Garage, "Nadeshiko"}
ID 109 = Kimura Nanashi {Garage, "Nadeshiko"}
ID 110 = Takahashi Karen {Garage, "Rivalries"}
ID 111 = Inoue Azami {Garage, "Rivalries"}
ID 112 = Yamamoto Hina {Garage, "Crossover", unpublished}
ID 113 = Kojima Daishi {Garage, "Crossover", unpublished}
ID 114 = Hashimoto Chiyo {Garage, "Crossover", unpublished}
ID 121 = Furuya Reika {ScarbucksCoffee, "Reika", unpublished}
ID 122 = Furuya Shunpei {ScarbucksCoffee, "Reika", unpublished}
ID 123 = Shimada Tsukasa {ScarbucksCoffee, "Reika", unpublished}
ID 124 = Shimada Tomo {ScarbucksCoffee, "Reika", unpublished}
ID 130 = Tanaka Grace {mysteriousone3, "Grace"}
(Note: You don't need to care about this list if your story events will not include existing characters, as ID numbers for characters in separate files don't have to be unique)
--> Finally, I've listed the game cheats here. You can use these during story events to test your content:
(The old Custom Content thread can be found here)
Helpful things:
--> Medium build girl, the .psd that was used to create the built-in characters, is available with layer names in English.
--> Kudos to SparkleFox for finding us a male tachie generator, authored by "彩 雅介" (Aya Mayabaikai?)! This one is put together as a program, but has PSD files with layer-names in Japanese. No "fan-translation" available at this time.
--> You can use any of these images for making new custom characters.
--> Notepad++ with syntax highlighting for Heartache 101 can be a big help with story creation. To set it up, go to the View menu and set User Defined Language to HeartAche. Then close View, go to the Language menu and select HeartAche. (If you already have Notepad++, here's userDefineLang.xml by itself)
--> Mr. Help File has, regrettably, forgotten to mention certain locations! They are as follows:
Beach (sunset), Grounds (sunset), Roof (sunset), Bedroom (Morning), Downtown, Studio Room.
Note that these locations must be specified via a PLACE command. To the best of my (ie: Marrend's) knowledge, they cannot be obtained via the generic "School" or "City" code.
--> If you are writing story content that includes the appearance of existing characters (built-in or custom), the following list may be of reference:
ID 0 = The Player
ID 1 = Nakajima Miki {flowerthief, Built-in content}
ID 2 = Ikeda Keika {flowerthief, Built-in content}
ID 3 = Onishi Tsubasa {flowerthief, Built-in content}
ID 4 = Kaneshiro Shihoko {flowerthief, Built-in content}
ID 5 = Kaneshiro Riho {flowerthief, Built-in content}
ID 6 = Sato Akari {flowerthief, Built-in content}
ID 7 = Hiraoka Hinami {flowerthief, Built-in content}
ID 8 = (Secret character) {flowerthief, Built-in content}
ID 9 = Watanabe Junko {Nekochi, "Junko"}
ALSO = Tsukino Emi {Silent Pheonix, "Tsukino Emi", in progress}
ID 10 = Mitsuya Masako {Marrend, "Masako"}
ID 11 = Monotami Ruri {Marrend, "Uchioniko"}
ID 12 = Nemoto Mayu {Marrend, "Uchioniko"}
ID 13 = Terakado Shoko {Marrend, "Uchioniko}
ID 14 = Shirazu Izumi {Marrend, "Uchioniko"}
ID 15 = Watanabe Aoi {Nekochi, "Junko"}
ALSO = Lambaria Yuu {KimotoDragoon, "Yuu", in progress, Caretaker: Marrend}
ID 16 = Ran Fujioka {Neckochi, unpublished}
ID 17 = Torako Koizumi {Neckochi, unpublished}
ID 18 = Yumemi Tanno {Neckochi, unpublished}
ID 19 = Umehara Joruri {Marrend, "Joruri"}
ID 20 = Sakuragawa Fuyuki {Fuyuki, "Fuyuki", cancelled}
ID 21 = 21 Ways {dude797, "21"; Caretaker: Dozen}
ID 22 = Ikari Kyouki {Dozen, unpublished}
ID 23 = (Reserved for Nekochi)
ID 24 = (Reserved for Nekochi)
ID 25 = Kuwabara Emiko {Marrend, "Emiko"}
ID 26 = Tanaka Yoko {triad2/Noone42, in progress}
ID 27 = Katanashi Seira {triad2/Noone42, in progress}
ID 28 = (Reserved for KimotoDragoon)
ID 29 = Shitazawa Arika {Dozen, unpublished}
ID 31 = Maeda Eriko {triad2, "Meada"}
ID 32 = ? Genji {triad2, "Meada"}
ID 33 = ? Ryoko {Dozen, unpublished}
ID 34 = (Reserved for Tthedragon)
ID 35 = (Reserved for Tthedragon)
ID 36 = Murakami Megumi {Render, unpublished}
ID 37 = Kawano Fujiko {Render, unpublished}
ID 38 = Matsuhara Akane {Render, unpublished}
ID 39 = Momohana Nami {GloopMaster, Unknown, in progress}
ID 40 = Konohana Midori {LordNight, "Midori", RMN only, in progress}
ID 41 = Natsume Rika {LordNight, "Midori", RMN only, in progress}
ID 42 = (Reserved for LorSquirrel)
ID 43 = Hasegawa Kanon {LordNight, "Midori", RMN only, in progress}
ID 44 = Kirihara Kana {LordNight, "Midori", RMN only, in progress}
ID 45 = (Reserved for LordNight)
ID 46 = (Reserved for LordNight)
ID 47 = (Reserved for LordNight)
ID 48 = (Reserved for LorSquirrel)
ID 49 = (Reserved for LorSquirrel)
ID 50 = (Reserved for LorSquirrel)
ID 51 = Shiromiya Kagami {BDFalcon, unpublished}
ID 52 = Tsuchitsuru Airi {BDFalcon, unpublished}
ID 53 = Kimura Shizuka {Mute, unpublished}
ID 54 = Columban Kuri {?, unpublished}
ID 55 = Shikimori Asuka {Render, "Clique", unpublished}
ID 56 = Shikimori Sanako {Render, "Clique", unpublished}
ID 57 = Nakao Yasuko {Render, "Clique", unpublished}
ID 58 = Sakaki Usagi {Render, "Clique", unpublished}
ID 59 = Waifu Mai {pegaso, "Mai", unpublished} (temporary reserve?)
ID 60 = Makoda Yuuki {Ilan14, unpublished}
ID 61 = Hisatsuki Seiryuu {BDFalcon, unpublished}
ID 62 = Torahashi Mio {BDFalcon, unpublished}
ID 63 = Eienji Rie {BDFalcon, unpublished}
ID 64 = Hamaguchi Takako {dewelar, unpublished}
ID 65 = Yoshimura Noriko {dewelar, "Noriko"}
ID 66 = Ichini Sanshi {BDFalcon, unpublished}
ID 67 = Kimura Sachiko {Mute, unpublished}
ID 68 = Hitsuragi Yuureiko {BDFalcon, unpublished}
ID 69 = Hanata Haruka {BDFalcon, unpublished}
ID 70 = Shiraki Kotone {BasedMG, "Kotone", in progress}
ID 71 = Kurokawa Sarako {BDFalcon, unpublished}
ID 72 = Kurokawa Mikari {BDFalcon, unpublished}
ID 73 = (Reserved for LorSquirrel)
ID 74 = Yamisaki Eliza {Kevincalanor, Wolfpack}
ID 75 = Yamisaki Alessa {Kevincalanor, Wolfpack}
ID 76 = Nakamura Yuriko {Kevincalanor, Wolfpack}
ID 77 = Harada Himeko {Garage, "Winggirl"}
ID 78 = Fujikawa Sayumi {Garage, "Winggirl"}
ID 79 = Fujikawa Mayumi {Garage, "Winggirl"}
ID 80 = Hashimoto Midori {Ertad, unpublished}
ID 81 = (reserved for Ertad)
ID 82 = (reserved for Ertad)
ID 83 = (reserved for Ertad)
ID 84 = (reserved for Ertad)
ID 85 = (reserved for Ertad)
ID 86 = (reserved for Ertad)
ID 87 = (reserved for Ertad)
ID 88 = (reserved for Ertad)
ID 89 = (reserved for Ertad)
ID 90 = (reserved for Ertad)
ID 91 = (reserved for Ertad)
ID 93 = Shogowa Yuka {RukasuWYZ, "Ijona on'nanoko", probably canceled}
ID 94 = Fujita Suki {RukasuWYZ, "Ijona on'nanoko", probably canceled}
ID 95 = Chihiro Sato {RukasuWYZ, "Ijona on'nanoko", probably canceled}
ID 96 = Shingoza Ayumi {RukasuWYZ, "Ijona on'nanoko", probably canceled}
ID 97 = Sawada Merika {Garage, "Winggirl - Pathways"}
ID 98 = Nagai Shika {Garage, "Winggirl - Pathways"}
ID 99 = Harada Hibiko {Garage, "Winggirl - Pathways"}
ID 100 = Robin Clark {Wowzer_, "Robin"}
ALSO = ? Takuya {Kevincalanor, "Built-off", tachie/profile only}
ID 101 = Miyazaki Kiyoka {Nedras, "First Years", unpublished}
ID 102 = Matsumoto Atsumi {Nedras, "First Years", unpublished}
ID 103 = Kagawa Yasuna {Nedras, "First Years", unpublished}
ID 104 = Azuka Ishikawa {Nedras, "First Years", unpublished}
ID 105 = Hayashito Kaede {ShinigamisApples/KiyokoKaia, unpublished}
ID 106 = Hayashi Kitsune {Garage, "Kitsune"}
ID 107 = Sasaki Riku {Garage, "Nadeshiko"}
ID 108 = Yamaguchi Ayame {Garage, "Nadeshiko"}
ID 109 = Kimura Nanashi {Garage, "Nadeshiko"}
ID 110 = Takahashi Karen {Garage, "Rivalries"}
ID 111 = Inoue Azami {Garage, "Rivalries"}
ID 112 = Yamamoto Hina {Garage, "Crossover", unpublished}
ID 113 = Kojima Daishi {Garage, "Crossover", unpublished}
ID 114 = Hashimoto Chiyo {Garage, "Crossover", unpublished}
ID 121 = Furuya Reika {ScarbucksCoffee, "Reika", unpublished}
ID 122 = Furuya Shunpei {ScarbucksCoffee, "Reika", unpublished}
ID 123 = Shimada Tsukasa {ScarbucksCoffee, "Reika", unpublished}
ID 124 = Shimada Tomo {ScarbucksCoffee, "Reika", unpublished}
ID 130 = Tanaka Grace {mysteriousone3, "Grace"}
(Note: You don't need to care about this list if your story events will not include existing characters, as ID numbers for characters in separate files don't have to be unique)
--> Finally, I've listed the game cheats here. You can use these during story events to test your content:
SHIFT + F5 -- Adds 10 to Looks
SHIFT + F6 -- Adds 10 to Athletics
SHIFT + F7 -- Adds 10 to Personality
SHIFT + F8 -- Adds 10 to Mind
SHIFT + F9 -- Adds 10 to Soul
ALT + F5 -- Adds 1000 to yen
ALT + F6 -- Active speaker's affection decreases by 100
ALT + F7 -- Active speaker's affection increases by 100
ALT + F8 -- Advances the calendar by 1 day
ALT + F9 -- Advances the calendar by 7 days
SHIFT + F6 -- Adds 10 to Athletics
SHIFT + F7 -- Adds 10 to Personality
SHIFT + F8 -- Adds 10 to Mind
SHIFT + F9 -- Adds 10 to Soul
ALT + F5 -- Adds 1000 to yen
ALT + F6 -- Active speaker's affection decreases by 100
ALT + F7 -- Active speaker's affection increases by 100
ALT + F8 -- Advances the calendar by 1 day
ALT + F9 -- Advances the calendar by 7 days
Posts 
Garage
2374
Garage
View playlists
Close97 is perfect ;) ... (inverse ID of Mayumi)
I had some time to think about my new project. ...
She'll have a dateable rival ...but I don't have a name for her yet.
That would neet another ID ... maybe for a Nagai Rika.
(That's just from my list of random generated names ... let's call it her working title ;)
* EDIT: Her name will be Nagai Shika. Another ID for her would be apprechiated ;)
I had some time to think about my new project. ...
She'll have a dateable rival ...
That would neet another ID ... maybe for a Nagai Rika.
(That's just from my list of random generated names ... let's call it her working title ;)
* EDIT: Her name will be Nagai Shika. Another ID for her would be apprechiated ;)
Garage
2374
In case this has drifted past the radar somehow ...
Can I have another ID for "Nagai Shika", please? Preferably 98.
In case it did not drift past the radar - sorry for my nagging.
Can I have another ID for "Nagai Shika", please? Preferably 98.
In case it did not drift past the radar - sorry for my nagging.
Garage
2374
I found a nice bug:
Take this snippet of code (look for the D: 9001 DONE)
Note: That's a conditional jump skipping over a three-way-choice - not a four-way-choice.
If I play this in test mode it takes BRANCH D if the condition is satisfied - as it should do. But - for whatever reason - it somehow ends the STORY before the last line of that BRANCH is played. (In one case that line of text appeared in the chose-a-story page of test mode). If I seperate the conditional jump from the three-way choice, like this
it plays out OK.
*Edit:* Never tested that in-game, only in test mode. Since it is that easy to avoid there's just no point.
Take this snippet of code (look for the D: 9001 DONE)
ID = 97
What's so funny?
ID = 0
Well,--
D: 9001 DONE
A: Tell her the secret.
B: Arrange a meeting with Himeko.
C: Tell her to ask Himeko.
If I play this in test mode it takes BRANCH D if the condition is satisfied - as it should do. But - for whatever reason - it somehow ends the STORY before the last line of that BRANCH is played. (In one case that line of text appeared in the chose-a-story page of test mode). If I seperate the conditional jump from the three-way choice, like this
ID = 97
What's so funny?
D: 9001 DONE
ID = 0
Well,--
A: Tell her the secret.
B: Arrange a meeting with Himeko.
C: Tell her to ask Himeko.
*Edit:* Never tested that in-game, only in test mode. Since it is that easy to avoid there's just no point.
The logic in my head is that it would be written like...
...this. Or, as your alternative points out...
...like so. I'm not sure if having the letter-branch-declaration out of order was causing difficulties, but, this might be an "err on the side of caution" deal.
Another question comes to mind: Has any other content attempted to mix up conditional branches like that? I am aware that there have been stat-checks, and BRANCH As that JUMP into BRANCH Ds, or like scenario. However, I cannot recall stories that do "A: Say a thing", "B: Say a different thing", "C: CONDITION"? I dunno. I'm barely awake, so...
ID = 97
What's so funny?
ID = 0
Well,--
A: 9001 DONE
B: Tell her the secret.
C: Arrange a meeting with Himeko.
D: Tell her to ask Himeko.
...this. Or, as your alternative points out...
ID = 97
What's so funny?
A: 9001 DONE
ID = 0
Well,--
B: Tell her the secret.
C: Arrange a meeting with Himeko.
D: Tell her to ask Himeko.
...like so. I'm not sure if having the letter-branch-declaration out of order was causing difficulties, but, this might be an "err on the side of caution" deal.
Another question comes to mind: Has any other content attempted to mix up conditional branches like that? I am aware that there have been stat-checks, and BRANCH As that JUMP into BRANCH Ds, or like scenario. However, I cannot recall stories that do "A: Say a thing", "B: Say a different thing", "C: CONDITION"? I dunno. I'm barely awake, so...
Garage
2374
author=MarrendHmm - this is from STORY 7611 from WingGirl ... probably one of the most tested stories there since it's part of that twin game:
I'm not sure if having the letter-branch-declaration out of order was causing difficulties, but, this might be an "err on the side of caution" deal.
ID = 0
(One of the twins ... but which one?)
B: Hi, Sayumi!
A: Hi, Mayumi!
C: Hi, ...
author=MarrendI've seen and maybe even written code like A: 7777 DONE followed by B: 79 LIKE ... which seemed to work, as long the parser doesn't puke over a missing STORY or anyother kind of error ...
Another question comes to mind: Has any other content attempted to mix up conditional branches like that? I am aware that there have been stat-checks, and BRANCH As that JUMP into BRANCH Ds, or like scenario. However, I cannot recall stories that do "A: Say a thing", "B: Say a different thing", "C: CONDITION"? I dunno. I'm barely awake, so...
Your example would not make to much sense IMHO. Having the conditional branch after the choice should trigger an error like "wait a minute - where's the BRANCH statement" (I've seen such an error doing something similar.)
OK - I just tried it out.
STORY 8888
PLACE = Front A
ID = 0
A: Say something
B: Say something else
C: 9000 NOT DONE
BRANCH A
Say something
BRANCH B
Say something else
BRANCH C
Hello there.
line 2
last line
... strangely enough - it does not give any error. It behaves exactly like my initial example: if the condition is met, then the choice is skipped - even though it comes AFTER the choice. Again, the last line of this branch is not played (in test mode at least).
Note: this time I used A: B: C: in alphabetic order.
Edit: if there's any text between the C: ... line and BRANCH A there will be an error message saying that the next line after a choice has to be a BRANCH ...
Garage
2374
One technical question ... my current project is an extension to winggirl ...
You will not be able to run it without having that one installed, too.
(You can of course play winggirl just fine without the extension)
It has it's own tachie, profile and of course stories.
Should I put it in seperate directory or should it belong into WingGirl's directory, too?
(My development is in a seperate dir, just to help me keep the tachie organized)
PS: maybe there will be a third part, eventually ... but that's a different story, literally.
You will not be able to run it without having that one installed, too.
(You can of course play winggirl just fine without the extension)
It has it's own tachie, profile and of course stories.
Should I put it in seperate directory or should it belong into WingGirl's directory, too?
(My development is in a seperate dir, just to help me keep the tachie organized)
PS: maybe there will be a third part, eventually ... but that's a different story, literally.
In the case of a content's author extending one's own work, I think it's up to that author as to whither or not said extension is physically part of the original content package/download, or as a separate package/download. The example I'm thinking about is, of course, Uchioniko and the extension that "masako_extra.txt" provides. Your case with Winggirl is probably a more major than what Uchi did, so I can only recommend to use your own best judgement in this regard.
As a point of policy, content extensions, spelling and/or grammar patches, bug-fixes, or what-not, that are not developed/written by the original author are generally considered to need a separate download.
As a point of policy, content extensions, spelling and/or grammar patches, bug-fixes, or what-not, that are not developed/written by the original author are generally considered to need a separate download.
dewelar
627
Okay, so I'm finally getting around to playing with some of the (relatively) recent content, and one thing popped up right off the bat as an issue with Winggirl. In my very first encounter with her, she's talking about Miki using devious motives to win the bet. The problem is that, in this playthrough, the player hasn't heard about the shenanigans with Keika yet. Either this story should be set to happen after the player finds out about that, or there should be some kind of branch where, if the player hasn't found out, he asks Winggirl what she means, and she gives him some kind of ominous hint that something fishy is going on.
Garage
2374
author=dewelarHm. I'll look into this. I thought she is being clear enough about it.
Okay, so I'm finally getting around to playing with some of the (relatively) recent content, and one thing popped up right off the bat as an issue with Winggirl. In my very first encounter with her, she's talking about Miki using devious motives to win the bet. The problem is that, in this playthrough, the player hasn't heard about the shenanigans with Keika yet. Either this story should be set to happen after the player finds out about that, or there should be some kind of branch where, if the player hasn't found out, he asks Winggirl what she means, and she gives him some kind of ominous hint that something fishy is going on.
OK. Maybe be not. She tells him "Let's say your stupid bet with that loudmouthed Miki earned you quite some popularity." and he deduces "Miki is warning all girls about me" but does not say it out loud.
Then she picks up on his thought and says something about an unfair advantage.
She is hinting him, only I probably made that hint way to subtle for a first interaction.
In the "built_in" stories Miki is warning her friends and classmates that Kazuhiko is looking for a girlfriend to win a bet btw. (That's one of the reasons Riho is mad at him from the start). So Himeko - wanting to be his wing girl should warn him. Maybe not right on the introduction, or maybe I should make it clearer and not let her answer to his thought bubble.
My initial intention was: he knows how Miki acts when competiting with him. He does know her for ages, and so if someone tells him she talks to her classmates about the bet he immediately suspects why. But since Himeko and Kazuhiko don't know each other that well yet ... they should have to need more words.
*Edit:* Sorry Miki, maybe I am painting you to negative all the time. In one of Keika's stories she claims that she did not tell anybody but Keika and Riho must have overheard it. I thought she would tell everybody. Yikes. That's not the only time one of my girls claims she "heard about that bet" ...
OK. I can always plead: "please play with clean mode on" ;)
dewelar
627
Hmmm...I think I might see where this is going. In a situation like this, there's a fine line between what the player knows, and what "Kazuhiko" knows. At this point, while Kazuhiko knows his own history with Miki, you can't assume that the person playing Kazuhiko does -- this might be the person's first playthrough, or they might not have played in a while and not remember Miki's tendencies, or they might have even made the mistake of never reading the prologue. I think what's needed is a little more exposition to show why Kazuhiko is making this leap of logic. I'm still not sure it works to place this before any hints that Miki is doing anything devious, but this would at least allow it to make a little more sense in context.
This playthrough also marks my first encounter with Natsume Rika. Boy, howdy, does she need work! Interesting and unique story, but someone needs to be introduced to these little things called capital letters and punctuation...
This playthrough also marks my first encounter with Natsume Rika. Boy, howdy, does she need work! Interesting and unique story, but someone needs to be introduced to these little things called capital letters and punctuation...
Garage
2374
Well, if it's the first time, clean mode can't be off. So the playing person should have had at least some interaction with Miki and maybe Keika before he meets Himeko.
Plus: if it's the very first time ... they really should play through the intro where the relationship between Miki and Kazuhiko is one of the main themes. Especially her being competetive. Somebody who never played through this has no right to complain about missed cues. ;)
Anyway, I think, I'll just make Himeko explain a bit more about Miki telling everybody what's going on and live with the discrepancies.
Himeko has other reasons not to like Miki too much - even if she knows herself that she's not entirely fair towards Miki. She does not want to be fair to Miki.
If you ever play through WingGirl ... there's an important scene at the beach with Himeko. You should ask her about Miki then. She does not detail exactly what happened between them but I think she gives you an idea.
As for Rika (not my project): I really liked her too. Alas, this content has never been finished as is seems. And
Edit: better?
Plus: if it's the very first time ... they really should play through the intro where the relationship between Miki and Kazuhiko is one of the main themes. Especially her being competetive. Somebody who never played through this has no right to complain about missed cues. ;)
Anyway, I think, I'll just make Himeko explain a bit more about Miki telling everybody what's going on and live with the discrepancies.
Himeko has other reasons not to like Miki too much - even if she knows herself that she's not entirely fair towards Miki. She does not want to be fair to Miki.
If you ever play through WingGirl ... there's an important scene at the beach with Himeko. You should ask her about Miki then. She does not detail exactly what happened between them but I think she gives you an idea.
As for Rika (not my project): I really liked her too. Alas, this content has never been finished as is seems. And
it seems getting Rika instead of Midori is supposed to be the bad ending ...
Edit: better?
ID = 0
Nice to meet you, Himeko!
...
So - how come you know me?
ID = 77
LIKE
Let's say your stupid bet with that loudmouthed Miki earned you quite some popularity ...
She is from the same year as me - so I run into her regularly.
...
Maybe you should know that she's talking to her classmates and friends about your competition, warning them about your intentions.
YEAR KNOWN
ID = 0
That ...
(This is just not fair! Miki is telling her side of the story to every girl, so they <b>all</b> will be biased.)
ID = 77
FRIENDLY
I don't like that she's is trying to get an unfair advantage ...
So I figured you deserved at least some warning about it.
...
If this were a commercial game, we might be able to assume that the intro will be watched at least once, and then, probably, never again. They would do that because they want to think their money is worth something. For a free game like this, where the only resource that is consumed is time? Then factor in something can be skipped? I mean, there's probably going to be players that watch it, but, we cannot assume that all players watch it.
*Edit: Erring on the side of "they skipped the intro" seems appropriate either way, actually. So. Winggirl's side-stepping of that issue. It's probably fine. However, I sense the need for Winggril to require the built-in content to be able to "see" various events that Winggirl could run interference against? Or... something like that? I dunno. I know there's extra content when Winggirl is run concurrently with the built-in stuff, and that content might make more sense than the stand-alone content?
*Edit: Erring on the side of "they skipped the intro" seems appropriate either way, actually. So. Winggirl's side-stepping of that issue. It's probably fine. However, I sense the need for Winggril to require the built-in content to be able to "see" various events that Winggirl could run interference against? Or... something like that? I dunno. I know there's extra content when Winggirl is run concurrently with the built-in stuff, and that content might make more sense than the stand-alone content?
Garage
2374
author=MarrendCommercial game or not, personally I tend to watch tutorials / intros exactly once anyway. There might be some content worth watching/reading (I like the rule about "manequins, pillows and blow-up dolls" for example). And I might miss a piece of backstory or a hint how to start playing otherwise.
If this were a commercial game, we might be able to assume that the intro will be watched at least once, and then, probably, never again. They would do that because they want to think their money is worth something. For a free game like this, where the only resource that is consumed is time? Then factor in something can be skipped? I mean, there's probably going to be players that watch it, but, we cannot assume that all players watch it.
But that's just me ...
author=MarrendI tried not to needlessly depend on built-in stuff when writing WingGirl. And I tried not to interfer with/contradict built-in stuff (at least not too much). You should be able to get both Mayumi (for example) and - say - Miki in the same playthrough just fine.
*Edit: Erring on the side of "they skipped the intro" seems appropriate either way, actually. So. Winggirl's side-stepping of that issue. It's probably fine. I know there's extra content when Winggirl is run concurrently with the built-in stuff, and that content might make more sense than the stand-alone content?
author=MarrendThe extra content with "clean mode = off" is basically threefold:
However, I sense the need for Winggril to require the built-in content to be able to "see" various events that Winggirl could run interference against? Or... something like that? I dunno. I know there's extra content when Winggirl is run concurrently with the built-in stuff, and that content might make more sense than the stand-alone content?
- Some reactions from Miki when she learns that Kazuhiko has made friendship with Himeko. (Those two girls really don't like each other)
- Himeko commenting on the built-in girls. Like telling him that Shihoko is hard to get - or telling him that he should know Miki better then she does. ;)
- The last point is a small spoiler: The (undesirable) ending with Himeko as only remaining option checks for builtin's too.
*Edit*: I forgot a nice reaction from Miki when she learnt about Mayumi showing up with a shiner for school.
OK, OK ... and there's a short scene with Tsubasa ...
(because her dad arrested some bad guys and she learnt about it)
WingGirl's story itself is completely independend of the built-in content in any other way. There are references to the bet, because that's the backround story which will be there in clean mode too. There are some short cameos of Takuya and there's mentioning Miki.
dewelar
627
author=Garage
Well, if it's the first time, clean mode can't be off. So the playing person should have had at least some interaction with Miki and maybe Keika before he meets Himeko.
Should have, but not necessarily. In this case, at most I'd seen the first Miki story and no Keika. This, I suppose, is the danger of having a fair of custom characters active: I get a lot of story events up front to the point that even on day 51, I haven't had the chance to get several phone numbers (including Sayumi, who's currently sitting on Heartache 11/12 with no way for me to talk to her.
Incidentally, on my first attempt yesterday, I ran with all the custom content from the one-stop download activated. I didn't even see Miki until about day 14 and hadn't even had the chance to ask for anyone's sign, much less their number. At that point I quit and started pruning.
Plus: if it's the very first time ... they really should play through the intro where the relationship between Miki and Kazuhiko is one of the main themes. Especially her being competetive. Somebody who never played through this has no right to complain about missed cues. ;)
Even if all that's true, I hadn't played the game in months, and probably haven't watched the intro in a couple years. I don't expect it to be suddenly relevant again :D .
If you ever play through WingGirl ... there's an important scene at the beach with Himeko. You should ask her about Miki then. She does not detail exactly what happened between them but I think she gives you an idea.
*nods* I'm running said playthrough now, and am on day 52. I'm looking forward to seeing what her deal with Miki is.
As for Rika (not my project): I really liked her too. Alas, this content has never been finished as is seems. Andit seems getting Rika instead of Midori is supposed to be the bad ending ...
Heh, and I haven't even seen
Midori
Edit:better?ID = 0
Nice to meet you, Himeko!
...
So - how come you know me?
ID = 77
LIKE
Let's say your stupid bet with that loudmouthed Miki earned you quite some popularity ...
She is from the same year as me - so I run into her regularly.
...
Maybe you should know that she's talking to her classmates and friends about your competition, warning them about your intentions.
YEAR KNOWN
ID = 0
That ...
(This is just not fair! Miki is telling her side of the story to every girl, so they <b>all</b> will be biased.)
ID = 77
FRIENDLY
I don't like that she's is trying to get an unfair advantage ...
So I figured you deserved at least some warning about it.
...
Yeah, that's better, I think. Looking at the code for the scene again, my concern was with the use of the phrase "dirty tricks". I don't think I'd consider what Miki does "dirty" -- that would be what Keika's doing.
Anyway, I'm enjoying the story so far. At some point I will run with clean mode on, I suppose (I don't really like doing it, TBH). I've been seeing a fair number of spelling/grammar errors, but I haven't been noting them this time through, since it takes away from the experience :).
Garage
2374
author=dewelarI started playing an "all content active" game today myself. It get's really weird fast. Like having two different fortune tellers on two adjacent days telling different fortunes ;)
This, I suppose, is the danger of having a fair of custom characters active: I get a lot of story events up front to the point that even on day 51, I haven't had the chance to get several phone numbers (including Sayumi, who's currently sitting on Heartache 11/12 with no way for me to talk to her.
Incidentally, on my first attempt yesterday, I ran with all the custom content from the one-stop download activated. I didn't even see Miki until about day 14 and hadn't even had the chance to ask for anyone's sign, much less their number. At that point I quit and started pruning.
Or not meeting Miki for the first two weeks ...
Or running into plenty of girls once and having to remember them weeks and weeks later because you did not meet them in between.
author=dewelarOK. "dirty" is a bit strong. But biasing other girls wouldn't be "fair play" either. (Miki does this at least when introducing Riho in the built-in content).
Yeah, that's better, I think. Looking at the code for the scene again, my concern was with the use of the phrase "dirty tricks". I don't think I'd consider what Miki does "dirty" -- that would be what Keika's doing.
Plus - as is mentioned several times - Himeko and Miki don't happen to like each other that well ...
author=dewelarI'll be much interested in any speelink erors you'd point out to me. Pointing out other errors would be appreciated too.
Anyway, I'm enjoying the story so far. At some point I will run with clean mode on, I suppose (I don't really like doing it, TBH). I've been seeing a fair number of spelling/grammar errors, but I haven't been noting them this time through, since it takes away from the experience :).
dewelar
627
Well, I just had my playthrough crash on day 134. It was actually Seira that caused the crash, as a phone call to her resulted in some sort of nilClass error. I...do not really wish to revisit that content, as it had pretty much no redeeming qualities. I suppose that type of character might float some people's boats, but I found her utterly unenjoyable -- although admittedly I've avoided 21 Ways for similar reasons, she actually didn't bother me beyond the rather paltry amount of content in her file. I did finally meet Midori somewhere in the 110's, by which time I hadn't even seen Rika in about three "months" other than via phone calls -- I don't even think she generated any random events during that time.
I saw the Himeko beach scene mentioned above at around day 120, and then the first part of the story that followed. While I had pretty much predicted the nature of the twist, it's what happens after the reveal that's the really good part. Very nice. I went ahead and looked at the code, and I admit that the doesn't sit well with me, just as the commentary in the file indicates it doesn't seem to sit well with Garage. I don't think the story would lose anything if it was removed. A couple quibbles I do have with the twins are (1) the length of some of the scenes seems oddly short, especially the ones involving , and (2)
Anyway, I will do at least one more playthrough with the Winggirl characters to catch spelling errors before moving on.
I saw the Himeko beach scene mentioned above at around day 120, and then the first part of the story that followed. While I had pretty much predicted the nature of the twist, it's what happens after the reveal that's the really good part. Very nice. I went ahead and looked at the code, and I admit that the
twelve-years-later Himeko pseudo-ending
the science club
does every "date" with Mayumi have to be a sparring session? It was a bit annoying after the first couple times, and since it was pretty much the only contact I had with her for several "weeks" their story kind of got lost in the shuffle for a long while.
Anyway, I will do at least one more playthrough with the Winggirl characters to catch spelling errors before moving on.
Garage
2374
author=dewelar
(1) the length of some of the scenes seems oddly short, especially the ones involving,the science club
I always tought I tended too much to write lengthy scenes ... maybe I'll spice those up a bit.
author=dewelar
and (2)does every "date" with Mayumi have to be a sparring session? It was a bit annoying after the first couple times, and since it was pretty much the only contact I had with her for several "weeks" their story kind of got lost in the shuffle for a long while.
You can take her to normal dates. Especially to the Karaoke, especially AFTER scoring her ending. The sparring is only ment to go on until you trained her.
author=dewelar
Anyway, I will do at least one more playthrough with the Winggirl characters to catch spelling errors before moving on.
This is very nice of you.
A Nil::nilClass error usually means that an object is being defined incorrectly. However, I cannot figure out why that error is being produced. Seira's story-file has no PHONE stories. So, whatever phone conversations players would have with her should default to generic events. Which would lead be to believe that the error is somehow within the code, itself?
*confused*
*confused*
dewelar
627
author=Garageauthor=dewelardoes every "date" with Mayumi have to be a sparring session? It was a bit annoying after the first couple times, and since it was pretty much the only contact I had with her for several "weeks" their story kind of got lost in the shuffle for a long while.You can take her to normal dates. Especially to the Karaoke, especially AFTER scoring her ending. The sparring is only ment to go on until you trained her.
Fair enough. However, my recollection of this isthat I went to the gym with her three times, and got the exact same story all three times. That was quite discouraging.
author=Garageauthor=dewelarThis is very nice of you.
Anyway, I will do at least one more playthrough with the Winggirl characters to catch spelling errors before moving on.
No worries. Sometimes I do get the urge to live up to my title as a developer on this game ;) .
