http://www.youtube.com/watch?v=_7PkLlxD2pw
Small quirks but usable. Crops are now displayed even after reconnecting and the seedbags have their proper names and work on the Cropnalyzer.
http://www.youtube.com/watch?v=_7PkLlxD2pw
Small quirks but usable. Crops are now displayed even after reconnecting and the seedbags have their proper names and work on the Cropnalyzer.
Forge updated today, I tested it, SP and SMP both work fine and I also tested it with IC2(and RP2), works perfectly. I eagerly await the release you promised in the comment on the video.
Forge updated? Finally!
However, given it works without erroring, the new SpecialArmor hook probably wasnt included yet, damnit
I guess this means Batpacks still breaking?
The 1.3.2.2 version, which is the stable one is just 1.3.1 as it should have been. Lex fixed all the older bugs (and Typos...) and the version problem and whatever else was strange. He wants to get things right before adding new stuff.
Let's say it this way: If the hook would have been implemented, Batpacks wouldn't possibly break anymore, after we ported IC² to the new forge version.
Al, the builds in Lex's system are straight off git, so it MUST have the armor fixes.
EDIT: Our changes aren't merged yet
http://lexmanos.no-ip.org:8080/job/Forge/5/
Try that out and let me know if it works for yall.
You are correct, my build system is linked to the github repo.
But the sourceforge is dead. You should not use it.
El needs to contact me or ST to be added to the GitHub repo.
Also if you have any other feature requests DO NOT send them to El, and DO NOT send them to me.
There is a public forum and github has pull requests.
You should bring things forward in a PUBLIC fashion.
If I would of known someone needed something like this, I would of done it days ago.
We're trying to move away from the cloak and dagger style of requesting Forge changes.
My bad then, dropping someone a zip with the files is easier then writing public requests and stuff
Don't consider it an ueber-critical issue, it's merely a "serious annoyance".
I know it's easier. Just not how things should be done
Esp if you give them to El.
She has her own mod and only works on forge when she feels like it.
Not saying thats a bad thing. She should work on her own mod.
If you make requests in public then both her and myself could do them.
Or someone else in the community could write a pull request.
Also it makes for better understanding of what you wanted and why if there is a public way of discussing it.
Display MoreI know it's easier. Just not how things should be done
Esp if you give them to El.
She has her own mod and only works on forge when she feels like it.
Not saying thats a bad thing. She should work on her own mod.
If you make requests in public then both her and myself could do them.
Or someone else in the community could write a pull request.
Also it makes for better understanding of what you wanted and why if there is a public way of discussing it.
Thanks Lex. You been a big help or at least to me you have