Currently, we are down to the last 4 CGs for this game. IRL issues caused some delays for my lovely volunteers, but a lot of progress has been made ^.^
As for the other two in the main quartet, my IRL has kept me horrifically busy. I am trying to find ways to get more work door throughout the day though in order to start hammering through more progress in that regard.
When you say "some" do you mean more than 2? If you pick 3 affection raising options, you will go onto the Attention path. If you want to guarantee the Spider ending, you must have 0 affection with both. No affection raising choices.
Uninstall the whole thing and redownload. Chances are there is something in the old cache lingering.
Outside of that, make sure you're only picking middle choices if you want to guarantee a Spider end. If you get them too high, you might end up on an Attention/Affection path instead.
Are you certain you fully uninstalled the original files you had (fully delete them - everything. Not a trace behind)?
Make sure you've done that and then download the 1.1 version on the game page. It looks like you're still using older files.
I've scanned the code for this sprite conflict , and it doesn't appear in the latest version of the game I have at present. If it persists after deleting everything and starting from scratch with the new files, let me know.
I'm afraid that Violo & Vivere don't have a reference sheet as per normal methods. If you dig around my tumblr though, you should be able to find the old WIPs for their sprites.
I don't have that sketch. Rian must have added that, as they had to upload the yanjam demo because the end of yanjam coincided with my injury. Iwas actively trapped at a hotel away from my rig at the time. I had to guide Rian through packing and uploading the demo from my phone. That's adorable. Maybe we did discuss it? The week of the demo release and the following ten months were frankly a blur of stress, pain, and discomfort, so I really don't remember much.
I don't have that sketch though, nor do I have access to the loose files (because I didn't compile the demo build). So, I have no way of adding it to the live versions I'm building.
This is a really cool mandela effect. I think you might be thinking of a really popular piece of fanart by brbbringingnachos. The main menu has always been a plain beach, and there has never been a beach walking CG.
The lack of randomness in the choices is intentional as an anti-frustration feature. Or at the very least, it's intended to be. Since a lot of the content is a numbers game, being able to confidently hit the numbers desired on subsequent playthrough is important.
Case in point: to get the bad end (there is only one) there are technically two paths. The easiest is to pick 6 good options throughout week 1 and week 2 to hit the minimum required to hit the affection route. Then, you start tanking your score by choosing only bad options during Week 3.
You can call me kiss. I'm currently working on my third VN, and while I have been blessed to find people for all of my other remaining art roles, I've been unable to find a logo artist and cover image illustrator.
The Woeful Rose & The Bitter Crow is the third game in my Sacrarium series (a volunteer powered VN series). It was originally an OjiJam 2023 entry, but I ended up dealing with a severe injury for a few months. That halted all progress for a while. Now that I am better and in a much better place, I've begun the work needed to complete it.
As it stands, the only art role I'm still missing is a logo artist and cover image illustrator. All that needs to be completed for this role is a 250 x 100 logo and a 630 x 500 cover image for itch.io. The game is set to hopefully release around May or June of this year, so this isn't a rush job.
Of course, as this series is entirely free, this would be a volunteer position.
Also, all applicants must be 18+. While this is a SFW series, I do not work with underage volunteers.
Thank you so much for your time and consideration! Please feel free to comment your discord in the comments below or shoot me an e-mail at stygianeyedev@gmail.com to discuss further!
The ending is fully functional. I just went to test it myself again to make sure it works.
You must "Decide to look around," "Ruminate on the thought" that MC could do a lot of good if they had some of his items, and choose "I decided to look around for interesting objects" when the option comes up. You also must keep his affection as low as possible. You cannot gain a single point of affection.
You need to be nosy both times, obsess over the fact that Heimos has the journal and a ton of magical stuff (and think it's unfair, and NOT have him in neutral or positive affection.
Essentially, any time there are three choices, always pick the top one. If you have the option to snoop, always snoop.
Pick only top answers from the beginning and that should lead you to most of the bad endings. Make sure to have one where you don't snoop and one where you do snoop and decide to keep snooping.
Theoretically that should them (and if it doesn't, I might need to double check the code).
Do not worry, this is a bug that has cropped up for multiple people. Some how some of Viv's voice lines got kicked to the music channel instead of the voice channel. It has been addressed and should hopefully not happen in the next patch.
I'm going to have to fiddle with the audio over all, as I did receive reports that Viv's lines tend to be a bit louder than Vio's. This time I'm going to make very, very sure that things are coded right.
It is still a W.I.P. Between my injury and some other things that got in the way, the game got very delayed. At the moment, it's still in waiting for final assets (AKA: CG art), but it has been fully written and mostly fully programmed at this point.
You more than likely hit the end of the demo (if the conversation was at the dinner table). Due to me being injured and trapped away from my computer at the time of release (we had to release it before the jam finished), the demo didn't have an end screen put in to signify the end of what was available.
Thank you for loving Heimos. Small correction though! The art was done by the wonderful Rian and Mota (alongside the GUI template from JaimeScribbles), they did stellar work didn't they :D
No :) As this was a volunteer project, there aren't any contracts/agreements in place for financials, thus I will never charge money for the game or have the "pay what you want" feature toggled on. Also, since these games are made in a short time span (each game is supposed to have only about 3-6 months of active work on it - IRL issues getting in the way not withstanding), they don't quite reach what I deem 'professional quality' (aka: something polished enough I feel comfortable charging money for).
I crawl out of my hole multiple months later to confirm that yes, Necare and Amare are planned to get their own games.
My IRL situation went to hell for a while, so progress is slow in general. Once Pario is finished, I will finish the mini sequel set a few hundred years later (The Woeful Rose & The Bitter Crow) and then start tackling Necare's game!
Hello, I'm running into an odd exception while trying to open the test game. It won't launch and gives me this exception:
File "C:\Renpy\renpy-8.0.3-sdk\renpy\bootstrap.py", line 277, in bootstrap
renpy.main.main()
File "C:\Renpy\renpy-8.0.3-sdk\renpy\main.py", line 558, in main
renpy.game.context().run(node)
File "game/gui.rpy", line 15, in script
define config.check_conflicting_properties = True
File "/home/tom/ab/renpy-build/tmp/install.linux-x86_64/lib/python3.9/site-packages/future/utils/__init__.py", line 441, in raise_
File "game/gui.rpy", line 15, in script
define config.check_conflicting_properties = True
File "C:\Renpy\renpy-8.0.3-sdk\renpy\ast.py", line 2441, in execute
self.set()
File "C:\Renpy\renpy-8.0.3-sdk\renpy\ast.py", line 2459, in set
ns.set(self.varname, value)
File "renpy/common/000namespaces.rpy", line 33, in set
setattr(self.nso, name, value)
File "C:\Renpy\renpy-8.0.3-sdk\renpy\defaultstore.py", line 105, in __setattr__
raise Exception('config.%s is not a known configuration variable.' % (name))
Exception: config.check_conflicting_properties is not a known configuration variable.
I'm not the best at GUI coding, so I'm a bit stumped. How might I go about fixing this?
