Ludum Dare 30 — August 22nd-25th, 2014 — Theme: Connected Worlds

[ Real World Gatherings | Ludum Deals | Warmup Weekend (Games) | MiniLD #53 | Wallpaper (1) (2) (3) | Mailing List ]

Back to Browse Entries

Crossed Paths:Connected Worlds

by MikomiKisomi - Jam Entry

Crossed Paths:Connected Worlds is a finished visual novel about a high school senior named Claire who's life keeps throwing things at her and feels she's at her breaking point, when she finds a mysterious necklace in the woods. That night she meets Sophronia, a girl her age with the exact same necklace who tells Claire that their necklaces have the ability to travel to other worlds! This game features 2 alternate endings, so be sure to go back once you get one ending!

Music was used with permission from here:
http://www.newgrounds.com/audio/listen/554093
http://www.newgrounds.com/audio/listen/566866

(This is my first Ludum Dare, and I just began game designing 2 months ago, so I decided to stick with a visual novel, since I'm best at those.)

Downloads and Links


Ratings

#2124Coolness10%

Comments

Aug 26, 2014 @ 6:48am

Hi! Congratulations, first of all, on your very first Ludum Dare game jam! I hope to see you again in December :]

I went looking for Visual Novels and was happy to find yours! I really like your character designs, and the music you chose was cute. Did you compose it yourself? You've clearly put a LOT of effort into this!

The only thing I would say is that I think the player might like some decision points sooner in the dialogue! When you're writing for games, you don't have as much opportunity to give lots of character exposition. The goal is to engage *interactivity*, so the player has to feel like they're taking an active part in the narrative, if only in interpreting it to make good choices later!

Thank you for the game!

GrooveMan says ...
Aug 28, 2014 @ 9:01pm

Ah, I do love cute romance stories. I'm not sure if I'm feeling the design decision to have both characters look at the 'camera' (Usually you choose to either look through the eyes of the protag or have the characters look at each other).

I think you needed another, more sombre music tracks, since the upbeat music kinda made the more heartfelt parts fall flat, but overall it was an enjoyable story!

Keep experimenting with Ren'Py functions (I'd say look into how to move characters around the screen and changing the look of the textbox as your next steps), and you'll be a pro in no time. Thanks for making this!

Sunflower says ...
Aug 30, 2014 @ 4:41pm

Okay, it was rather interesting, though there have been only two choices from what I saw, out of which the first probably still had the same outcome eventually. There's just some thing I really wasn't fond of - it seemed only the characters' mouth expression changed during the conversations, while eyes, gestures etc. (especially eyes) were static, which made especially Claire look somewhat... I don't know, aloof? *shrugs*

Still, that's a nice start for your first entry. ^^"

Aug 30, 2014 @ 6:19pm

Hey, another RenPy dev ! Not bad for someone who had just begun, the story was nice and all. I just got the good end but it was satisfying (YURI FTW).

Just a little nitpicking but you shouldn't show sprites over a CG, it hides the picture and doesn't add much to the story =o.

NicePenguins says ...
Sep 3, 2014 @ 3:34pm

Well done for your first ludum game !
Like Victory Garden was saying, it's need more interactions to engage the player. And i find that the dialogues were a little bit cliché.

Sep 4, 2014 @ 12:30pm

Overall, this VN is good, save for some nitpicks.

1. Event CGs are called event CGs for a reason. They signify an event that cannot be conveyed by ordinary character sprites alone. As an experienced VN connoisseur since 2005, please do not place character sprites when showing event CGs.
2. Some typos and grammatical errors remain, but they do not bother me a lot.
3. A credits sequence would be nice.

You must sign in to comment.


IMPORTANT NOTE: If you want to place in the final results, you NEED votes. The easiest way to get votes is by rating other games. Judging lasts for 3 weeks following the end of Ludum Dare. For best effect, rate 20 games as soon as possible. Rating more games is encouraged.

MORE TIPS AND DETAILS AT THE BOTTOM OF THIS PAGE

TEAMS: Teams entering the Jam should pick a single representative to submit your game, or create a team specific account you can share. We currently do not support Team Voting, but sharing an account and together playing and rating games is acceptable.

NOT LOGGED IN?: If you get a message about not being logged in, even though you are, it’s because your web browser cached the non-logged in page. You can fix this by either refreshing your cache or clearing your cache. CTRL+F5 in many browsers. Chrome is a bit more work. Press F12 to enable Developer Mode, then you can right click on the refresh button and select “Empty Cache and Hard Reload”. This option is unavailable if you are not in Developer Mode.

PORTS: Ports to other platforms can be done after the deadline. That said, the sooner you finish your port, the sooner people can play your game, improving your chances of placing in the final results. For best results, provide a Web version of your game, or a Windows version with no dependencies. Also be sure to rate about 20 games to improve your visibility.

MY GAME DOESN’T SHOW UP: If you can’t find your game, it’s usually because the URL to your downloads are missing ‘http://‘. Fix your URLs (http://mysite.com/mygame.zip) and you will show up.

MY GAME CRASHES, IS UNBEATABLE, OR I MADE A TYPO: We allow you to fix crash or win condition bugs after the deadline (in a sense, like “porting” to support more players). We also allow “typo” bugs. I.e. A true that should have been a false, a word that should have been a different word, very tiny changes that you would have caught if you had more sleep. We leave this open to interpretation, but generally speaking your game should be identical to the game you submitted. No new features, just things you messed up last minute. Typos.


[cache: storing page]