Skip to content
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

When you morph unobtanium to Gems in capital planet it becomes level 0 and can't be upgraded #65

Open
afwbkbc opened this issue Oct 12, 2018 · 4 comments

Comments

@afwbkbc
Copy link

afwbkbc commented Oct 12, 2018

See screenshot: http://dump.bitcheese.net/files/donusyj/gems.png

@DaloLorn
Copy link
Contributor

DaloLorn commented Oct 13, 2018

Working as intended, I think. You're not supposed to waste your homeworld's Unobtanium on something as insignificant as Gems.

In my opinion, you should hold on to it until you get a scalable, or at least a level 3 resource.

@l29ah
Copy link
Contributor

l29ah commented Oct 13, 2018

What about the unique level0 resources? They're quite valuable, yet i think they would fuck the homeworld up as well.

@jonesmz
Copy link

jonesmz commented Oct 13, 2018

If I can make a guess

The bug isn't that you can convert your home world to gems.

The bug is that doing so prevents you from leveling the planet up ever again.

If your not supposed to be able to level the planet up again, then there should be 1) a warning popup before morphing. And 2) text in the planet view explaining why you can't level the planet up.

@DaloLorn
Copy link
Contributor

DaloLorn commented Oct 14, 2018

If I can make a guess
The bug isn't that you can convert your home world to gems.
The bug is that doing so prevents you from leveling the planet up ever again.
If your not supposed to be able to level the planet up again, then there should be 1) a warning popup before morphing. And 2) text in the planet view explaining why you can't level the planet up.

Oh, I understood it perfectly the first time around. My answer stands - probably working as intended, and go scalable/T3 or bust.

I do agree that this should be more visible without digging through the files, but that wasn't the first thing I thought when I saw this issue. (Also, I'm currently in no state to be changing things like these.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants