[RELEASE/FEEDBACK] FapJack with Melody

[fapnip]

Here's a test version that's more aggressive with stroking in later rounds if you have a number of unused rests:
xx this has been released now xx

Please let me know if you think it should/shouldn't be used as the release version.

[Achatius]

It's completely random. I could increase the probability of stroking I suppose. The free rest time does (should) decrease after each full round.
Surprised that you ended (won?) with 7 unused rests... maybe I should increase stroking penalty probability and length based on number of unused rests?

No... I didnt won. The new version with more stroking is better

[thongs911]

I doubt it is anything you can control, but it sucked up a ton of RAM. It was over 4 GB before my browser crashed.

[fapnip]

I doubt it is anything you can control, but it sucked up a ton of RAM. It was over 4 GB before my browser crashed.

Wow. I was wondering if I'd get reports like this. Probably related to this EOS bug?

What browser were you using? Were you in private/incognito mode?

I put in periodic game state saving, so you can continue where you left off if you get back in before 2 min. is up, for this very reason -- though I imagine many people use web teases in private/incognito mode, so once your browser window closes, you'll lose all state.

[fapnip]

Here's another pre-release (0.7) for anyone interested in testing:
xx this has been released now xx

Includes:

• More aggressive stroking in later rounds if you still have a number of rests left
• Re-shuffle deck after 5 hands instead of continuous re-shuffle. (Currently no re-shuffle notification.)
• Maybe a fix for memory leak? (I tightened up notification use in a couple spots. Not sure if it will help. I can't replicate any memory leak.)
• A bunch of other under-the-hood changes that you shouldn't notice, unless they introduce a bug.

[Carnal1]

I still think this is a great tease but it's crashing on me too. I thought it was just me but guess not. I'm using an older tablet with Chrome. Tried both incognito and not. Signed in and not. Just tried this latest release of yours: 0.7. Yesterday tried whatever was up on a newer phone with Firefox. Regardless, I get to 3rd round and it starts getting sluggish at spots then after a couple more hands crashes. When I immediately restart it starts at beginning of tease with no progress, even signed in and not in incognito (didn't have to sign back in after crash, it still had me in)

I know nothing of eos programming, but some teases are able to save progress between sessions. This wouldn't be the same tease if play was broken up with rests or over days, but if there was a way to save progress we could at least restart after crashing. If that's a no go, even just being able to jump to each round & start fresh there would be better than nothing.

I've liked this tease from the get-go. And changes too - more edges, more stroking, whatever. It's all been great. It's definitely super tough, but not impossibly so. Thanks for not only producing it, but sticking with it and trying to improve. Definitely appreciated.

[fapnip]

I still think this is a great tease but it's crashing on me too. I thought it was just me but guess not. I'm using an older tablet with Chrome. Tried both incognito and not. Signed in and not. Just tried this latest release of yours: 0.7. Yesterday tried whatever was up on a newer phone with Firefox. Regardless, I get to 3rd round and it starts getting sluggish at spots then after a couple more hands crashes. When I immediately restart it starts at beginning of tease with no progress, even signed in and not in incognito (didn't have to sign back in after crash, it still had me in)

I'm sorry to hear that.

If it was able to save/restore state, you should have been prompted at the beginning of the tease if you want to continue or not. I currently have a 2 minute time limit, so if the last state save (beginning of a hand) was over two minutes old, it would be lost. If you're stuck in an edge, etc., I suppose that could be longer than 2 minutes... maybe I need to save the state more often, or increase the age limit? Or maybe the crash causes the browser to not actually store items in local storage?

I know nothing of eos programming, but some teases are able to save progress between sessions. This wouldn't be the same tease if play was broken up with rests or over days, but if there was a way to save progress we could at least restart after crashing. If that's a no go, even just being able to jump to each round & start fresh there would be better than nothing.

It should be saving your state as describe above, but unfortunately I've not been able to replicate the issue you're having yet. Could you give me more details on the devices (model/ram/OS/version) and browsers (name/version) you were able to consistently get this issue to trigger on?

I've liked this tease from the get-go. And changes too - more edges, more stroking, whatever. It's all been great. It's definitely super tough, but not impossibly so. Thanks for not only producing it, but sticking with it and trying to improve. Definitely appreciated.

Thank you for your valiant attempts to play it!

[fapnip]

After some more testing, I think I may have been able to reproduce the memory leak issue on mobile chrome with remote debugging enabled, though I haven't had much time to look into it very deeply.

What appears to be happening (very preliminary, could be wrong) is that EOS is re-downloading the all the images for a given level over and over again each time only a single new image is to be loaded. I'll look into it more, but I'm not sure if there's much I can do to easily fix it. Interestingly, it doesn't seem to happen on non-mobile chrome.

I'll keep looking into options to resolve this, but for now, I'd recommend reloading your browser page when you notice things bogging down, but before the game borks. You should be prompted to continue where you left off. (Please give that part a test before you get too far in.)

[Carnal1]

I saw how you'd said it should reload with saved state if within 2 minutes, and it was definitely within that. I think the tease was doing the punishment roulette bit when it crashed (but hadn't seemed to have picked one yet). It didn't crash the whole browser, just that tab which immediately started to reload and had a pop up to continue. I did and the tease started from the beginning with no other option. I clicked on the button to start playing just to be sure and it just started like a new game. I then closed it and reloaded to see if that'd make a difference and it didn't.

I did just now give it a little test by playing just a few hands then closing the tab and reloading the game. It worked just as you expect and noticed I had an uncompleted game which reloaded fine. So, no idea why it didn't earlier when actually playing crashed.

Samsung tablet, android 4.4.2, chrome browser. Like I'd said, older! Other teases seem ok, but it does sometimes get challenged by some high demand websites. Also happened on pretty new motorola phone with current Firefox a day or 2 ago. I'll give it another go on that when I get another chance and see if your changes since then helped.

[fapnip]

Here's a pre-release of v0.8:
xx this is now released xx

Anyone having crash issues with this tease, please give this 0.8 pre-release a shot and let me know if it helps. Hopefully I identified the issue correctly, and not barking up the wrong tree.

Changes:

• Completely refactored the way round images are loaded. Before, I loaded one page per "level", then if'd through 15 images to display the one for the given round. Mobile browsers seemed to re-load all 15 images on every level change. Now, there's one page per image.
• Changed most page goto actions to "pages.goto(page);" eval actions. EOS seems to pre-load any images it can find in pages referenced with goto actions, even if in an "IF" action that doesn't match, and those pre-loads seem to happen over and over again, eating ram on mobile browsers. (Do that in a loop like I do with each hand, and you die quickly? Strange that only some browsers/devices seem effected though.) EOS doesn't seem to follow pages.goto(page);, so images in pages referenced that way appear to only be loaded if the page is actually requested.

[Achatius]

This tease is really amazing. Do you think of putting in other stuff like POT, CEI, CBT etc.?

[eloelo120]

Hey,
I've played this tease earlier and I must say I didn't thought that such concept will give so much fun. It's cool to play and stroke at the same time. Sentences you used to describe things like Get close to the edge are also very well put which gives even more fun. Overall, very fun to play.
Unfortunately I quit after couple of minutes because it was getting kinda boring. Getting to edge so many times in such short time is just not my thing. I would highly suggest to add different tasks e.g. slap your balls, put on a clothespin or anything else really. If someone don't want that included, you could just add that to settings and if someone wants just an endure test, go ahead.

I understand that your idea was to make this year difficult, but maybe give it a try to add other tasks:) no clue how much work it is so in sorry if I am asking for too much

[thongs911]

I doubt it is anything you can control, but it sucked up a ton of RAM. It was over 4 GB before my browser crashed.

Wow. I was wondering if I'd get reports like this. Probably related to this EOS bug?

What browser were you using? Were you in private/incognito mode?

I put in periodic game state saving, so you can continue where you left off if you get back in before 2 min. is up, for this very reason -- though I imagine many people use web teases in private/incognito mode, so once your browser window closes, you'll lose all state.

I was using Firefox on Windows 10 in Private mode.

[fapnip]

I was using Firefox on Windows 10 in Private mode.

Thanks. I've released a new version that hopefully addressees the issue, but I'm kinda shooting in the dark since I'm still unable to fully replicate it. The updated version seems to have a lower average memory footprint on most browsers.

I can get Chrome on Android to bog down a little, but can't get it to crash. The updated version actually shows a slightly higher memory footprint on Chrome/Android.

Unfortunately I quit after couple of minutes because it was getting kinda boring. Getting to edge so many times in such short time is just not my thing. I would highly suggest to add different tasks e.g. slap your balls, put on a clothespin or anything else really.

Do you think of putting in other stuff like POT, CEI, CBT etc.?

Thanks for the feedback!

I may experiment in a later tease, but I wanted this first FapJack release to be as simple and approachable as possible.

The core game is built to make adding penalties relatively easy.

[itslate]

I enjoyed this tease a lot! Very innovative and simple, yet hard

I would love to know how you incorporated variables in the notifications. Did you do a big cascading if-action?
Also, how did you program the shuffling edging and stroking tasks?

Really neat!