65
edits
Changes
Jump to navigation
Jump to search
Line 18:
Line 18: + Line 27:
Line 28: + + + + + + + Line 169:
Line 177: + + +
no edit summary
==Important Ideas==
==Important Ideas==
Variations in customer demand<br>
Variations in customer demand<br>
Perishable resources<br>
Variation of prices (both materials and final product)<br>
Variation of prices (both materials and final product)<br>
Random events that may influence supplies and/or cost and/or customers<br>
Random events that may influence supplies and/or cost and/or customers<br>
Potential use of network, competitive or cooperative modes<br>
Potential use of network, competitive or cooperative modes<br>
==Weekly Milestones==
4/24: Have everyone look at the current implementations.
5/1: produce a basic 'sugarized' build to work from. Implement price fluctuations.
5/8: Move to a 'graphical interface' based off of pyGTK or pygame. Add any art we have managed to collect where it seems appropriate.
==Code so far==
==Code so far==
today += 1
today += 1
</pre>
</pre>
==Design Decisions==
Is lemonade made at the beginning of the day (make all available lemonade at once) or on the fly (a customer asks for lemonade and it is made for them)? This is important as it impacts the resources from day to day. In the former, normally non-perishable objects like cups will be used if they can make another drink (even beyond demand), however in the latter, it makes the game easy if you stock up on resources and slowly sell them each day. This is usually mitigated by having perishable resources (lemons, etc) and variable prices.