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)
author=MarrendWithout CONTINUE you have no way to schedule a "real date" - in the sense of game logic.
It's technically possible to do, but it would certainly be more limited. My train-of-thought involves using BRANCHes for "Just Chat" and "Ask for a date", and do follow-up BRANCHes in regards to "Ask for a date". If "Ask for a date" was successful (you should be able to use ID LIKE, or like CONDITION for this check), you could JUMP into a regular STORY where the player character has a thought-bubble about where to go, and then do a choice of up to four locations, probably having at least one "good" location, and one "bad" location on the list. It's possible the actual choice made might be irrelevant, though, as the various DATING stories should be able to use CONTINUE. This is all very largely speculation on my part, though.
You could make up a PHONE STORY where player and his girl decide to go to xyz which looks much like a regular one and matching City-STORY which plays much like a DATING.
This would still not be regarded as a regular date by game logic. No checking how long its been till the last time he dated her, no <3 in the location list, no factoring in of a confidence boost that might have been scored by the player (at least not in to the calculation whether she say yes or no). And you would have to emulate stuff "where will we meet" and "why didn't you show up" on your own. Which is entirely solvable - at least if you have a limited number of simulated dates.
It gets complicated fast if you want this to be repeatable, or if you want to allow different locations.
By the way: yes, a DATING story is able to use CONTINUE (regardless of branch or not). And you can use PLACE = City, DATING = id_of_girl for a generic customization but that's a differnt beast ;)
PS: for my current purpose I just suspend the possibillity of dating Mayumi while she and the player are in training mode ... so "Ask for date" is replaced by something like "Schedule training" and "Just chat" by a short "(we chatted for a while)" + AFFECTION UP. This phase should not be lasting longer the a few weeks anyway.
Content creation (technical)
author=MarrendOK: So it wasn't just me ... I thought I remembered Mr. Helpfile mentioning PHONE-Stories in the context of CONTINUE.
I am aware that Mr. Help File mentions that PHONE events can use CONTINUE to allow for a generic phone event to occur, both when talking about Phone events and when talking about the CONTINUE command. I am also aware that, outside of this command, it is utterly impossible for authors to emulate the proceedings of generic phone events. Particularly in respect to setting up where the date occurs in, much less anything else you mention. Maybe further investigation (on my side) is in order ;)
However, the error message that you're getting (or, at least, the one that I'm seeing) specifies that CONTINUE can only be used in a "City" or "Dating" STORY. Which tells me that the PHONE-story functionality for CONTINUE is brokenor never worked to begin with, because nobody ever tried it until now
*Edit: even a 5-liner STORY without anything fancy (no branches, a minimum 2-line header, an ID= line, a bit of text and CONTINUE) triggers the warning.
And Mr. Helpfile simply LIES about this!
author=MarrendHaving to have to work with what is there is another way to have fun ;)
*Edit: I'm sorry I can't be of more help. There are many things that authors can do, but, we are still limited by the code-base. We are also learning how much of that code-base is even usable, given the recent errors in regards to multiple-character-endings, and now this.
By the way 2.5 is the correct and final version, right? Or are there some last minute patches that I missed because I downloaded from the wrong location?
Content creation (technical)
author=MarrendThe char is a plot device ... her identity is ment to come as a surprise to the "player".author=GarageLemme think out loud for a bit. A new character that has about five lines of text that also has a tachie. I sorta have to question why bother with the tachie, and just have that character use ID=<insert_name_here>? Unless the intent was to flesh out that character elsewhere, as it's "just" a cameo in the one content?
A short cameo (one scene - the char in question has a tachie but only about 5 lines of text) doesn't deserve an official ID, does it?
Currently I have no intention of making her playable, and she would not fit as a playable char in my current content.
author=MarrendYeah. But I am already using faked "Just Chat"-options in other places. I do not want to emulate the whole PHONE-Call and random ENCOUNTER stuff more then I have too.author=Garage
I checked - this issues the same warning.
That's most peculiar. I vaguely remember getting an error with CONTINUE in the context of a BRANCH (Darigaaz, did I ever report that?), but, figured it would work with a "normal" STORY. I think the best thing you can do in that BRANCH is to go something like...ID = 0
(We continued chatting for a bit.)
ID = 79
AFFECTION UP
...this?
Plus: it is impossible to perfectly emulate this - I cannot have a customized PHONE-Call schedule a date (in the sense of a DATING-Story), AFFECTION UP uses a fixed value instead of looking at player's stat.
Not to mention that a random phone call can fail. A selfwriten PHONE-Story always counts as a success. Even if you fake "She doesn't pick up" - her heartache gets still reset. Just ask the author of Robin ... (great character, by the way!)
For example: (minor spoiler)
Himeko will not accept dates. To implement this I'll be ending up having REPEATABLE PRIO-High PHONE-Stories for every state from NEUTRAL up to LIKE for her.
Content creation (technical)
author=MarrendI checked - this issues the same warning.
I'm not really sure about this, but, it might need a new STORY to work. Such as...
...JUMP 7910
STORY 7910
CONDITION = 7909 DONE
PHONE = 79
CONTINUE
...this?
*Edit: Screwy code-tag!
*Edit: yup, screw that screwy tag!
Content creation (technical)
Speaking of cameos I found a nice hack.
Suppose you want Miki for a short appearance in a route that's supposed to be played with Clean Mode on ...
This is how you can do this:
The game does check for unintroduced chars in a STORY ... but it does not check the JUMPs in a STORY whether they end up on a STORY with unintroduced chars.
Suppose you want Miki for a short appearance in a route that's supposed to be played with Clean Mode on ...
This is how you can do this:
my_profile.txt, game_profiles.txt
STORY 11111
#CONDITION = whatever
PLACE = Front A
PRIORITY = High
ID = 0
It's good that Miki did not see this.
JUMP 11112
STORY 11112
CONDITION = 11112 DONE
ID = 1
SHOW CENTER
That I did not see <i>what</i>?
The game does check for unintroduced chars in a STORY ... but it does not check the JUMPs in a STORY whether they end up on a STORY with unintroduced chars.
Content creation (technical)
A short cameo (one scene - the char in question has a tachie but only about 5 lines of text) doesn't deserve an official ID, does it?
Content creation (artistic)
Does anyone have a background PIC of a barber shop / hairstylist I could use in my content? The two collections posted by Kevincalanor don't.
And maybe a dark side road with an ATM ...
And maybe a dark side road with an ATM ...
Content creation (technical)
author=Marrend
I'm not really sure about this, but, it might need a new STORY to work. Such as...
...
author=MarrendI doubt that adding another PHONE story to jump to will change things ... but I'll try.
...this?
*Edit: Screwy code-tag!
Content creation (technical)
There is no way to use CONTINUE in a PHONE-Story, is there?
Like:
That will issue a warning.
Like:
STORY 7909
CONDITION = 7908 DONE
CONDITION = 7911 NOT DONE
CONDITION = NOT Saturday
PHONE = 79
PRIORITY = High
REPEATABLE = Yes
ID = 0
Am I ready for a fight?
A: Schedule training
B: Not yet.
BRANCH A
So ... You ready for some training?
ID = 79
Sure!
ID = 0
Let's meet a the gym!
JUMP 7911
BRANCH B
CONTINUE
That will issue a warning.
Content creation (artistic)
author=MarrendThat would be greatly appreciated - as long as you do not expect too much.
@Garage: The tachie is definitely better! I hope to look into that content in more detail maybe next week.
I posted it to find out about problems with my tachie in advance (mission accomplished on that part, thanks to you) - and because I wanted someone else to test my "guess-the-twin" game - you will know what that is supposed to mean pretty soon (around the third or fourth encounter with them).
Games - Tester
Games - Other
