Full Games List
Featured Games
New Games
Reviews
Media
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
Profile
Locker
Play ListsGARAGE'S PROFILE
Close
Search
Filter
All
User Statuses
Content creation (technical)
If you don't mind, I'd like to reserve the following slots for my next project:
ID 77 = Harada Himeko
ID 78 = Fujikawa Sayumi
ID 79 = Fujikawa Mayumi
(All names are have been randomly generated by repeately playing "generic", unnamed chars and noting down their names. I then chose among those which sounded "good" for me ;) )
ID 77 = Harada Himeko
ID 78 = Fujikawa Sayumi
ID 79 = Fujikawa Mayumi
(All names are have been randomly generated by repeately playing "generic", unnamed chars and noting down their names. I then chose among those which sounded "good" for me ;) )
Content creation (artistic)
Here is an update for mutliending and here the corresponding version of cheatbot.
Main change is that I implemented bug preventing alternative endings for the case where you score a double-girl-ending and don't have any ohter options.
The easiest solution has been to provide at least one alternative single-girl-ending - I opted to provide one ending for each girl in any open double-girl-finale.
Cheatbot is focused on debuging the endgame ... since that was MY focus for the last few days.
Aside of this, I fixed about three million speelling misdages and grammar erors.
(And rephrased a few sentences).
EDIT (2016-03-19): Important bugfix. Please redownload the .ZIP.
(Or change the JUMP 3517 in STORY 3517 to JUMP 3518)
Main change is that I implemented bug preventing alternative endings for the case where you score a double-girl-ending and don't have any ohter options.
The easiest solution has been to provide at least one alternative single-girl-ending - I opted to provide one ending for each girl in any open double-girl-finale.
Cheatbot is focused on debuging the endgame ... since that was MY focus for the last few days.
Aside of this, I fixed about three million speelling misdages and grammar erors.
(And rephrased a few sentences).
Riho / Shihoko is a bit special since you would normally need to complete Riho's solo route anyways just to start my extention to this sidepath.
The other STORYs are designed to show alternative developments in the lives of Shihoko, Riho or Tsubasa if <player> fails their main routes and they somehow still fall for them.
Other then my STORY for Riho these should clearly seem less desirable then finishing their built-in routes (<player> failed them!). Tsubasa or Shihoko somehow finds her own way. And she wants to see <player> again - but the final outcome is less then certain.
Riho's alternative to Riho/Tsubasa is about a Riho who fails her great dream of finishing a very reknown university. But the result is anything but a failed life.
The other STORYs are designed to show alternative developments in the lives of Shihoko, Riho or Tsubasa if <player> fails their main routes and they somehow still fall for them.
Other then my STORY for Riho these should clearly seem less desirable then finishing their built-in routes (<player> failed them!). Tsubasa or Shihoko somehow finds her own way. And she wants to see <player> again - but the final outcome is less then certain.
Riho's alternative to Riho/Tsubasa is about a Riho who fails her great dream of finishing a very reknown university. But the result is anything but a failed life.
EDIT (2016-03-19): Important bugfix. Please redownload the .ZIP.
(Or change the JUMP 3517 in STORY 3517 to JUMP 3518)
Content creation (technical)
Currently I'm planing to use about three slots. There will be one main route for one of them and one maybe two alternatives which I regard as less-then-desirable choices (read: he can get her, but <player> should be well aware that he will NOT be HER perfect option).
I am not too sure that my story will really work out as planed.
For example it might happen that build up to much sympathy for "the wrong one" while "Ms. Right" ends up too ... flat? (is this the right word for a not-too-deep-developed character?)
I am not too sure that my story will really work out as planed.
For example it might happen that build up to much sympathy for "the wrong one" while "Ms. Right" ends up too ... flat? (is this the right word for a not-too-deep-developed character?)
Content creation (technical)
author=MarrendYour memory is working ;)author=GarageOne could probably do a custom ending this way. Though, if memory serves me right, the event preceding the phone call highly suggests that the phone call happens. From that phone call, maybe one can have the characters meet up again after however-long-it's-been? Sorry, my memory's more than a bit fuzzy here!
First: even in an normal ENDING you don't have to stick to that phone call routine. You can have BRANCHES and have tachies SHOW up as in any other STORY.
But: you can just start with a phone call, and then something else happens.
Think of Junko's ending - this is implemented as a CUSTOM ENDING ... but I am pretty sure you could emulate it just as well with a normal one.
(Another example will be in my next version of my current project).
author=MarrendGuess what was the second thing I tried after discovering that STATE = LIKE works ...author=GarageHuh. That's an interesting technique. However, my guess is that "Other" slots could not be used this way, as those are not states
Second: if you ever want to change the face of the girl in that last "heart" picture at the very end ... just use "STATE = <whatever>" ...
So ... if you really want to, you can even create a heart with a "DISLIKE" tachie in the middle ...listed under the "STATE" line, in accordance to Mr Help Fileper say.
STATE = OTHER1 just yeilds an error message telling me that "OTHER1" is not a "state".
Not very surprising since "STATE = " is related to the affection system ...
Nonetheless, there are some uses for my discovery: an heart showing a girl in a STATE other then LOVE or LOVESICK (for example: I'm planing use this for a not-perfectly-happy ending ...).
Another way of using this would be if you can make 100% sure to avoid a given state (probably DISLIKE or maybe LOVESICK) ... for example if she has ENCOUNTERS OFF (and no PHONE) or if you lock her after reaching LOVE anyways.
(Or at the moment the drops below UNFRIENDLY). A nice application would be using an somewhat aged version of her with a differnt outfit.
Speaking of projects ... whenever I get this multiending stuff where I want it to be I would like to try some content with some own characters.
What is the current policy about IDs? (I am not planing to have them interact with existing content, so I could probably number them 1,2,3 anyways - but if you have some IDs that I should preferably use ...)
Content creation (technical)
Two nice bits of information about ENDING-Stories:
First: even in an normal ENDING you don't have to stick to that phone call routine. You can have BRANCHES and have tachies SHOW up as in any other STORY.
Second: if you ever want to change the face of the girl in that last "heart" picture at the very end ... just use "STATE = <whatever>" ...
So ... if you really want to, you can even create a heart with a "DISLIKE" tachie in the middle ...
First: even in an normal ENDING you don't have to stick to that phone call routine. You can have BRANCHES and have tachies SHOW up as in any other STORY.
Second: if you ever want to change the face of the girl in that last "heart" picture at the very end ... just use "STATE = <whatever>" ...
So ... if you really want to, you can even create a heart with a "DISLIKE" tachie in the middle ...
Content creation (technical)
author=Marrend
I'm tempted to say "no" to that question, though I'm not 100% sure. Like, I know Masako's "going away" event set ENCOUNTERS OFF and PHONE UNKNOWN. However, I'm pretty sure her name is still on the phone-list!
Masako stayed on the phone-list. Hmm ... Hinami? ... I am pretty sure she stayed there too.
The only thing that happens with PHONE UNKNOWN is: you can't call them - luckily the heartache counter gets frozen too (iff ENCOUNTERS are OFF also).
Other content just inserted PHONE STORYs which emulated "does not pick up" or "the number you have dialed is currently unavailable" (Robin does this. And wolfpack if I remember correctly, I used it in Riho / Tsubasa for one night if the player fails to show for a very important "date")
In these cases the girls obviously stayed on the list ...
... short version: i can't see a way to get a girl off that list no matter what happens to her in her stories.
Content creation (artistic)
I abandoned the idea with that hidden fake emulated two person "character".
This just doesn't work out too well. It feels kludgy. I would have to dance around that 151 dilemma (which I am not too sure whether it would really work).
And things would just get crazy if some other content used a DAY 100 Bedroom STORY for something else.
Currently I am planing to offer alternative single girl ENDINGs when ever he earns a "double feature" but did not score the normal ENDINGs for the girls involved.
This should feel much more natural. And it might offer an opportunity to tell some interesting story variations (What would become of Riho's plans if <player> did not help her thru? Especially when he played her against her sister and decided for her in the very last moment?)
This just doesn't work out too well. It feels kludgy. I would have to dance around that 151 dilemma (which I am not too sure whether it would really work).
And things would just get crazy if some other content used a DAY 100 Bedroom STORY for something else.
Currently I am planing to offer alternative single girl ENDINGs when ever he earns a "double feature" but did not score the normal ENDINGs for the girls involved.
This should feel much more natural. And it might offer an opportunity to tell some interesting story variations (What would become of Riho's plans if <player> did not help her thru? Especially when he played her against her sister and decided for her in the very last moment?)
Content creation (technical)
Em. I just noticed that there is no NAME UNKOWN or the like ... is there any way to hide a girl from the "phone list" once you were introduced to her and had her name?
Like when she moved away or died or whatever. (Or in my case is not really a "girl" but a placeholder).
Like when she moved away or died or whatever. (Or in my case is not really a "girl" but a placeholder).
Content creation (artistic)
This here seems to work - mostly at least.
Even if I use the "ring of sleep" by the way.
But there seem to be spurious events whithout any girls in them (like you normally only get if you have CLEAN MODE ON and no other STORY that can play in this mode). I am not sure about this ... I'll have to run additional tests.
Main problem that remains: there can't be more then one Bedroom STORY on DAY 101 - so this will interfer with any other route using the same trick, that's no issue for my own stuff, since I can integrate the different DAY 101 hacks into one ...
The other issue is of course, that there seems no way to tell whether 151 mode is on or not. Oh, well. Guess I can hide the name on DAY 101 Front A (which should not trigger in 151 mode off) and reenable it on DAY 151 Bedroom.
Even if I use the "ring of sleep" by the way.
But there seem to be spurious events whithout any girls in them (like you normally only get if you have CLEAN MODE ON and no other STORY that can play in this mode). I am not sure about this ... I'll have to run additional tests.
# INTRODUCE Story - to make the ending available.
STORY 3434
CONDITION = 3406 DONE
CONDITION = DAY 100
PLACE = Bedroom
INTRODUCE = 3434
PRIORITY = High
ID = 3434
ID = 0
There is a message on my phone from Miki:
"Today is the moment of truth!"
STORY 3407
CONDITION = 3406 DONE
CONDITION = 3 LOVE
CONDITION = 4 LOVE
ENDING = 3434
#ENDING = 3,4
Main problem that remains: there can't be more then one Bedroom STORY on DAY 101 - so this will interfer with any other route using the same trick, that's no issue for my own stuff, since I can integrate the different DAY 101 hacks into one ...
The other issue is of course, that there seems no way to tell whether 151 mode is on or not. Oh, well. Guess I can hide the name on DAY 101 Front A (which should not trigger in 151 mode off) and reenable it on DAY 151 Bedroom.
Games - Tester
Games - Other
