hoho / pillbox 2013-10-23

102031 ForestryWiki706 │ hi. I told greg about your request but, as you know, he doesn't really use IRC. Could I tell something to him? I pretty much have a direct line to him atm.
102519 ForestryWiki706 │ I sent him your "official" requirements and this is his current response: There is the small Problem, that I cant trust mDiyo to not put his Code back right afterwards (like he did last time), not to mention that right now it is not possible to release any new proper Version of GT.
102608         pillbox │ I don't understand how it's not possible to release a new proper verson of GT
102733 ForestryWiki706 │ well, the computer he used to use was insanely crappy already. He mentioned running MC at sub-20FPS with minimum amount of mods and stuff as low as possible. I can't even imagine how bad the other PC must be that he is using atm
102814         pillbox │ He doesn't need more than 20FPS to enable a filter in code and verify MC runs afterwards
102846 ForestryWiki706 │ from what I know he doesn't have a dev env on the machine, not quite sure what prevents him from setting it up
102857 ForestryWiki706 │ is there a rough ETA how long it might take for the code to end up in TiC? I imagine if it's more than a few weeks it won't be much of an issue as greg is already working on getting a decent PC
102953         pillbox │ We are hoping to see a stable build within a week
103005         pillbox │ It could be longer
103124 ForestryWiki706 │ ok, roger that
104407 ForestryWiki706 │ greg just told me it's unlikely he'll get a new PC before TiC becomes stable
104419 ForestryWiki706 │ he also said: Said Config would have to be ON per Default, because nobody would see it otherwise, and that would not fulfill any purpose, since people can still see it in the Logs, when they have unchanged Configs. Not to mention, that it doesnt spam as much as you all describe, those UnknownHostExceptions you get on SSP by many other Mods are much worse.  And I would like a peaceful solution, but I cant trust mDiyo at all.
104811         pillbox │ Don't have to trust mDiyo. He just has to trust me.
104825         pillbox │ But leaving that config on by default is a deal breaker
104847         pillbox │ Unless the wording is changed
104930 ForestryWiki706 │ any suggestions how to change it?
104942         pillbox │ What's the exact wording now?
105005 ForestryWiki706 │ 2013-10-23 17:50:17 [INFO] [STDERR] Improperly registered Ore: bone !!!Improperly registered Ore detected!!! This Object does not follow any OreDictionary Convention. Please report this to its Modauthor for a fix. A good suggestion for its Name would be 'SpmodAPI:bone' don't forget to insert the ':' inbetween the Mod ID and OreDict Name, that is the most important part.
105100         pillbox │ Remove "Please report this to its Modauthor for a fix" and comletely remove the portion about the "SpmodAPI:" and ':'
105115         pillbox │ Because mod specific oreDict entires are nonsensical
105140         pillbox │ Also, there is no such thing as an OreDictionary Convention
105436 ForestryWiki706 │ there isn't but don't you agree that it would make sense to have one? :)
105456         pillbox │ Yes; but Greg doesn't get to decide that by himself
105544 ForestryWiki706 │ of course
105606 ForestryWiki706 │ can you see a way how to create a convention that would be generally accepted and would make sense?
105620 ForestryWiki706 │ I mean the way greg suggests to change the names does make a whole lot of sense, after all
105728         pillbox │ I'm not the entire modding community; my suggestions would only carry as much weight as Greg's. And that's fine; let's all get together and discuss TCon's naming conventions. Modder-to-modder.
105736         pillbox │ Not tell your users to report them as bugs
105804 ForestryWiki706 │ yes but I am asking how to get the community together to work it out, not just a couple of modders
105816         pillbox │ Precisely! I have no idea ^_^
105824 ForestryWiki706 │ the way I see it Forge should make the suggestions on wiki official. It's rather sad that they don't
105844         pillbox │ That's outside of the scope of what Forge intends to do and support
105912 ForestryWiki706 │ oredict is part of forge, it should be on API side to describe the best practices of using it
105928         pillbox │ We can base best practices on what Forge itself does
105934         pillbox │ Which Greg has said he disagrees with
105959 ForestryWiki706 │ I see no real difference between that and jar mods and they did make a very much official suggestion to not do jar mods
110022         pillbox │ afk a few
110446         pillbox │ back
110745 ForestryWiki706 │ I sent our chat to greg up until my question about having conventions would make sense, this is what he said:
110745 ForestryWiki706 │ 1. There were OreDict Conventions right on from the beginning when Eloraam created it, but they seemingly went forgotten. 2. There are quite some cases, where private Prefixes are indeed needed, like for people who make Lists of Stuff usable in their contraptions or crafting recipes, but dont want to have Name clashes. 3. I cannot update right now as mentioned.
111457         pillbox │ If possible, I would like a list of all TCon OreDict entries that Greg deems incorrectly defined
111522 ForestryWiki706 │ sure, I'll need a few minutes for it
111535         pillbox │ No problem
111543 ForestryWiki706 │ also, in case you don't know GT also flags vanilla items that are added to oredict :)
111656         pillbox │ I know; part of the problem actually. It appears Greg is willing to point a finger at Forge for using the thing they provide/maintain
111820         pillbox │ Oh ,I see. I misread that.
111839         pillbox │ I'm not sure why you wouldn't want to add vanilla-compatiblity to your oreDict entries
112610 ForestryWiki706 │ actually it seems like I was mistaken and it doesn't complain about things added to oredict by forge
112624 ForestryWiki706 │ also, there are two different log messages, one for blocks and one for items
112731 ForestryWiki706 │ here are the log entries about TiC by the oredict scanner: http://pastebin.com/xqpmPuHq
112820 ForestryWiki706 │ so the "ores" are hambone, mossystone and slimeball
112833 ForestryWiki706 │ items are all the rods
112905         pillbox │ Rods aren't going to change; they are holdovers from Inficraft
112931         pillbox │ 'slimeball' seems legit to me
113036         pillbox │ hambone... can't we just ignore this one? ^_^
113047         pillbox │ Is there an existing moss stone oredict entry?
113048 ForestryWiki706 │ what is "mossystone"? I'm not sure what mod does this but NE shows me that the vanilla mossy stone is in dict as stoneMossy
113054 ForestryWiki706 │ *NEI
113128         pillbox │ Yeah, I think we can change stoneMossy on this side.
113150 ForestryWiki706 │ there was a suggestion for hambone to use materialHambone on forums somewhere
113213 ForestryWiki706 │ as I'm not really using TiC, what exactly is a hambone? Perhaps there is a better oredict name for it
113242         pillbox │ It's a decorative block...
113248         pillbox │ That looks like a giant block of ham.
113308 ForestryWiki706 │ heh, ok
113341         pillbox │ Honestly, it should probably be blockMeat
113412         pillbox │ But we discussed making it compat with MFR and decided against
113440 ForestryWiki706 │ would anything break if bot MFR and TiC change the oredict names?
113531         pillbox │ Just TiC needs to change; it's not a shared entry with anybody
113542         pillbox │ What's it take to get installed on the ignore list?
113623 ForestryWiki706 │ if only TiC needs to change then why was it needed for MFR compatibility?
113635 ForestryWiki706 │ and by ignore list you mean the list that GT would ignore when reporting to log?
113640         pillbox │ Yes
120129 ForestryWiki706 │ finally something that should work :)
120129 ForestryWiki706 │ "slimeball" -> either "ballSlime" or "itemSlimeball" "hambone" -> could be "blockPorkchop" or "blockHam" if it is made of 9 Pig Meat, block is especially for those 9 Items = 1 Block Recipes. "mossystone" -> "stoneMossy", while that follows the concept of "logWood" and allows any mossy stone.  I can add a special case where the error can ignore anything registered by the ModID TConstruct, but that's it, and will as mentioned take some t
120351         pillbox │ slimeball will not be changed
120407         pillbox │ It is the internal codename for the vanilla item and, as such, is the perfect name for an oreDict entry
120431         pillbox │ stoneMossy is currently in proress
120433         pillbox │ progress
120611         pillbox │ "hambone" is akin to mDiyo's pet and is likely not going to change.
120631         pillbox │ If we can get it added to the "I don't understand this, but I won't say anything" category, that would be best
120739         pillbox │ And if we do a big overhaul for 1.7, I will work to get materialRod changed to rodMaterial
120906 ForestryWiki706 │ Ok, good to know
120923 ForestryWiki706 │ considering greg said he is willing to add a mod to the ignore list I'd say that should be good enough solution?
120931         pillbox │ I concur
121322 ForestryWiki706 │ reply from greg: "I will add those two to the ignoredNames List."
121519 ForestryWiki706 │ now my own question would be, why didn't mDyio ask something like that from Greg in the first place and instead went thermonuclear? :)
121635         pillbox │ I can't speak to that
121655 ForestryWiki706 │ no problem, it was a rhetorical question anyway :)
121700         pillbox │ ^_^
125931               < │ ForestryWiki706 ([email protected]) has quit (Ping timeout: 202 seconds)