search

MechOrigin / NTC2

9 stars 10 forks source link

[1.4.9b] Osmium not spawning in The End #102

Closed Timeslice42 closed 2 years ago

Timeslice42 commented 2 years ago

I have killed the dragon and flown around with the scanner for an hour or two and no osmium has spawned. The JEI tip for Emendates Enigmatica indicates that it should be spawning, but there's nothing.

In an (un?)related issue, I noticed that the laser ore drill entry for osmium, it has every biome in The End blacklisted. Could this be indirectly related?

Daykauz commented 2 years ago

Salut , j'ai le même problème , en plus de ça aucun petit portail n'apparait , si quelqu'un a une solution je suis preneur merci

Dasffion commented 2 years ago

Osmium is extremely rare. Extremely. To make up for this when you do find it you’ll get around 1000 clusters, which are 4 chunks each, which can then be processed further.

Daykauz, English will be easier to answer as the modpack author speaks English. I ran it through google translate though and if you’re not getting the little portals then you haven’t killed the ender dragon.

Daykauz commented 2 years ago

hello, I am sending you this video to prove to you that we have indeed killed the dragon? but no small portal appears, a bug?

video link :https://www.youtube.com/watch?v=D3UFZyZxhzE

thanks

Le sam. 2 juil. 2022 à 04:44, Dasffion @.***> a écrit :

Osmium is extremely rare. Extremely. To make up for this when you do find it you’ll get around 1000 clusters, which are 4 chunks each, which can then be processed further.

Daykauz, English will be easier to answer as the modpack author speaks English. I ran it through google translate though and if you’re not getting the little portals then you haven’t killed the ender dragon.

— Reply to this email directly, view it on GitHub https://github.com/MechOrigin/NTC2/issues/102#issuecomment-1172819104, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZ4HN3GGKB4ZBRVSYUUYSCDVR6UHLANCNFSM52EHHAVQ . You are receiving this because you commented.Message ID: @.***>

Timeslice42 commented 2 years ago

I feel this issue has been sufficiently addressed in 1.5.x, so I'm closing the issue.