Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

velShandru

5
Posts
4
Following
A member registered Mar 10, 2022

Recent community posts

Plays fine on mine. What's the issue exactly (which version won't load and have you tried others?).

I have it running in Wineskin6 under MacOS10.15, which is 64 bit. I'm seeing a wine32on64 applet in the resources folder, along with the expected wine64 but given Catalina's crankiness, I strongly suspect that it's running in 64 bit mode. I can try running it in a linux VM if you like, just let me know which *nix you'd like to see tested.  :)

Because we're not using Scriv to write code, the Menu/UI block would, IMO <g>, be used to sketch in the elements we want to include without committing us to any particular engine. Of course, it could simply be used to display a screenie of whatever GUI template we plan to use, but the various engines and template have enough tweak-ability that I thought you had included the block so we consider our screen layouts. I s'pose a ReadMe ought to be there describing what the user may (or may not) want to consider...

(1 edit)

You did indeed describe it as a starting point for an overwhelmed beginner.  I simply expected more than you promised to deliver <smile>. The description said it wasn't designed to teach coding — nor should it since we could be coding in any of several VN engines —  but your filled in examples provide some light RenPy coding to get us started and my sample did the same. It would have been clearer if I had simply included the Coding line and then added the sample separately as you had done. The Item and Location profiles have a section for Programming Notes and I happen to feel that it's a useful addition to the Character profile as well.

I also like to keep the storyboard focused on story flow and use the Narrative block to break the story down into panels within a scene. Obviously one or the other block could be eliminated depending on the user's working style, but showing two approaches to story flow may be useful to beginners. My Narrative block has stage directions but not the actual code for them, e.g.:


------
PANEL <$SN>: BUYUNISTAN VILLAGE STREET. SITA SLIDES IN ON THE LEFT.

Sita:    Kei, over here!

ADJUST: KEI SLIDES IN ON THE RIGHT.

               {short dialogue between Sita & Kei omitted}

ADJUST: SITA GESTURES LEFT.


Sita:    {more dialogue}

ADJUST: SITA RESUMES ORIGINAL POSE.

Sita:    {continues...} [Kei being my viewpoint character & Sita my exposition fairy]
-------

For beginners looking at this, the PANEL <$SN> tag is from the comic template I based my own template on and simply indicates a scene with no change of background, hence the ADJUST tags. Note that it's a bit closer to the actual code (RenPy in this example) but could still be implemented in any of several engines.
(1 edit)

Wasn't terribly happy with this @$10, though it would have been worth every penny had I come across it a year ago before adapting my own from a couple of comics templates. I was quite disappointed that the Narrative section is a copy-paste of the Storyboard, though with its own ReadMe; and Menu/UI is entirely empty. What did you use that section for?

On the upside, I had entirely overlooked adding Programming Notes to every template. I had only put that in my Character Profile. It's now just below Character Art e.g.:

Coding:   image sita=“Sita.png"
               define s = Character("Sita", color="#c8ffc8", what_color=“#c8ffc8")

If you feel bad about an unhappy customer, just toss a copy into the community pool; I'd far rather work with you to improve the template.  :)