Jump to content

smbarbour

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by smbarbour

  1. For anyone moving from FG for 1.6.4 to 1.7.2, the sonatype maven entry needs to be added after the forge maven entry in the buildscript section at the top: maven { name = "sonatype" url = "https://oss.sonatype.org/content/repositories/snapshots/" }
  2. If the modder cares about compatibility, load all the mods he or she cares to be compatible with and call OreDictionary.getOreNames(), and if they want to go even further, iterate over the string array that it returns to call OreDictionary.getOres(oreName) and get a List of ItemStacks. Mod compatibility is meant to be global, not something restricted to certain mods. Guess what forge does, by allowing several different mods to run together, without any problems? Standardization of oredict names allow cross-mod compatibility between mods even if they don't know the existance of each other, so the end user will never find incompatibility issues of items of the same type if both mods follow the standard. So, this is not something unnecessary and not making mods follow the convention will eventually cause item incompatibility issues between mods, like GT and TiC rods are incompatible because of different oredictnames for same item. In the example you list, GregTech chose to not use the names that were already in use. Also, the code that GT uses specifically ignores a large number of entries that do not follow the guideline, such as bronzeTube, ironTube, obbyTube, leatherSeal, and stoneBowl Bonus fact: one of the entries in the list of specifically invalid names is in fact appropriate according to the guideline: woodRod. According to the guideline: "- For anything wooden, please use "wood", then the type"
  3. If the modder cares about compatibility, load all the mods he or she cares to be compatible with and call OreDictionary.getOreNames(), and if they want to go even further, iterate over the string array that it returns to call OreDictionary.getOres(oreName) and get a List of ItemStacks.
  4. The whole "private prefix" notion is completely contrary to the point of the ore dictionary in the first place (which is to allow mods to specify interchangeable items). My counter-proposal, therefore would be to print an opt-in list after all of the mods have loaded of the strings registered in the ore dictionary and the number of items registered to those strings. Anyone interested in compatibility would have done research into the strings that were already in use.
  5. This is unnecessary. There is no good reason to spam users about a non-issue.
  6. I had this same issue on one of my Linux machines. The real question though is why is this value being set so low? The default setting is 40, and "A maximum of less than two indent lengths will be ignored." Since the indent length is not being specified in the config, the indent length is 4 spaces. According to the astyle documentation, this is, in fact, an invalid configuration.
  7. If it is possible, could the MD5 of the download be provided for the user-installed files on files.minecraftforge.net?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.