Ren'Py's Public Image

[PyTom]

DSE == Dating Sim Engine, an engine that supports stats-based scheduling.

I'm not sure how many of the Blade panels I will attend (I get the impression I'd be unwelcome). But I was invited by Shira-Oka/Okashi (they're good guys!), and their panel should be mentioning a new Ren'Py game.

We'll see how brave I am when I get down their.

(Does anyone have any idea how to issue press releases?)

[lordcloudx]

actually, I think that everyone is just trying to be technical about the demo app.

I'm as untechnical (hehe I coined a phrase... I think) as you can get and so are a lot of us here I believe. Check out the completed games in the ren'ai archives

dse... that would be the dating sim engine in the folder that ships with ren'py?

whoops looks like PyTom beat me to it.

Issuing a press release would be... any way you want? (I'm no help, I know.)

[ShiraiJunichi]

DSE stands for Dating Simulation Engine.

I'm getting kind of confused now... are we working on a demo that show's ren'py's power, or a tutorial that shows how to do things? I think it may be possible to include both, though I think it should have some kind of logical division. Kind of like how the image dissolve tutorial first shows everything, then explains it later.
Like I said before, first lure them in with Ren'Py's amazing capability, then hook them with ease of use.

You could even include a section on converting an already existing work- such as a web comic- into a game.

As far as a game template goes, I think it's a good idea, but shouldn't comprise the demo, as that will limit it too much. It could be an extra- with it's own executable.

[DaFool]

PyTom, since the Blade Engine panel is earlier on Friday, attend it without pinning on your 'Ask Me about Ren'py' badge.

Once that's over, then put on your badge. It'll be too late for them ^_^.

I'm not sure who else here would be attending Otakon, but hopefully some Ren'py loyalists would be able to provide feedback

Difference between demo game and tutorial...just do it the Blade Engine way.

Demo stands by itself. Tutorial is an html that quotes from the script of the Demo. Simple as that. One Demo + Tutorial per major feature, or several simple features.

[PyTom]

To be honest, I'm way too close to Ren'Py to know the right split into demos, tutorials, and the like. So I will leave it up to others to figure out the right way to do things.

(I probably won't make it down to Baltimore in time for the Friday Blade workshop, anyway... Is anyone else going to be there? I would like intel, if possible.)

[Kikered]

Going along with the "dream" idea for the demo, it might be interesting if each of the vignettes had different "variations" of Eileen in them - similar enough to be faintly recognizable but different enough to seem like a separate character at first glance. Then they could be all be tied together at the end with the "actual" Eileen or something to that effect.

[ShiraiJunichi]

To be honest, I'm way too close to Ren'Py to know the right split into demos, tutorials, and the like. So I will leave it up to others to figure out the right way to do things.

I think this whole movement lacks direction. We can all talk about the wonderful things we could do- but unless there's someone there to make decisions, and start taking action, then talk will remain just that- only talk. If Py'Tom feels too close to the issue to know which direction to take, I think he should appoint someone to be in charge. That person can then take all input from the community, make final decisions, and delegate responsibilities to other forum members.

[PyTom]

Thank you for volunteering.

[ShiraiJunichi]

Is that an invitation?

[DaFool]

Hehe...

*cough*

Well, I for one suck at leadership

I can only give suggestions

All I know is that I'm still learning but that definitely will be making the script for my game as easy to understand, with comments. I will also release a pdf 'how I made my game' once that's done, and that will serve as supplementary tutorial.

The best demos imho, since they are part of more full-featured applications, share that application's quality.

Therefore, don't make something specifically to be a demo, but only with an eye that 'hey, this could be a good demo'. If you get my drift. Just make it good, then decide if you want it to be friendly for reverse engineering. If so, polish the script and write up a technical how-to. The actual programming style will be given away of course, but the original artworks will still be protected under Creative Commons license or whatever. Just hope no one pulls a Subarashishit whatever on your project.

[lordcloudx]

hehe that's more like a surprise appointment.

So then, do we go with the dream sequence?

[DaFool]

I still don't fully understand the concept of the dream sequence.

Is it like a series of flashbacks, with each flashback demonstrating an aspect of Ren'py? Or each flashback featuring a clip from a Ren'py visual novel? How will the different incarnations of Aileen play into this? Wouldn't this be just as complex as the original demo?

[lordcloudx]

the concept of the dream sequence if accepted would all depend on the arbitrator. Which ideas make it to the final demo and which ones get axed.

I'm still advocating a good main story and several substories for the dream sequence.

[DaFool]

But this assumes we only have one upgraded demo. Which still doesn't solve the complexity problem. Look at Blade...they have 3. It sure didn't intimidate me unlike the first time I looked at Ren'py.

Btw kabayan, it seems like you are working on night shift. Which only means either call-centers or animation studios. Lol, those are the only ones with good internet

[lordcloudx]

So... prior to the next demo release let's all wear a "support the ren'py movement" sig in any other forums we're members of. Oh yeah and a nice fat ren'py banner would look good on top of our websites too no?

something like this. (points to sig) although technically, none of those characters have been used in a ren'py game.