Curious whether or not I am getting the right idea about this VN from those of you who have played it. Trying to see if it is worth subscribing or even trying.
My read from the comments is:
-- it potentially is a very good VN
-- VERY buggy
-- with update after update incompatible with prior saves so that you have to start over every update.
-- extremely weak programming and logic skills
-- little evidence the author is getting better at programming Renpy
(There is so much crap released as VNs on Patreon -- piss-poor or abandoned after a release or two -- that I always read through a few pages of F95 posts before I consider subscribing to VNs. )
Am I misreading FILF as "...wait for the author to get his act together before getting frustrated with it..." status?
My read from the comments is:
-- it potentially is a very good VN
-- VERY buggy
-- with update after update incompatible with prior saves so that you have to start over every update.
-- extremely weak programming and logic skills
-- little evidence the author is getting better at programming Renpy
(There is so much crap released as VNs on Patreon -- piss-poor or abandoned after a release or two -- that I always read through a few pages of F95 posts before I consider subscribing to VNs. )
Am I misreading FILF as "...wait for the author to get his act together before getting frustrated with it..." status?
ICCreations has a moderately decent track record, and they've made (I think) about a half dozen previous games. I would give them a shot at bringing this project to fruition.
V0.6.2 I doubt is very buggy, if at all.
Major code rework has happened in the update, at which changed around some of the questline flow and as such, other things.
V0.7 should be compatible with a playthrough in this version. It was literally impossible to have perfect old-save compatibility. I always provide a save with previous version content done, but that also wasn't possible as some of Sam's questline happens BEFORE a lot of the older stuff.
What people seem to not understand is that a BETA means possible bugs, and there were a couple. V0.6.1 was not meant for everyone to play yet. It wasn’t a stable version.
As for v0.6.2, I haven’t been hearing about any bugs so far and others are experiencing a stable playthrough.
Please be mindful that your jumping into a beta version of a game, you should be going in expecting a problem or two, or if we are lucky, none at all.
Major code rework has happened in the update, at which changed around some of the questline flow and as such, other things.
V0.7 should be compatible with a playthrough in this version. It was literally impossible to have perfect old-save compatibility. I always provide a save with previous version content done, but that also wasn't possible as some of Sam's questline happens BEFORE a lot of the older stuff.
What people seem to not understand is that a BETA means possible bugs, and there were a couple. V0.6.1 was not meant for everyone to play yet. It wasn’t a stable version.
As for v0.6.2, I haven’t been hearing about any bugs so far and others are experiencing a stable playthrough.
Please be mindful that your jumping into a beta version of a game, you should be going in expecting a problem or two, or if we are lucky, none at all.
You can give her or you give buy it ? If you can give her can you tell me how you buy it please ?
I fully understand the issues with a beta release. Yet, the save game compatibility and degree of bugs cited in this forum should be cause for concern for you.
However, I will log into Patreon, subscribe, and try 6.2 -- if you have indeed licked the save game issue then all the positives about your story make it worth a shot. Heading over to subscribe now.
EDIT: Correction -- just went to your Patreon page and see you only have the beta version available. Will wait for a stable non-beta 6.2
- May 26, 2017
- 119
- 68
The bugs cited for V0.6.2 on the forum aren't bugs, but false reports. V0.6.1 DID have a few bugs though, as it is in beta testing. Those were cleared up and I haven't experienced or been reported of any bugs as of V0.6.2. A bug free game is VERY important to me, and I released a fixed version within 24 hours.
As for save files, V0.6 was originally going to have compatibility with V0.5 saves, but as I was finally able to hire someone to do the coding for me, it had to be delayed for an update.
- Apr 6, 2018
- 55
- 15
ugh what do i do I'm sorry, but an uncaught exception occurred. While running game code: File "renpy/common/000statements.rpy", line 485, in execute_call_screen store._return = renpy.call_screen(name, *args, **kwargs) File "game/script_map.rpy", line 3, in execute File "game/script_map.rpy", line 3, in execute File "game/script_map.rpy", line 5, in execute File "game/script_map.rpy", line 79, in execute ValueError: 0 is not in list -- Full Traceback ------------------------------------------------------------ Full traceback: File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 105, in script call File "script_auntshouse.rpyc", line 434, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 105, in script call File "script_laptop.rpyc", line 2935, in script call File "script_laptop.rpyc", line 2914, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 105, in script call File "script.rpyc", line 1787, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 105, in script call File "script.rpyc", line 1726, in script call File "script_scenes.rpyc", line 3969, in script call File "script_spa.rpyc", line 217, in script call File "script_spa.rpyc", line 453, in script call File "script_spa.rpyc", line 453, in script call File "script_spa.rpyc", line 327, in script call File "script_spa.rpyc", line 327, in script call File "script_scenes.rpyc", line 4183, in script call File "jobs.rpyc", line 701, in script call File "jobs.rpyc", line 744, in script call File "jobs.rpyc", line 658, in script call File "jobs.rpyc", line 701, in script call File "jobs.rpyc", line 744, in script call File "script.rpyc", line 928, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 105, in script call File "script.rpyc", line 928, in script call File "script_characteridles.rpyc", line 29, in script call File "script_spa.rpyc", line 327, in script call File "script_spa.rpyc", line 327, in script call File "script_spa.rpyc", line 217, in script call File "script_spa.rpyc", line 217, in script call File "script_spa.rpyc", line 453, in script call File "script_spa.rpyc", line 453, in script call File "script_scenes.rpyc", line 4253, in script call File "jobs.rpyc", line 658, in script call File "jobs.rpyc", line 658, in script call File "jobs.rpyc", line 744, in script call File "jobs.rpyc", line 701, in script call File "jobs.rpyc", line 701, in script call File "script_auntshouse.rpyc", line 434, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 105, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 105, in script call File "script.rpyc", line 928, in script call File "script_characteridles.rpyc", line 29, in script call File "script_spa.rpyc", line 453, in script call File "script_spa.rpyc", line 453, in script call File "script_spa.rpyc", line 327, in script call File "script_spa.rpyc", line 327, in script call File "script_spa.rpyc", line 217, in script call File "script_spa.rpyc", line 217, in script call File "script_scenes.rpyc", line 4253, in script call File "jobs.rpyc", line 658, in script call File "jobs.rpyc", line 744, in script call File "jobs.rpyc", line 744, in script call File "jobs.rpyc", line 701, in script call File "jobs.rpyc", line 701, in script call File "script_auntshouse.rpyc", line 434, in script call File "script.rpyc", line 928, in script call File "script_characteridles.rpyc", line 29, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 105, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 1562, in script call File "script_laptop.rpyc", line 105, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 1562, in script call File "script_laptop.rpyc", line 105, in script call File "script_laptop.rpyc", line 20, in script call File "script_laptop.rpyc", line 105, in script call File "script_laptop.rpyc", line 2935, in script call File "script_laptop.rpyc", line 2914, in script call File "script.rpyc", line 928, in script call File "script_characteridles.rpyc", line 29, in script call File "script_map.rpyc", line 789, in script File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\ast.py", line 1801, in execute self.call("execute") File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\ast.py", line 1789, in call return renpy.statements.call(method, parsed, *args, **kwargs) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\statements.py", line 169, in call return method(parsed, *args, **kwargs) File "renpy/common/000statements.rpy", line 485, in execute_call_screen store._return = renpy.call_screen(name, *args, **kwargs) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\exports.py", line 2655, in call_screen rv = renpy.ui.interact(mouse="screen", type="screen", roll_forward=roll_forward) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\ui.py", line 287, in interact rv = renpy.game.interface.interact(roll_forward=roll_forward, **kwargs) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\display\core.py", line 2624, in interact repeat, rv = self.interact_core(preloads=preloads, trans_pause=trans_pause, **kwargs) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\display\core.py", line 2999, in interact_core root_widget.visit_all(lambda i : i.per_interact()) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\display\core.py", line 511, in visit_all d.visit_all(callback) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\display\core.py", line 511, in visit_all d.visit_all(callback) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\display\core.py", line 511, in visit_all d.visit_all(callback) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\display\screen.py", line 401, in visit_all callback(self) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\display\core.py", line 2999, in <lambda> root_widget.visit_all(lambda i : i.per_interact()) File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\display\screen.py", line 411, in per_interact self.update() File "C:\Users\IO\Desktop\FILF-0.6.1_BETA-pc (1)\FILF-0.6.1_BETA-pc\renpy\display\screen.py", line 592, in update self.screen.function(**self.scope) File "game/script_map.rpy", line 3, in execute File "game/script_map.rpy", line 3, in execute File "game/script_map.rpy", line 5, in execute File "game/script_map.rpy", line 79, in execute File "<screen language>", line 79, in <module> ValueError: 0 is not in list Windows-8-6.2.9200 Ren'Py 6.99.14.1.3218 FILF 0.6.1_BETA Sat Jul 28 01:01:26 2018
You want the drinks to add up to 50% so buy one red which is 20%, 2 of the 9% which I can't recall the color and then 3 of the 4%, which is blue. Then offer her a drink and give her all of them, it will add up to 50%. Then ask the DJ to play I want candy and then ask her to dance.
- Aug 7, 2016
- 211
- 462