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

Dimension maintenance cost wrong #63

Closed
Pandemoneus opened this issue Feb 24, 2015 · 8 comments
Closed

Dimension maintenance cost wrong #63

Pandemoneus opened this issue Feb 24, 2015 · 8 comments

Comments

@Pandemoneus
Copy link

In the Infinity 1.2.0 pack, I tried making a dimension using (in this order):

  • Biome Deep Ocean
  • Liquid Gelid Cryotheum
  • Terrain Flat
  • Controller Single

The Gelid Cryotheum dimlet has a maintenance cost of 20k RF/t according to the tooltip.
However, the fully created dimension has a specified maintenance cost of 200k RF/t (Note, it's x10!).
There's something wrong there.

@McJty
Copy link
Collaborator

McJty commented Feb 24, 2015

Note that the cost can increase after creation due to random generated features. But 200kRF/t is a lot though. Can you tell me what the dimension was created with? i.e. shift-right click with the dimension tab and paste all the information you get here.

@Pandemoneus
Copy link
Author

See this screenshot:
http://imgur.com/D5XRMFX

And this one for the power cost:
http://imgur.com/QuvNzor

@McJty
Copy link
Collaborator

McJty commented Feb 24, 2015

Ok, that doesn't look as if it should be that expensive. I will look into this and see what's the problem here.

@McJty
Copy link
Collaborator

McJty commented Feb 24, 2015

Ah oops no. This is actually normal (although a bit excessive). Material and liquid modifiers cost 10 times more when used as a terrain modifier (as opposed to using them as a feature modifier like lakes or tendrils). The reasoning is that there is a lot more of it when used like that.

@Pandemoneus
Copy link
Author

Ah. That should be mentioned in the manual. :)

@McJty
Copy link
Collaborator

McJty commented Feb 24, 2015

Yes, and for that reason I will reopen this so that I can make the manual more clear. Thanks for reporting.

@McJty McJty reopened this Feb 24, 2015
@a-rat-girl
Copy link
Contributor

Oh, I'm working on the manual now. I can write that in.

@McJty
Copy link
Collaborator

McJty commented Feb 25, 2015

Manual is updated for next release

@McJty McJty closed this as completed Feb 25, 2015
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

3 participants