• 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:
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

Posts

author=Marrend
There's also the adage "If it ain't broke, don't fix it." I don't know that it's "broken" per say, but there is a chance that it isn't!

One I'm willing to take, apparently.


Well said:)
So, I announced her a while ago, but I would like to reserve ID 54 for Hitsuragi Yuureiko, and ID 68 for the unannounced Hanata Haruka.

The ID's I choose get sandwiched anyways, so why not just spread them around?
Marrend
Guardian of the Description Thread
21806
author=BDFalcon
So, I announced her a while ago, but I would like to reserve ID 54 for Hitsuragi Yuureiko, and ID 68 for the unannounced Hanata Haruka.

The ID's I choose get sandwiched anyways, so why not just spread them around?


Oh. Right. That post. Let's see. How about we slide those two into 54/55? Or, if you want them closer to your other ones, 68/69?
Marrend
Guardian of the Description Thread
21806
I think I have an idea as to what's happening with Joruri's "black screen" events. It has to do with her "common event" tech. See, her REPEATABLEs that have a defined location jump to a REPEATABLE event that has no defined location. That event only requires that one of the REPEATABLEs that have a defined location is DONE. So, that's why it's possible to get Joruri events in school: Getting any one of her REPEATABLEs allow the "common event" processing to occur in school.

If this assumption is true, I have no clue how to go about getting this to work the way it was intended to. Setting "PLACE = City" to the "common event" will push it outside of school-phase (Which is good!), but you can still get it during any city event (Which is bad!).
author=Marrend
I think I have an idea as to what's happening with Joruri's "black screen" events. It has to do with her "common event" tech. See, her REPEATABLEs that have a defined location jump to a REPEATABLE event that has no defined location. That event only requires that one of the REPEATABLEs that have a defined location is DONE. So, that's why it's possible to get Joruri events in school: Getting any one of her REPEATABLEs allow the "common event" processing to occur in school.

If this assumption is true, I have no clue how to go about getting this to work the way it was intended to. Setting "PLACE = City" to the "common event" will push it outside of school-phase (Which is good!), but you can still get it during any city event (Which is bad!).


I've tried to push over my usual comprehension problems and look it up.

Your assumptions are correct, once you've met the conditions to the event 15, it will trigger forever and anywhere, as it have the repeatable switch on, and no place. Use a "PLACE = City" would help pushing it away the school phase and preventing black screens, as it'll use the location you went.

If the Story 15 must only be triggered on the previously selected places, the only solution I can see for now is a rather low-tech copy-pasting the 15 into the repeatables with location (STORY 4, 6, 8, 10, 12, 14), turn off the REPEATABLE at the 15, and finish placing "CONDITION = 15 DONE" in both of them. {As 15 is accesed by jump}
Marrend
Guardian of the Description Thread
21806
author=Kevincalanor
If the Story 15 must only be triggered on the previously selected places, the only solution I can see for now is a rather low-tech copy-pasting the 15 into the repeatables with location (STORY 4, 6, 8, 10, 12, 14), turn off the REPEATABLE at the 15, and finish placing "CONDITION = 15 DONE" in both of them. {As 15 is accesed by jump}


If the contents of the "common event" are copy-pasted into the location-based STORYs, then... I'm not seeing the point of JUMPing to the "common event", or having anything there at all? Am I missing something? Probably.

I vaguely recall Dozen saying he had an idea about this back in the day, but I do not remember what his idea actually was. Though, I could be forgetting everything something, and attempting to look this up would probably cause three-and-a-half headaches.
author=Marrend
If the contents of the "common event" are copy-pasted into the location-based STORYs, then... I'm not seeing the point of JUMPing to the "common event", or having anything there at all? Am I missing something? Probably.

I vaguely recall Dozen saying he had an idea about this back in the day, but I do not remember what his idea actually was. Though, I could be forgetting everything something, and attempting to look this up would probably cause three-and-a-half headaches.


The events 3, 5, 7, 9, 11 and 13 tagged with locations JUMP to the "common event", they use the same location of the 4, 6, 8... but have High priority and aren't repeatable.
Keep the event 15 there would prevent even more copy-pasting, however those events were used as condition to start the "common event" before, so maybe you can just wipeout them. Hope I didn't missed anything. I always do... :p

As a new weird idea, if you keep the setting, and change the common event condition for something like "2783 DONE"?
2783 will never happen, so the Conditions will never be met and the common event will only appear by the previous JUMPs, eliminating the black screens. It's more high-tech than the copy-paste :3
*Yeah you'll have to create a story 2783 to prevent loading from crashing, just let him alone with a self condition. The number 2783 is random and must be ignored Certain conditions may apply all right reserved.
Marrend
Guardian of the Description Thread
21806
If I JUMP to a STORY with an "impossible condition" like that example...

Yeah, I think that could work! That's similar to how "switches" work, at any rate!

*Edit: 50 days with Joruri's content, with no black screens in sight. That sounds pretty solid to me! Though, I think I might have said that before?
I actually have a question about Joruri. I've gotten to the point where I see Masako after school and she tells me that one of her close friends from before is in town on Personal Business, and that she can almost always be found in the Children's Park, but whenever I go she's not there, and it's really annoying me. Can one of you help with this?
Marrend
Guardian of the Description Thread
21806
Have you meet Watanabe Aoi? If not, if memory serves, her introduction is a relatively early event in Watanabe Junko's route. If you have meet her, crap, I have to look at that again.
Marrend
Guardian of the Description Thread
21806
ID listing updated! Please let us know if we need to make any corrections.
Man my ID's are all over the place. =.=; I would like to request ID 66 for Ichini Sanshi, who's neutral tachie should be uploaded to the artistic thread sometime tomorrow. (if you get the name, know that it is as such for perfectly story relevent reasons ^.^;)
A note to people who use the PICTURE command (especially Kevincalanor):
Be absolutely sure to use the 'PICTURE = None' command before the end of any story that uses the PICTURE command. If you don't, the picture will remain on the screen in other events and even on the school board.

Kevin, I'll just let you know that I was looking at Keika standing in front of two people hugging in the trees because of this.
Marrend
Guardian of the Description Thread
21806
Was I just imagining things, or did you not make a post about getting Shoko's fast-food scene, only you were at the fishing place during a rainstorm?

Never mind. I'll just have to look out for that if I'm going to be having scenes of Emiko with that station-at-night graphic that's in her tachie directory.
Another lurking scout... oh.

author=Mute
A note to people who use the PICTURE command (especially Kevincalanor):
Be absolutely sure to use the 'PICTURE = None' command before the end of any story that uses the PICTURE command. If you don't, the picture will remain on the screen in other events and even on the school board.

Kevin, I'll just let you know that I was looking at Keika standing in front of two people hugging in the trees because of this.

I always took the train to go to a greenhouse that was on the school this whole time? That's embarrassing.
Eliza wouldn't be happy to be spotted at that scene too...

Kidding aside, I indeed love to use this command, as it helps with my writting issues, on the bright side of the things this the penultimate time I use this command on Yami's route, so it must be the only time I forgot to reset the command. I'll check it ASAP. :p

On a less to not important note.
If anyone is wondering why my LMG speed of posting transformed on a sniper like timing, I'm engaged, and winning, a lvl. race on a MMO :p
Yeah, I shouldn't be doing this being so close to finish up my C.C., I just can't help myself with slacking at 90's%, happens with everything I do...
And darn, can you say no to a berserker this cute? Also it's unhealthy to say it to someone with a axe that big.

"Get the pigs back to safety instead of chopping them? No fun at all."

However, I will not drop the project and I'm still tracking the feedback, and I'm vacation now, I should have time to do both. ^^
(So you don't to tell any of this to Dozen, 'kay? :p)


EDIT: Err... I checked the last events... the Last event is also lacking the "PICTURE = NONE", please place it near the PHONE KNOWN command to avoid being stuck at the school entrance forever :p
I have a few more things (tachies, pictures, and stuff), that I want to place on the next patch. Also due the folder name and txt changes, it will most likely wreck up saves.
PRIORITY = Absolute

As long as the conditions are fulfilled and the player is at the proper place to witness this event, the event is 100% likely to happen. It'd be useful for events that are meant to happen on a specific day, but it also opens up griefing possibilities for writers.

That's nothing a good check of each story before uploaded can't fix, though.
Marrend
Guardian of the Description Thread
21806
Uhhhh, doesn't PRIORITY = HIGH already do this? I dunno. To my knowledge, I've never failed to hit a PRIORITY = HIGH event, so...
So I'm just gonna go ahead and re-request ID 66 for Ichini Sanshi, and newly request ID 63 for Eienji Rie. My ID's. Just all over the place.
I'm going to be updating the game to fix all bugs and issues reported since last release. Marrend, could you (or anyone else willing to) compile a list of all issues that need addressing? Since I haven't been keeping up.