Chef Archive
Thread: Sciguy Dont back out now!
- Schematic lookup (displays required resources/components when selecting a food/drink name). Not really glamorous, but the data is going to be needed for other pieces, so I figured it wouldn't be too difficult to add.
- Experimental percentage calculations (basically what that last spreadsheet does). It would have the food stats in addition to the raw percentages. This might even include a "crafting simulator" where you can allocate points into the different categories and see what the final result would be (although dealing with different success types might be a bit difficult).
- Resource comparison. Similar to the percentage calculations, but allowing the user to enter multiple types of a resource to see how that effects the final product. This would probably be limited to a single schematic slot, comparing the various results of combining 3 different berries with 4 different fruits would get a bit daunting.
- Some sort of price calculator. I'm trying to lay something out so subcomponents are easier to include.
I've got a rough design sketched out, although I'm still up in the air on the data storage. A database might be overkill, maybe something along the lines of an XML document would be enough. Although that would probably require loading all the data into memory at once, as opposed to getting it as needed from the database...
I will check back in later with a progress report. 
sciguyCO wrote:
Geeze, you give people an appetizer and they want a 5 course meal!
With the holiday weekend coming up (plus taking next week completely off from work for a break and so I can hit Fan Fest) I was planning on finally buckling down and getting this done (at least in prototype form). Right now, my plans are to include:
- Schematic lookup (displays required resources/components when selecting a food/drink name). Not really glamorous, but the data is going to be needed for other pieces, so I figured it wouldn't be too difficult to add.
- Experimental percentage calculations (basically what that last spreadsheet does). It would have the food stats in addition to the raw percentages. This might even include a "crafting simulator" where you can allocate points into the different categories and see what the final result would be (although dealing with different success types might be a bit difficult).
- Resource comparison. Similar to the percentage calculations, but allowing the user to enter multiple types of a resource to see how that effects the final product. This would probably be limited to a single schematic slot, comparing the various results of combining 3 different berries with 4 different fruits would get a bit daunting.
- Some sort of price calculator. I'm trying to lay something out so subcomponents are easier to include.
I've got a rough design sketched out, although I'm still up in the air on the data storage. A database might be overkill, maybe something along the lines of an XML document would be enough. Although that would probably require loading all the data into memory at once, as opposed to getting it as needed from the database...
I will check back in later with a progress report.
I think doing the application via database, would lend for future use towards other crafting trees... Once all the code is in, and if its generic enuff to be controlled by the database... adding say doctor crafting to the application would be easy.
Schematic lookup (displays required resources/components when selecting a food/drink name). Not really glamorous, but the data is going to be needed for other pieces, so I figured it wouldn't be too difficult to add.
Pretty easily done with database queries, plus the same database could be used to create the "forms" for filling in resource stats.
Experimental percentage calculations (basically what that last spreadsheet does). It would have the food stats in addition to the raw percentages. This might even include a "crafting simulator" where you can allocate points into the different categories and see what the final result would be (although dealing with different success types might be a bit difficult).
The only part thats a challenge here for design is determining the exact formulas which I'm sure you already have, however also determining if the formula works for expanded applications (ie doc crafting).
The simulator was something I was thinking about today, it would be interesting to figure out the formulas for experimentation successes, and calculate the actual % you would have given inputed variables such as research center, bespin bonus, and soon FS crafting bonus to produce certain stats. So maybe rather than just a simulator, allow the user to allocate his points (10-12) and produce a chance of achieving certain stats. Or allow the user to just input desired stats... brandy for example:
nutrition 420
flavor 45 minutes
filling 49
uses 21
I would think code could be written to determine the % of achieving the stats, and possible the needed point allocation and needed success type.
Resource comparison. Similar to the percentage calculations, but allowing the user to enter multiple types of a resource to see how that effects the final product. This would probably be limited to a single schematic slot, comparing the various results of combining 3 different berries with 4 different fruits would get a bit daunting.
While I like the idea as possibly something to expand into, the app would/should allow the user to figure this out by possibly running it in say 3 seperate browsers.
Some sort of price calculator. I'm trying to lay something out so subcomponents are easier to include.
This would be fairly easy to do, you could always just allow for a CPU input on the resource input form, that is not required... and it produces a cost per item/crate.
Something that might be very useful as well when building this app, is to include the BE additive schematics in the database (if you descide to use a db) since I know alot of chef's either make thier own, or supply a BE with the resources and get a schematic made.
I read your post in where you linked to your excel spreadsheet, and was bummed it sounded like you no longer wanted to take on this project. I actually began to start designing it myself, but I'm glad you descided to stick with it... I think this would be extremly useful to chefs, and if it uses a database to generate its forms, and input I would think it could easily be expanded to other crafter types.
HavocDroid wrote:
Sounds like a good idea. In my opinion, PHP & MySQL would be the way to go. A database is expandable, once you have the basic system working, you can add data and make it work for other professions.Things like swgcraft data can also be loaded into a MySQL database through a simple parser script, allowing you to do whatever you need to it.
Yes another great idea if we wanted to think about exanding this into a great chef site is a script to parse thru all the swgcraft resources and display the ones that pertain to cef assigning them values based upon thier stats and how they relate to chef schematics.
Elmmx-5 wrote:
A small part of the code, yes. But if you never get that right what do you have? To me it seems you'd end up with another version of swgcraft. I apologize if I misunderstood the scope of this, but what exactly do you envision this doing? Even if you build the schematics in as a lookup, how will that be of help if you can't accurately see what the end result will be? How will you handle some chef's preferences to say make canape with max nutrition while others make 33 fill, just a standardized weighting system?
Ok well lets all get together, and descide on 1 schematic... (something with decimal places is probably most accurate, bivoli, vegeparsin, pyro, something along those lines..) post our resource stats...initial assmelby... and maximum %. This wouldn't be very difficult to take 5+ results and test it against someone's formula.
As for chef's personal choices on filling vs nutrition etc it has been mentioned here to produce some sort of simulation crafting code... So instead of pointing fingers and accusing others of having a lack of intrest why dont you creat a post, heck link it in this post... and descide on a schematic or 2, and determine what variable and results you want/need to test against a formula and lets do it.Your attitude towards the entire thing does not seem to be as constructive, and positive as it could be... rather than blanket statements like people don't care, why don't you come up with a way to prove/disprove the formula and ask people for help with your theory.