denseores's People
Forkers
vexatos thevikingwarrior bonii-xx trade12 iactu captainclyde bboldt orondf343 tmtravlr kuenzign jermangarc nalimleinad skilande leon1236 vykor howrie smbarbour dragonslover shoxz sasikaa svangen madsmith jamesphenry robijnvogel maegnustheblackmage scolby33 arukaalter allanf181 whichonespink44 daniel6899 searge-dp kryptoncaptain heufneutje yrsegal tommsy64 deathdude181 dorzar tencao josephcsible managarmr719 iamgoofball toberumono regonizer lemonnekogh teamsevered jonab03 alasdairh3denseores's Issues
Crash Initialing game
using version 1.4.1
YelloriumOre
Here's config i've made. It shows in NEI but it's got the black/purple default texture. Until there is proper one somehow i'm gonna copy texture name from dense gold (S:baseBlockTexture=gold_ore).
block_57 {
S:baseBlock=BigReactors:YelloriteOre
I:baseBlockMeta=0
S:baseBlockTexture=BigReactors:YelloriteOre
D:denseOreProbability=1
I:renderType=1
I:retroGenID=1
S:underlyingBlock=stone
}
For someone wondering how i found out BigReactors:YelloriteOre, give yourself OP ingame, and type
/give YourIngamename bigreactors: and hit tab key to let it auto-complete with right caps.
Texture PermaCache
I was wondering if there is a way to perma-cache the generated textures, to speed up client load time after the first start, or even right away if a pack creator generates the textures in advance?
Want one Dense Ore Block
config: nestable groups
Example time:
(the idea came to me while i was typing block_55
. I don't want others to run out of key-presses either.)
# Configuration file
ores {
block_0 {
S:baseBlock=minecraft:iron_ore
I:baseBlockMeta=0
S:baseBlockTexture=iron_ore
D:denseOreProbability=1.0
I:renderType=0
I:retroGenId=0
S:underlyingBlock=stone
}
}
groups {
blocks_0 {
S:baseBlock=minecraft:gold_ore
I:baseBlockMeta=0
S:baseBlockTexture=gold_ore
D:denseOreProbability=1.0
I:renderType=0
I:retroGenId=0
S:underlyingBlock=stone,netherrrack,endstone
block_0 {
S:baseBlock=minecraft:quartz_ore
I:baseBlockMeta=0
S:baseBlockTexture=quartz_ore
D:denseOreProbability=1.0
I:renderType=0
I:retroGenId=0
S:underlyingBlock=netherrack
}
block_1 {
S:baseBlock=minecraft:gold_ore
I:baseBlockMeta=0
S:baseBlockTexture=gold_ore
D:denseOreProbability=1.0
I:renderType=0
I:retroGenId=0
S:underlyingBlock=stone
}
block_2 {
S:baseBlock=minecraft:lapis_ore
S:baseBlockTexture=lapis_ore
}
block_3 {
S:baseBlock=minecraft:diamond_ore
S:baseBlockTexture=diamond_ore
}
block_4 {
S:baseBlock=minecraft:emerald_ore
S:baseBlockTexture=emerald_ore
}
block_5 {
S:baseBlock=minecraft:redstone_ore
S:baseBlockTexture=redstone_ore
}
block_6 {
S:baseBlock=minecraft:coal_ore
S:baseBlockTexture=coal_ore
}
}
blocks_1 {
I:baseBlockMeta=0
D:denseOreProbability=1.0
I:renderType=1
I:retroGenId=0
S:underlyingBlock=stone,netherrack,endstone
block_0 {
S:baseBlock=appliedenergistics2:tile.OreQuartz
S:baseBlockTexture=appliedenergistics2:OreQuartz
}
block_1 {
S:baseBlock=appliedenergistics2:tile.OreQuartzCharged
S:baseBlockTexture=appliedenergistics2:OreQuartzCharged
}
}
blocks_2 {
S:baseBlock=BiomesOPlenty:gemOre
D:denseOreProbability=1.0
I:renderType=1
I:retroGenId=0
S:underlyingBlock=stone,netherrack,endstone
block_0 {
I:baseBlockMeta=2
S:baseBlockTexture=biomesoplenty:rubyore
}
block_1 {
I:baseBlockMeta=4
S:baseBlockTexture=biomesoplenty:peridotore
}
block_2 {
I:baseBlockMeta=6
S:baseBlockTexture=biomesoplenty:topazore
}
block_3 {
I:baseBlockMeta=8
S:baseBlockTexture=biomesoplenty:tanzaniteore
}
block_4 {
I:baseBlockMeta=10
S:baseBlockTexture=biomesoplenty:malachiteore
}
block_5 {
I:baseBlockMeta=12
S:baseBlockTexture=biomesoplenty:sapphireore
}
}
}
Also notice the gold and nether quart was completely typed out, this would allow copy and pasties into the new format with no problems.
Also note that BOP uses the same name, and look at how setting defaults for groupings would help.
This example would have all the vanilla overworld ores (coal is an ore now, limiting iron ore) dense versions to spawn in netherrack and endstone. as well as a few other adjustments.
Example RenderType guide?
While messing with the new render type, I decided to make myself a bit of a guide, would it be of any use to you?
[Request] ProjectRed Ores Example Config
Can you please update the ProjectRed Example Configs? ProjectRed added 4 new ores beside Ruby, Sapphire & Peridot: Copper, Tin, Silver, Electrotine.
Thanks!
EDIT: And they also changed the names of the ore textures if I saw right.
Texture Pack Crash
When i try to use Sphax Thermal Foundation 64x patch it crashes my game with the following error..
Actually not a bug
Hi,
I "programmed" dense ores for nevermine. U could add the following to
https://github.com/rwtema/DenseOres/tree/master/example_configs/mods
Example Config File
Make sure to replace block_X with a proper number
ores {
block_X {
S:baseBlock=nevermine:oreLimonite
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreLimonite
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=stone
}
block_X {
S:baseBlock=nevermine:oreAmethyst
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreAmethyst
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=stone
}
block_X {
S:baseBlock=nevermine:oreCrystallite
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreCrystallite
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stoneHaven
}
block_X {
S:baseBlock=nevermine:oreChestFragments
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreChestFragments
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stonePrecasiaLow
}
block_X {
S:baseBlock=nevermine:oreEmberstone
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreEmberstone
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=netherrack
}
block_X {
S:baseBlock=nevermine:oreFootFragments
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreFootFragments
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stonePrecasiaLow
}
block_X {
S:baseBlock=nevermine:oreJade
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreJade
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=stone
}
block_X {
S:baseBlock=nevermine:oreLegFragments
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreLegFragments
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stonePrecasiaLow
}
block_X {
S:baseBlock=nevermine:oreRosite
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreRosite
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=stone
}
block_X {
S:baseBlock=nevermine:oreSapphire
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreSapphire
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=stone
}
block_X {
S:baseBlock=nevermine:oreSkullFragments
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreSkullFragments
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stonePrecasiaLow
}
block_X {
S:baseBlock=nevermine:oreGhastly
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreGhastly
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stoneGreckon
}
block_X {
S:baseBlock=nevermine:oreGhoulish
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreGhoulish
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stoneGreckon
}
block_X {
S:baseBlock=nevermine:oreVarsium
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreVarsium
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:baronStone
}
block_X {
S:baseBlock=nevermine:oreElacanium
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreElacanium
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:baronStone
}
block_X {
S:baseBlock=nevermine:oreBaronyte
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreBaronyte
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:baronStone
}
block_X {
S:baseBlock=nevermine:oreRunium
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreRunium
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=stone
}
block_XX {
S:baseBlock=nevermine:oreChargedRunium
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreChargedRunium
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:deeplandsRock
}
block_X {
S:baseBlock=nevermine:oreBlazium
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreBlazium
I:denseOreProbability=1
I:renderType=2
I:retroGenID=0
S:underlyingBlock=nevermine:barathosHellstone
}
block_X {
S:baseBlock=nevermine:oreLyon
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreLyon
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stoneIromine
}
block_X {
S:baseBlock=nevermine:oreMystite
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreMystite
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stoneMysterium
}
block_X {
S:baseBlock=nevermine:oreBloodstone
I:baseBlockMeta=0
S:baseBlockTexture=nevermine:oreBloodstone
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=nevermine:stoneAbyss
}
}
RetroGen causing crashes (OutOfMemoryError) when running EnderPump
java.lang.OutOfMemoryError: Java heap space
at com.rwtema.denseores.WorldGenOres.retroGenSave(WorldGenOres.java:86)
at cpw.mods.fml.common.eventhandler.ASMEventHandler_390_WorldGenOres_retroGenSave_Save.invoke(.dynamic)
at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:51)
at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:122)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.func_75816_a(AnvilChunkLoader.java:126)
at net.minecraft.world.gen.ChunkProviderServer.func_73242_b(ChunkProviderServer.java:203)
at net.minecraft.world.gen.ChunkProviderServer.func_73156_b(ChunkProviderServer.java:286)
at net.minecraft.world.WorldServer.func_72835_b(WorldServer.java:164)
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:609)
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:326)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:531)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:414)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:669)
A detailed walkthrough of the error, its code path and all known details is as follows:
-- Head --
Stacktrace:
at com.rwtema.denseores.WorldGenOres.retroGenSave(WorldGenOres.java:86)
at cpw.mods.fml.common.eventhandler.ASMEventHandler_390_WorldGenOres_retroGenSave_Save.invoke(.dynamic)
at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:51)
at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:122)
at net.minecraft.world.chunk.storage.AnvilChunkLoader.func_75816_a(AnvilChunkLoader.java:126)
at net.minecraft.world.gen.ChunkProviderServer.func_73242_b(ChunkProviderServer.java:203)
at net.minecraft.world.gen.ChunkProviderServer.func_73156_b(ChunkProviderServer.java:286)
at net.minecraft.world.WorldServer.func_72835_b(WorldServer.java:164)
-- Affected level --
Details:
Level name: world
All players: 0 total; []
Chunk stats: ServerChunkCache: 28 Drop: 2
Level seed: 2434036188922274986
Level generator: ID 00 - default, ver 1. Features enabled: false
Level generator options:
Level spawn location: World: (0,0,0), Chunk: (at 0,0,0 in 0,0; contains blocks 0,0,0 to 15,255,15), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Level time: 0 game time, 0 day time
Level dimension: 0
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:609)
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:326)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:531)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:414)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:669)
-- System Details --
Details:
Minecraft Version: 1.7.2
Operating System: Linux (amd64) version 2.6.32-431.11.2.el6.x86_64
Java Version: 1.7.0_55, Oracle Corporation
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 32064 bytes (0 MB) / 6372720640 bytes (6077 MB) up to 6372720640 bytes (6077 MB)
JVM Flags: 4 total; -Xmx6G -Xms4G -XX:MaxPermSize=512m -Xincgc
AABB Pool Size: 1596 (89376 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
IntCache: cache: 0, tcache: 2, allocated: 17, tallocated: 96
FML: ERROR OutOfMemoryError: Java heap space
AE2 Version: stable rv0-stable-4 for Forge 10.12.0.1024
Mantle Environment: Environment healthy.
TConstruct Environment: Environment healthy.
AE2 Integration: RotaryCraft:OFF, IC2:ON, RC:ON, BC:ON, MJ5:ON, MJ6:ON, RF:ON, RFItem:ON, MFR:OFF, DSU:ON, FZ:ON, CLApi:OFF, RB:OFF, FMP:ON
Profiler Position: N/A (disabled)
Vec3 Pool Size: 1123 (62888 bytes; 0 MB) allocated, 1109 (62104 bytes; 0 MB) used
Player Count: 0 / 20; []
Is Modded: Definitely; Server brand changed to 'fml,forge'
Type: Dedicated Server (map_server.txt)
DenseOre class, getSmeltingRecipe method: smelt field not being initialized
Not a bug that I am experiencing, but I have been reading through the code trying to learn how this mod works, and I noticed that in the getSmeltingRecipe method of DenseOre class, the smelt field is being returned if initSmelt is true, however, it looks like the smelt field is never initialized. When you run through the first pass through getSmeltingRecipe, initSmelt is set to true, and there is an ItemStack generated and returned, but smelt is never set.
I'm sure this isn't what was intended, but not sure if it will ever cause a bug (will getSmeltingRecipe ever be called more than once?)
Issue generating TC4 infused stone blocks
I was trying to add infused stone to dense ores. You know the ones from ThaumCraft 4. When I load up the config I wrote for TC4 the only ores that work are Cinnibar and Amber which have static textures. The infused stone just shows the "missing texture" texture and I do not see it generating anywhere in the world. I attached the config I made, I was hoping you might be able to determine why it wont work. all of the other mods works and even parts of TC4 just not the infused stone.
Thanks in advance...
Configuration file
ores {
block_8 {
S:baseBlock=Thaumcraft:blockCustomOre
I:baseBlockMeta=0
S:baseBlockTexture=thaumcraft:cinnibar
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
I:retroGenId=0
S:underlyingBlock=stone
}
block_9 {
S:baseBlock=Thaumcraft:blockCustomOre
I:baseBlockMeta=1
S:baseBlockTexture=thaumcraft:infusedorestone
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
I:retroGenId=0
S:underlyingBlock=stone
}
block_10 {
S:baseBlock=Thaumcraft:blockCustomOre
I:baseBlockMeta=2
S:baseBlockTexture=thaumcraft:infusedorestone
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
I:retroGenId=0
S:underlyingBlock=stone
}
block_11 {
S:baseBlock=Thaumcraft:blockCustomOre
I:baseBlockMeta=3
S:baseBlockTexture=thaumcraft:infusedorestone
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
I:retroGenId=0
S:underlyingBlock=stone
}
block_12 {
S:baseBlock=Thaumcraft:blockCustomOre
I:baseBlockMeta=4
S:baseBlockTexture=thaumcraft:infusedorestone
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
I:retroGenId=0
S:underlyingBlock=stone
}
block_13 {
S:baseBlock=Thaumcraft:blockCustomOre
I:baseBlockMeta=5
S:baseBlockTexture=thaumcraft:infusedorestone
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
I:retroGenId=0
S:underlyingBlock=stone
}
block_14 {
S:baseBlock=Thaumcraft:blockCustomOre
I:baseBlockMeta=6
S:baseBlockTexture=thaumcraft:infusedorestone
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
I:retroGenId=0
S:underlyingBlock=stone
}
block_15 {
S:baseBlock=Thaumcraft:blockCustomOre
I:baseBlockMeta=7
S:baseBlockTexture=thaumcraft:amberore
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
I:retroGenId=0
S:underlyingBlock=stone
}
}
Allow for ores with particle effects
There are a few ores now that have particle/animation effects on them.
The list, as I am aware, is as follows:
Redstone (also animated, so that should be mentioned)
Charged Certus Quartz (which comes with its own challenges, along with Certus Quartz, see Issue #10
Eximite
Meutoite
Carmot
Mithril
Orichalcum
Adamantine
Atlarus
Midasium
Vyroxeres
Ceruclase
Kalendrite
Vulcanite
Sanguinite
It would be awesome if we had support for the particle/animation effects in future versions :)
Osmium from not "dense-ore-able"
I think it's because it has a 32x32 texture instead of 16x16, any thoughts?
my code:
block_20 {
S:baseBlock=Mekanism:OreBlock
I:baseBlockMeta=0
S:baseBlockTexture=mekanism:OsmiumOre
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
I:retroGenId=0
S:underlyingBlock=stone
}
Possible expanded feature
As of today, Railcraft has been updated to 1.7.10. I was going to add an example config for the ores from railcraft, but the dark ores use an underlyingBlock of abyssal stone, which is not in the vanilla textures. I was thinking that instead of the way underlyingBlock is right now, maybe you could make it similar to baseBlockTexture. For example: "S:underlyingBlock=minecraft:stone" for stone or "S:underlyingBlock=railcraft:cube.stone.abyssal" for abyssal stone. It uses the mod's texture folder name, then a colon, and then the texture .png name. Just some food for thought.
config: listable elements
I started with a simple idea, and by the time I finished typing, I came up with a second idea...
block_48 {
S:baseBlock=NetherOres:tile.netherores.ore.1
I:baseBlockMeta=15
S:baseBlockTexture=netherores:Magnesium
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=stone,endstone,sandstone:1,netherrack
}
What I would like is being about to say S:underlyingBlock=stone,netherrack
or S:underlyingBlock=sandstone:1,netherrack
and turn that to an array separated from commas. This way you can generate all the netherores in the overworld, or if you make a mining world (miner's paradise) out of sandstone:1 then it generates ;)
You could also change the format all together to something like this
(I ended up splitting my ideas into separate config issues/enhancments)
Dense Osmium not being generated
I tried making a dense osmium ore and even though as far as I can tell I've made the configuration correctly, it fails to generate the block ingame. It's not even making a block with a broken texture, it just won't show up in NEI. What's even weirder is the config doesn't remove the block definition, which would tell me I made it correctly, or else it just removes it, right? Anyway, here's what I've done for the config, maybe you can find something I did wrong.
block_X {
S:baseBlock=Mekanism:OreBlock
I:baseBlockMeta=0
S:baseBlockTexture=mekanism:OsmiumOre
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=stone
}
I'm using Dense Ores v1.4.2 and Mekanism v7.0.0.75
Missing Config
Tcon is missing aluminum can anyone post what is should be so i can please add it to my config .. thanks
Also can anyone post Quartz from AE2
Trouble adding dense ores.
For whatever reason, I have been unable to get dense ores (version 1.4.1) to recognize my configs for Galaticraft (including Galaticraft Planets), Mekanism, and Project:Red World. I have tested the configs for each mod individually without success. Instead, I get one "invalid ore."
http://pastebin.com/MHe9Mn67
Adding the use of denseOreProbability
Currently i have edited the ores i want to spawn down to one per cluster and many clusters but only a few get changed to dense ores.
Instead of all of them and thats the effect i'm looking for.
Thanks!
World Fails to Load with 1.6
Updated Dense Ores 1.5 to 1.6, and on trying to open a world it just returns to the main menu.
No specific crash log, but this โ http://pastebin.com/cu3cbDYG โ is the end of the log.
(I have the full log if you want it.)
Looking at the top of the stack trace, references to IC2 compat, and I do not have IC2.
vanilla ores ignore renderType setting
1.7.10 denseores 1.5 .
this does not work:
block_0 {
S:baseBlock=minecraft:iron_ore
I:baseBlockMeta=0
S:baseBlockTexture=iron_ore
D:denseOreProbability=1.0
I:renderType=6
I:retroGenId=0
S:underlyingBlock=stone
}
this does:
block_8 {
S:baseBlock=ThermalFoundation:Ore
I:baseBlockMeta=0
S:baseBlockTexture=thermalfoundation:ore/Ore_Copper
D:denseOreProbability=1
I:renderType=6
I:retroGenId=0
S:underlyingBlock=stone
}
Client Crash
Feature req: Cache textures by server/resource pack.
Currently dense ores generates the textures on every startup. It makes sense to generate them once and store them by resource pack so they can then just be loaded on startup rather than generated. I play on a server with a lot of mods, cutting any time at all off the startup process is very important when the startup time is reaching over 3 minutes.
textures-customs
How do we call the generated textures inside new blocks?
So for example I have a dense dense and dense dense dense ore. They all have the same texture atm because the have the same baseBlockTexture.
The code below produces this : http://puu.sh/cxoQW/409cead3cc.png
block_51 {
S:baseBlock=NetherOres:tile.netherores.ore.1
I:baseBlockMeta=15
S:baseBlockTexture=netherores:Magnesium
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=netherrack
}
block_52 {
S:baseBlock=denseores:block3
I:baseBlockMeta=4
S:baseBlockTexture=denseores:denseoreNetherMagnesium
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=netherrack
}
block_53 {
S:baseBlock=denseores:block3
I:baseBlockMeta=5
S:baseBlockTexture=denseores:denseoreMagnesium
D:denseOreProbability=1
I:renderType=0
I:retroGenID=0
S:underlyingBlock=netherrack
}
Dense Ores mimicing original ore's properties
I think it would be neat if the dense ores had the same properties as their original ores. For example, Tcon's gravel ores would make the gravel sound when stepped on, mined, and placed. They would also obey gravity and would be mined with a shovel instead of a pick. I'm not so sure how hard this would be to implement because they are multiblocks, but I believe it would add a lot to the mod.
Underground Biomes Support?
Is this even doable with how the ores are generated, without having to configure a dense ore version of every variation of ores and their base block type?
Would it be possible to generate the just overlay texture that, if I remember correctly is what you'd need to add compatibility for UB? That way it should just work and UB would take care of the variations themselves.
ambiguous recipe Error
Hello there,
I encountered an Issue with Dense Ores 1.6.1 on MC 1.7.10,
When another mod (like GregTech) overrides the ic2 recipes, one is unable to load a world:
http://pastebin.com/VE2UedUB
It would be nice to add config entries to disable certain recipes with the Denso Ores, so incompatibilities can be prevented.
Greetings
ultrasn0w
DenseOres crash on startup.
I'm seeing this on startup. I pull DenseOres and forge starts just fine.
I love this mod, btw, it's really clever and makes mining interesting!
[Dense Ores 1.6.1] Crash on loading
I crash on loading with the following crash log: http://paste.ee/p/AsQPd
The relevant lines seem to be:
Caused by: java.lang.NoClassDefFoundError: ic2/api/recipe/IRecipeInput
at com.rwtema.denseores.modintegration.ModIntegration.(ModIntegration.java:19)
at com.rwtema.denseores.DenseOresMod.init(DenseOresMod.java:37)
I do not have IC2 installed.
Crash during what appears to be retrogen
Game crashes on a world that used version 1.3, but was updated to 1.4 along with the config. It appears to be conflicting with Natura during retrogen. I created a fresh world and had no problems, but when I tried a world that I've been using before 1.4 to test mods, it crashes.
Crash report:
http://openeye.openmods.info/crashes/3ea7274cea2bfc8c0576f4d64c32bb30
[Enhancement] Ore Dictionary for any Ores
It would be sweet if that is possible to do.
ore you could just add in dense versions of Copper, Zinc, Tin, etc. but only have them activate and generate if "some mod" is installed.
Can't get into any world with Thermal Foundation Dense Ores
I can only get into any world with deleting the Thermal Foundation / Expansion dense ores (I mean removing from the config). It has to do something with Thaumcraft as I saw.
Thanks for the help!
Refusing to read texture from resource pack
Forgive me if I'm understanding the config incorrectly, first of all.
I have this as an entry for Ignis Infused Stone, attempting to lead dense ores to generate the texture based upon a flat, still image I've haphazardly put together rather than the textures used to create the animated look they have ingame.
The directory of the texture itself is, from the root of the resource pack, \assets\minecraft\textures\blocks\InfusedOreIgnis.png
block_46 {
S:baseBlock=Thaumcraft:blockCustomOre
I:baseBlockMeta=2
S:baseBlockTexture=minecraft:InfusedOreIgnis
D:denseOreProbability=1
I:renderType=2
I:retroGenID=1
S:underlyingBlock=stone
}
I was hoping this'd work as I'm already including a resource pack consisting of a few additional images for the sake of custom research added through minetweaker, but either it's refusing to read the texture, I've got the baseBlockTexture setup incorrectly, or it doesn't do what I think it does despite it working appropriately when I told it to use iron ore texture.
Oh, whoops, apparently it's a texture size difference between baseBlockTexture and underlyingBlock which is both known and unfixable.
Worlds wont load
Whene i load a world it just go's back too the main minecraft screen.
denseores 1.6.1/1.6.2
Allso whene i removed thaumcraft and addons the worlds load just fine.
More flexible configs?
The method of adding ores to the config is a bit weird for now... At this point, we have to know both the name the block is registered under in the mods code (a potential problem for either closed-source or metadata ores) and the filename of the texture used (not as problematic, necessarily, but certainly not convenient).
It seems like a few people have spoken up about automatic ore dictionary scanning. I would say this, plus a blacklist option, might be the best, but maybe even allowing us to just use block IDs?
Server crashes with Thaumcraft and MFR (Compat Thaumcraft)
I have no idea if Dense Ores itself is having an issue or is just crying to the side, but here goes:
Forge: b1401 Server Edition
MFR: 2.8.0-104 for 1.7.10
Thaumcraft: 4.2.3.5 for 1.7.10
Dense Ores: 1.6.2 for 1.7.10
And a Pastebin full of modlist and stack trace. The mod list lists FastCraft as being installed, however I've also tested it without to the same effect.
I've raised this issue up elsewhere - azanor/Thaumcraft#1805 and CoFH/Feedback#604. I realize my mods aren't fully up-to-date, but since it seems even the newer versions are reported in the CoFH issue, I figured I might as well report anyway.
Useful notes: The issue only seems to be instigated (right word?) when new chunks are being genned, and even then it's a rare occurrence per-chunk. A recent attempt to start the server netted me a few problem mods - namely Thaumcraft complaining about both MFR and Dense Ores; stacktraces pasted into the Thaumcraft issue give a little more detail.
When underlyingBlock & baseBlockTexture are different resolutions, textures don't work
One example of this is Big Reactors.
The baseBlockTexture is bigreactors:oreYellorite, which is at 32x for some reason.
The underlyingBlock should be stone, which is 16x. When you try that it gives you the purple/black missing texture ingame.
If I set the underlyingBlock to be the same as the baseBlockTexture, it does render ingame, but it doesn't have any of the fancy effects.
block_X {
S:baseBlock=BigReactors:YelloriteOre
I:baseBlockMeta=0
S:baseBlockTexture=bigreactors:oreYellorite
D:denseOreProbability=1
I:renderType=0
I:retroGenID=1
S:underlyingBlock=bigreactors:oreYellorite
}
This different resolution thing also effects mods like Galacticraft, it probably effects Thaumcraft as well because I know those infused ore textures are 32x with a base of stone which is normally 16x.
Textures not displaying correctly
I'm running into some issues getting this to work with certain ores. I may be doing it wrong, but just in case I'm not, I figured I'd post what my config is here along with some screenshots of what blocks were created in case something isn't working correctly.
I'm using version 1.1 (1.0 was worse, for reference) of dense ores, version 4.0.2.5 of Metallurgy, and version 2.0.0.833 of Biomes O' Plenty. The problem I'm having is the texture generation seems to go awry when trying to create dense versions of Metallurgy ores.
Here is my config: http://pastebin.com/9z0byVB4
And here are some of the results:
https://imgur.com/a/eJ2R5
Some had completely broken textures, some had discoloration issues, some only seemed to rotate once. Oddly enough, not every ore broke, and even ores from the same mod sometimes worked, yet I didn't configure them any differently (to my knowledge at least) so I don't understand what could go wrong. Am I just doing something wrong? Or is there something conflicting with the base stone/end_stone/netherrack and the ores in question? If so, is there anything I can do to alleviate the issue?
Dense Ores never loads (1.8-1.4.2)
No world gen or blocks in creative/NEI found. Not included in the mods list on the title screen. When seraching "Dense" in the FML logs these are the 8 lines found
[14:55:10] [main/DEBUG] [FML/]: Examining for coremod candidacy denseores-1.4.2.jar
[14:55:10] [main/DEBUG] [FML/]: Not found coremod data in denseores-1.4.2.jar
[14:55:17] [main/INFO] [LiteLoader/]: Inspecting jar metadata in 'denseores-1.4.2.jar'
[14:55:17] [main/INFO] [LiteLoader/]: Ignoring C:\Users\Mitch\AppData\Roaming.minecraft\mods\denseores-1.4.2.jar
[14:55:47] [Client thread/DEBUG] [FML/]: Found a candidate zip or jar file denseores-1.4.2.jar
[14:55:58] [Client thread/DEBUG] [FML/]: Examining file denseores-1.4.2.jar for potential mods
[14:55:58] [Client thread/TRACE] [FML/]: Located mcmod.info file in file denseores-1.4.2.jar
[14:55:59] [Client thread/INFO] [FML/]: FML has found a non-mod file denseores-1.4.2.jar in your mods directory. It will now be injected into your classpath. This could severe stability issues, it should be removed if possible.
Forge version: 11.14.0.1290
Quarry mine only 1 ore from Dense Ore
Hello. I have problem with BuildCraft quarry - quarry can mine only 1 ore from Dense Ore.
Silk Touch drops Dense Iron Ore
Apparently this is a graphical error occurring only when the blocks are Silk-Touched. Dropped blocks from the inventory appear correctly, and Silk Touch drops are properly handled, but appear as Dense Iron Ore, and become the proper item once picked up.
Crashes dedicated forge server b1285 while looking for client side classes
Adding Common Mod Ores
I suggest making the config generate the common mod ores. Considering 1.7 does not use block ids but uses block names, this should cause no issues and should make life for the user easier. I suggest adding default support for IC2, thaumcraft 4, railcraft, AE2, factorization, and TCon. Thank you for takingg this into consideration.
AE2 Quartz/Charged Quartz is 2 textures in their files, add support?
In AE2, the texture files are set up as 2 textures. One for the stone, and one for the gem. This makes it impossible(?) to have a correctly textured Dense Quartz. The ores drop fine, however.
Comments removed after loading Minecraft.
While adding other mods ore to Dense Ores I was adding comments to keep track of which Mod/ore I was working on. But I found that after I started Minecraft the config was overwrote and my comments were removed.
Becomes a pain with mods like Mekanism and Mineralogy were the ore name is not in the baseBlock.
Crash when using a ResourcePack
At least I think it's denseores which causes this:
Crashes client straight away when trying to turn on the resourcepack and I don't have any denseore textures in the RP.
Allow more then one config file similar to cofh
Current Dense Ores stores everything in one config. It would be nice to have it setup more like COFH were you have a folder you can make multiple config files. This would allow for user to create config files for each mod. Then add a mod base config file as needed vs having them all in one file were you have to remove the lines from the config file and then renumber the block number.
Crash with 1.6
Documentation request
How to force all ores to be dense ores?
I had the mod on my server and on my client (1.8.0/Forge 1450) and if I swap to creative and just lace a massive patch with tnt I cannot see one single block of dense anything, anywhere
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.