Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


Forge Modder
  • Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About fr0st

  • Rank
    Creeper Killer


  • Gender
  • Location
  • Personal Text
    I used to be new!
  1. Are you looking for ChunkProviderSettings ? There are hardcoded defaults of world generation settings. (The gui when you choose to make a custom world)
  2. fr0st


    That was my best guess anyways. Aah, alright, no point in this thread anymore!
  3. fr0st


    I seem to have solved my issues with some random seed trickery; I still have a question for you. The only "problem" left is the slight lag that my (?) world gen causes. Even though I am just generating one ore, it sometimes says Can't keep up! Did the system time change ... in the console. The amount of ticks skipped is not too large, but still quite substantial (peaking at 173 ticks skipped). Does this happen even on vanilla worlds? I could understand if the whole minecraft world generation would be causing this, not just my mod's. (as such errors are prompted when flying thr
  4. fr0st


    Hi. Not too long ago I made a thread about my WorldGen system's odd behaviour. I am not porting, but entirely rewriting my mod for 1.10.2. This is to ensure better code quality. Anyways, I now need to remake the WorldGen system. I have a few problems and questions about this. The main issues/questions I have are these: My ores spawn very far away from the spawn. How are chunk coordinates chosen? Completely randomly, or based on player's position? Can't keep up! Did the system time change... is my system not efficient? The main issue. To spawn my copper ore, I
  5. Nailed it. Thanks a lot. I'll let this thread open in case I'll need anything else, until I'm done porting. Edit: Anything about Item>getColorFromItemStack ?
  6. Thanks a lot, choon! Oh, and another small thing: what about onBlockEventReceived ? Couldn't find anything on the issue tracker. Edit: Is it now eventReceived ? It's shown as deprecated, though.
  7. Hey. I am in the tedious progress of porting a mod. 1.8 -> current latest 1.10.2 ( I have had some success up to now, but I can't find anything about World#markBlockForUpdate . I saw that TGG uses it in his MBE github repo, but won't show up for me. Was it renamed? Was it removed? Was it reworked? I'd like to know! P.S: Oh, and I found myself quite often in this kind of situation, where I blindly google for alternatives. But, can some of you share the secret to knowing which changes Forge underwent? (The changelog doesn't help the smallest bit. I tried.)
  8. So all I have to do is create the blockstate json and place the model files in models/block ? And what do you mean by "normal" item model? I will post my attempt later, thank you guys. Edit: I am working on it (currently rewriting my model registry), and I just realized that I should have told you I'm working with 1.8, not 1.8.9, if that makes any difference.
  9. Hi. After playing a bit with the new JSON systems introduced in 1.8, I have been wondering.. Since a BlockState JSON file can be used (with the forge syntax) to reduce a lot the number of useless and redundant Block Model files, can something similar be done with items? Is there a way to use BlockState files for items, or to dynamically define the texture of an item, using one simple model, just editing some texture values for each variant the item has? Thanks to anyone who can provide any information about this.
  10. I was totally sure I had. Sorry. I'll try to double-check next time. Have a good evening!
  11. Hi everyone. Coding quite tired at the moment, and I have run into an error. I have a Coal Generator block with facing and on-off variants. I currently have implemented everything and it works fairly well, altough the blockstate/model JSONs aren't working as intended. Can any of you give a look at it, since I am fairly new to 1.8 and still unfamiliar with such errors? [spoiler=BlockCoalGenerator.java] package projectcoal.common.block.energy; import com.google.common.base.Predicate; import net.minecraft.block.material.Material; import net.minecraft.block.properties.IProperty; impo
  12. And that is exactly what came to my mind, jeffryfisher, so I have just debugged the FeatureOre#[b]generateOre[/b] calls, and they always use the same BlockPos', so the randomness is shared across all 5 FeatureOre s. Any idea on how to go about this? Thanks again. Edit: I might try one thing out. I'll let you know in a few minutes. Okay. Using a new Random instance for every time WorldGenFeature#generate is called instead of the Random argument,fixes my issue. Now I still have a slow world gen and densely packed ores, but there is no way these should be a problem.
  13. Good point. I now have. WorldGenFeature#[b]generate[/b] is called by GameRegistry#[b]generateWorld[/b] 5 consecutive times per chunk (chunkX and chunkZ changing after 5 times) in the order Copper-Silver-Lithium-Tin-Lead during world init, and it's copper that gets generated. We might be a step closer now..
  14. The static section runs after the enum's constructor, and everything runs as one would expect. The constructor gets called 5 times with the right arguments, and then the META_LOOKUP array is filled with the correct values. Thanks for the heads up, but still nothing useful came up from the debugging.
  15. Alright, I have carried out a few more tests, but nothing came up. I got to generate every type of ore at least once, except for silver, which has never been picked by the generator so far. The generated ore doesn't change each world created, nor every time the client is run from Eclipse, so I still don't get how the ore is chosen. May the generators be conflicting? This is a mystery that just goes beyond me, I am clueless. Any bit of help would be greatly appreciated.
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.