12-05-2024, 05:57 PM
Hey @SierraKen
I loved Apple ][ Lemonade Stand! I've tried this as a result.
It's cool that you are showing graphics of weather, it'd be even cooler if it animated them using code.
The game loop is:
1. Show weather (full screen) wait...
2. Show status (full screen) [press ENTER]
3. Show menu / handle choices
This is good, and it's honoring the original game, but I'm finding that when I'm at #3 I often want to know what my status is.
What if...
You showed the status and the menu at the same time? Or made an option to show it in the menu? This way we don't have to remember the status, and can make more informed decisions.
Just a thought
Your program is well made and works great. I am not sure about the weather algorithms and the randomness though.
For example, it was hailing, and I sold cups for $2 each. I had more people come out to buy lemonade during a hail storm for 2$ than I did on a regular day
I think this might need some tweaking In my mind hail = less customers.
If your logic (I have not yet looked at the code wanted to capture the feedback first) is calculate based on price as a first pass, maybe factor in weather first? Then advertising/prices?
Thanks for sharing.
Here is a screenshot. In the menu it looks like maybe you could have room for status too. Or another option to "show status"
One pattern that would be useful is all in one screen Weather in a quadrant, status in another, and menu/results/events in another?
2c.
Thanks
I loved Apple ][ Lemonade Stand! I've tried this as a result.
It's cool that you are showing graphics of weather, it'd be even cooler if it animated them using code.
The game loop is:
1. Show weather (full screen) wait...
2. Show status (full screen) [press ENTER]
3. Show menu / handle choices
This is good, and it's honoring the original game, but I'm finding that when I'm at #3 I often want to know what my status is.
What if...
You showed the status and the menu at the same time? Or made an option to show it in the menu? This way we don't have to remember the status, and can make more informed decisions.
Just a thought
Your program is well made and works great. I am not sure about the weather algorithms and the randomness though.
For example, it was hailing, and I sold cups for $2 each. I had more people come out to buy lemonade during a hail storm for 2$ than I did on a regular day
I think this might need some tweaking In my mind hail = less customers.
If your logic (I have not yet looked at the code wanted to capture the feedback first) is calculate based on price as a first pass, maybe factor in weather first? Then advertising/prices?
Thanks for sharing.
Here is a screenshot. In the menu it looks like maybe you could have room for status too. Or another option to "show status"
One pattern that would be useful is all in one screen Weather in a quadrant, status in another, and menu/results/events in another?
2c.
Thanks