-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Prospecting #43
Comments
Some random thoughts: One thing I've learned from using the shared spreadsheet: The commonest 4 To me the most valuable information is details on the single rarest item Another thing the spreadsheet has taught me: quantities are fairly One other piece of data I would find useful: terrain difficulty. That is, Btw, I've mentioned the spreadsheet quite a bit. It has been useful but I
|
I think we will start with it simple. Still debating with myself if add numbers of materials or just a check-box Only a check box is needed but numbers foung might be more fun. 2016-01-01 16:32 GMT+01:00 Greg Malcolm notifications@github.com:
|
Already came up in conversation on Skype earlier, but to reiterate for the record, I think checkbox is the more useful option. But saving the backend data as an integer might give you more leeway to change your mind later (using 0 and 1 for checkbox values). That probably wouldn't be hard to upgrade the database from binary to integer data, so my suggestion is perhaps breaking the YAGNI rule... :D |
Ooh, brilliant! Does EDDB store that data or will it be local data only? Mark Jelic
|
Certainly gravity would be good to know as that can determine the type of skip you can take fun there. But certainly just a pop-up page of checkboxes for the materials will do. No need for quantities etc. Mark Jelic
|
I vote just checkboxes. Mark Jelic
|
CREATE TABLE "Objects" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL UNIQUE , "SystemName" TEXT NOT NULL , "ObjectName" TEXT NOT NULL , "ObjectType" INTEGER NOT NULL , "Gravity" FLOAT, "Terrain" INTEGER, "C" BOOL, "Fe" BOOL, "Ni" BOOL, "P" BOOL, "S" BOOL, "As" BOOL, "Cr" BOOL, "Ge" BOOL, "Mn" BOOL, "Se" BOOL NOT NULL , "V" BOOL, "Zn" BOOL, "Zr" BOOL, "Cd" BOOL, "Hg" BOOL, "Mo" BOOL, "Nb" BOOL, "Sn" BOOL, "W" BOOL, "Sb" BOOL, "Po" BOOL, "Ru" BOOL, "Tc" BOOL, "Te" BOOL, "Y" BOOL) Or should we change to int for possible counting? Not that i think we will use it now |
Updated with Commander och updatetime. CREATE TABLE "Objects" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL UNIQUE , "SystemName" TEXT NOT NULL , "ObjectName" TEXT NOT NULL , "ObjectType" INTEGER NOT NULL , "Gravity" FLOAT, "Terrain" INTEGER, "C" BOOL, "Fe" BOOL, "Ni" BOOL, "P" BOOL, "S" BOOL, "As" BOOL, "Cr" BOOL, "Ge" BOOL, "Mn" BOOL, "Se" BOOL NOT NULL , "V" BOOL, "Zn" BOOL, "Zr" BOOL, "Cd" BOOL, "Hg" BOOL, "Mo" BOOL, "Nb" BOOL, "Sn" BOOL, "W" BOOL, "Sb" BOOL, "Po" BOOL, "Ru" BOOL, "Tc" BOOL, "Te" BOOL, "Y" BOOL, "Commander" Text, "UpdateTime" DATETIME ) |
I'd like to suggest that the prospecting tool include planetary rings and asteroid belts. I've contacted gregmalcolm about adding this into EDMaterializer. I have found a number of "Material Content: High" asteroids in some planetary rings where the materials can be mined. |
Heh heh, yeah I will not roll out a v5 api interface for EDM at some point to cope with this. It means stars are now prospectable. Although probably doesn't happen much |
Is this idea dead in the water? |
prospecting part will be dead in water after 2.2 but the viewing of it will 2016-07-30 10:02 GMT+02:00 robbyxp1 notifications@github.com:
|
Superceeded by 2.2 ED |
Add a may to record prospecting of minerals.
And a way to view known planets with minerals you wants.
The text was updated successfully, but these errors were encountered: