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
Closeauthor=dewelarI haven't supplied any sound or music ... I was referring to Maayumi's taste in music (if you follow her route to the end you will know ...)author=Garage
Hope Mayumi's music too ;)
Actually, I generally play with sound off now, since my PC isn't the only one in the room and wearing headphones gives me a headache pretty quickly.
author=dewelar
Next up, STORY 7700:
Seems you're in advantage of me.
- Usually, this would be phrased as "Seems you have me at a disadvantage," but "Seems you have an advantage on me" would also work.
She is from the same year as me - so I run into her regularly.
- This doesn't need a dash - just a comma, I think. ;-)
Regarding "in advantage of me": I could've sworn this to be the correct grammar, maybe a bit dated though. Oops. According to wikipedia it should have been "you have the advantage of me"
Dash, smash ;) Yeah I know - nobody likes them dashes just as much as me. I'll smash most of them ... after all those contractions ...
Dash, smash ;) Yeah I know - nobody likes them dashes just as much as me. I'll smash most of them ... after all those contractions ...
Update: Fixed 7700 ... btw: the two dashes at the end of 7701 are goners too!
Garage
2374
Vote request:
"Anyway ... you wanted a ballad - this is one of my favorites."
Dash, comma or colon between ballad and this?
"Anyway ... you wanted a ballad - this is one of my favorites."
Dash, comma or colon between ballad and this?
It could be "Anyway, you wanted a ballad? This is one of my favorites." I suppose it depends on how much of a pause there is supposed to be between "anyway" and "you".
Garage
2374
Talking about "I'm a 2nd year" and stuff ...
Is this OK?
ID = 98
OTHER4
Oh - I'm not looking for my own class. I'm a 2nd year anyway.
YEAR KNOWN
NEUTRAL
I'm searching for Arisawa Hiroaki. He is offering to help us 2nd graders with maths and geography.
OTHER5
I don't want to write "2nd year" in every other sentence of this conversation.
And another thing about contractions: does really anybody use "what're" instead of "what are"? If I would do anything to "What are you " it would be "Whatcha "
Hmm ... contracting "who are" to "who're" is a bit unfortunate, ain't it?
Is this OK?
ID = 98
OTHER4
Oh - I'm not looking for my own class. I'm a 2nd year anyway.
YEAR KNOWN
NEUTRAL
I'm searching for Arisawa Hiroaki. He is offering to help us 2nd graders with maths and geography.
OTHER5
I don't want to write "2nd year" in every other sentence of this conversation.
And another thing about contractions: does really anybody use "what're" instead of "what are"? If I would do anything to "What are you " it would be "Whatcha "
Hmm ... contracting "who are" to "who're" is a bit unfortunate, ain't it?
Garage
2374
Intermediate update to WingGirl.txt and crossover.txt.
Note: currently the first few stories no longer have PRIO = High
Don't be confused if you bump into unplayable girls before you meet Himeko too.
(This change will be better as soon as there are more then just the twins and Himeko available)
This is just a temporary release, if some bug hunter (nods @dewelar) want's to debug the current files and not those released a month or so ago.
- Fixed contractions to my best abilities.
- Removed that unwanted feature.
- Fixed stories up to 7613
Note: currently the first few stories no longer have PRIO = High
Don't be confused if you bump into unplayable girls before you meet Himeko too.
(This change will be better as soon as there are more then just the twins and Himeko available)
This is just a temporary release, if some bug hunter (nods @dewelar) want's to debug the current files and not those released a month or so ago.
To me, the term "2nd grader" would refer to a student in second grade, not a student in their second year of high school. I sincerely doubt you can use something like "He's offering to help us Sophomores with math and geography" as a cross-reference to students in their 2nd year.
Hrm. Yeah, I'm not really sure how to get around that!
*Edit: Though, you could do something like...
...this, to avoid the duplication of terms?
Hrm. Yeah, I'm not really sure how to get around that!
*Edit: Though, you could do something like...
ID = 98
OTHER4
Oh - I'm not looking for my own class.
NEUTRAL
I'm searching for Arisawa Hiroaki. He is offering to help us 2nd years with math and geography.
YEAR KNOWN
...this, to avoid the duplication of terms?
dewelar
627
author=Garage
Regarding "in advantage of me": I could've sworn this to be the correct grammar, maybe a bit dated though. Oops. According to wikipedia it should have been "you have the advantage of me"
Huh. I have literally never heard anyone say that. Then again, it is marked as being a "dated term", so perhaps it's something people used to say?
author=Garage
Vote request:
"Anyway ... you wanted a ballad - this is one of my favorites."
Dash, comma or colon between ballad and this?
Marrend's right that, in colloquial speech, a question mark might be appropriate. A dash would be more likely than a comma, but definitely not a colon -- a semicolon, perhaps, but not a colon.
author=Garage
Talking about "I'm a 2nd year" and stuff ...
I don't want to write "2nd year" in every other sentence of this conversation.
A better alternative would be "juniors", because "2nd-graders" to an English speaker would be interpreted as second grade in elementary school, so a seven- or eight-year-old.
ETA:
author=Marrend
I sincerely doubt you can use something like "He's offering to help us Sophomores with math and geography" as a cross-reference to students in their 2nd year.
Remember that Japanese high schools only cover three years, which are typically approximated in English as freshman-junior-senior.
author=Garage
And another thing about contractions: does really anybody use "what're" instead of "what are"? If I would do anything to "What are you " it would be "Whatcha "
Hmm ... contracting "who are" to "who're" is a bit unfortunate, ain't it?
*nods* I would agree with all of this :) .
author=Garage
This is just a temporary release, if some bug hunter (nods @dewelar) want's to debug the current files and not those released a month or so ago.
Noted :) . I know you changed some things in 7701, but here's a couple other things I noticed:
That's besides the point.
- beside the point
And you seem to be not be quite "my type".
- One too many "be"s :) . You can remove either one and it would still work.
Especially as I am not interested in you for myself - so I won't sabotage your efforts regarding other girls.
- This dash should definitely be a comma :D .
Another global observation: I'm wondering if perhaps "wing girl" should be hyphenated (i.e., "wing-girl"). Instinct tells me it should, but I can be convinced otherwise :).
Garage
2374
author=MarrendID = 98...this, to avoid the duplication of terms?
OTHER4
Oh - I'm not looking for my own class.
NEUTRAL
I'm searching for Arisawa Hiroaki. He is offering to help us 2nd years with math and geography.
YEAR KNOWN
You're right, the easiest way is the best.
Garage
2374
author=dewelarMaybe I'm reading to many English fantasy novels. ;)
Huh. I have literally never heard anyone say that. Then again, it is marked as being a "dated term", so perhaps it's something people used to say?
I read it somewhere sometime ago. It sounded weird enough to remember.
*Edit*: ... Do you know a better way to say "Excuse me, Miss, you seem to know my name, but I don't know yours, so why don't you just fix this?"
author=dewelar
Noted :) . I know you changed some things in 7701, but here's a couple other things I noticed:
That's besides the point.
- beside the point
And you seem to be not be quite "my type".
- One too many "be"s :) . You can remove either one and it would still work.
Especially as I am not interested in you for myself - so I won't sabotage your efforts regarding other girls.
- This dash should definitely be a comma :D .
Fixed the first two ... the third had been fixed in the meantime, anyway.
author=dewelarSearch me ... I'm German so I'd happily chain three or more nouns together without giving it a thought. ;)
Another global observation: I'm wondering if perhaps "wing girl" should be hyphenated (i.e., "wing-girl"). Instinct tells me it should, but I can be convinced otherwise :).
Hm. The term wingman doesn't need a hyphen. But I think it should be either wing-girl or wing girl, not winggirl.
*Edit*: 'Know what: I coined that term and I agree that wing-girl looks better then two seperate words.
dewelar
627
author=Garageauthor=dewelarMaybe I'm reading to many English fantasy novels. ;)
Huh. I have literally never heard anyone say that. Then again, it is marked as being a "dated term", so perhaps it's something people used to say?
I read it somewhere sometime ago. It sounded weird enough to remember.
*Edit*: ... Do you know a better way to say "Excuse me, Miss, you seem to know my name, but I don't know yours, so why don't you just fix this?"
As I mentioned above, the way I've typically heard it phrased is "You have me at a disadvantage." However, one fairly straightforward way to do it would be to have Kazuhiko say, "I'm sorry, should I know you?"
I have downloaded the partial update, so there should be no more correcting of things already corrected. Next up is STORY 7702:
Not about what <b>you</b> have to gain of it.
- "gain from it"
I don't know you good enough to reveal all my secrets to you just yet.
- technically should be "know you well enough" but I hear it often enough this way that it could stand like this
it's your decision, of course. But I think you're making a mistake.
- Missed capital letter at the beginning
To bad. But I have to accept your choice.
- "Too bad". You do like this one, it seems :) .
Garage
2374
author=dewelarIn doubt one should pick the easiest way ...
As I mentioned above, the way I've typically heard it phrased is "You have me at a disadvantage." However, one fairly straightforward way to do it would be to have Kazuhiko say, "I'm sorry, should I know you?"
That would yield:
ID = 0
Sorry. But should I know you?
ID = 77
No. We never met before. My name is <last> <first>.
author=dewelar
Next up is STORY 7702:
Not about what <b>you</b> have to gain of it.
- "gain from it"
I don't know you good enough to reveal all my secrets to you just yet.
- technically should be "know you well enough" but I hear it often enough this way that it could stand like this
it's your decision, of course. But I think you're making a mistake.
- Missed capital letter at the beginning
To bad. But I have to accept your choice.
- "Too bad". You do like this one, it seems :) .
@#2 Oops: I read this scene a hundred times. Allways read it as "well enough".
@#3 Maybe a search&replace victim ...
@#4 Told you this were my favorite mistake.
@#3 Maybe a search&replace victim ...
@#4 Told you this were my favorite mistake.
Garage
2374
And now for something completely different.
Announcement: I'm currently working on a parser/grapher/maybe testool for heartache ...
The base idea is that I want to make it easier (for me) to keep track on which stories lead where. It will at least be able to load all STORY files of a project and understand those CONDITION = funparthere lines. ... Then I should be able to browse to say WingGirl, STORY 7999 and retrace all paths that lead there.
It'll be written in Javascript, the parser is half way through done. (condition parsing is one part that is not yet done)
Two questions:
#1 Are you interested in me publishing the final tool?
#2 If yes: my current version is able to work with local files ... but it would be somewhat easier if it could rely on a php-enabled webserver (for one you can't really search local files with Javascript, you have to use try-and-error, and what's worse: you'll have to name every possible directory to look for them in a config file). How would you feel about setting up an local apache + php installation to use such a tool (you won't have to give others access to the website. http://localhost/ would be enough for using it).
Announcement: I'm currently working on a parser/grapher/maybe testool for heartache ...
The base idea is that I want to make it easier (for me) to keep track on which stories lead where. It will at least be able to load all STORY files of a project and understand those CONDITION = funparthere lines. ... Then I should be able to browse to say WingGirl, STORY 7999 and retrace all paths that lead there.
It'll be written in Javascript, the parser is half way through done. (condition parsing is one part that is not yet done)
Two questions:
#1 Are you interested in me publishing the final tool?
#2 If yes: my current version is able to work with local files ... but it would be somewhat easier if it could rely on a php-enabled webserver (for one you can't really search local files with Javascript, you have to use try-and-error, and what's worse: you'll have to name every possible directory to look for them in a config file). How would you feel about setting up an local apache + php installation to use such a tool (you won't have to give others access to the website. http://localhost/ would be enough for using it).
I feel like there should be some kind of method that can be used so that potential authors/users wouldn't need to specify every single directory that exists, or could potentially exist, in the base Heartache/Story directory. However, if my limited experience with Tsukihime's resource-checker for VX Ace is any indication, I could be dead wrong!
Garage
2374
author=MarrendIn JavaScript? No. Well using HTLM5 plus Javascript you could use a file-input tag (like the browse button in the upload dialog of your locker) ... maybe the user could select one or more directories instead of files. But even that would feel cludgy.
I feel like there should be some kind of method that can be used so that potential authors/users wouldn't need to specify every single directory that exists, or could potentially exist, in the base Heartache/Story directory. However, if my limited experience with Tsukihime's resource-checker for VX Ace is any indication, I could be dead wrong!
In PHP you'd just use either readdir () or better yet scandir () and would be basically done.
What Javascript can do to local files is deliberatly kept limited. Because the normal use involves downloading the script from some webpage and running it locally. So the computer *running* the script should not be too trusting towards the person who put it on the *remote* machine where it was downloaded from.
If the script resides on your local computer it has at least limited access to the files in the same directory (including subdirectories). But if it doesn't know the exact location of a file it has to guess ... and if it doesn't know the directory-structure ... you're just out of luck.
In a nutshell: without a webserver to help my script out there'd have to be a config file naming each and every directory that could contain stories, profiles, tachie ...
*Edit:* to make things more ... interesting: stuff like
A: 87191 DONE IN dunno.txt
is probably either a CONDITIONal jump to BRANCH A if there really is a dunno.txt containing a STORY 87191 ... or it's regarded to be part of a choice. (Scroll back a few pages to the discussion about an example in "Ijona on'nanoko" where it turned out that a CONDITION containing a wrong ID is enough to turn A: 9 LIKE into a choice instead of a conditonal jump).
Garage
2374
@Marrend: found a cute little bug in Uchioniko\uchioniko_profile.txt, line 695:
The fun part is: the Game loads this profile without a complaint.
(Found in the "official downloads" version of your Uchioniko)
CUSOTM 91 =
The fun part is: the Game loads this profile without a complaint.
(Found in the "official downloads" version of your Uchioniko)
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?
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?
Garage
2374
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 ;)
Yeah, thanks for pointing that out. Both content have been updated on my end. The update on this end will probably occur with the next update of the ZIP file, slated for... December, I think?
Side note: Darigaaz, the content for Emiko is almost two years old now, and Uchioniko's reached 5 years old.
*Edit: Man, sometimes I feel so OLD. Not as old as compared to some that have been around the scene for literal decades, but still.
Side note: Darigaaz, the content for Emiko is almost two years old now, and Uchioniko's reached 5 years old.
*Edit: Man, sometimes I feel so OLD. Not as old as compared to some that have been around the scene for literal decades, but still.
Garage
2374
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)
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!
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!
