Discussion in 'Feed the Beast News' started by slowpoke, Aug 4, 2013.
As most of the people here I'm for the full fix
Wait just for clarification all this only affects the direwolf20 pack correct?
Oh boy, 10% band-aid vs 90% full.
Thinking of punching that trees...
I know how you feel, but I'm with the majority. I'd rather it was completely fixed than just putting a bandaid over it.
Thank you very much for the update Slow. All tickets relating to this issue will now be directed here, since my offerings will yield no real solutions for them.
My Server and I have decided to stay on the current Direwolf 1.1.1 release if we are forced to d a world reset. Most of us have already spent way too much time building our new world.
Are the mod authors doing updates for 1.5 anymore?
Some of them are yes. Right now there's mods that have moved to 1.6 and are done updating for 1.5, Mods that are staying on 1.5 and may not update till 1.7 and mods updating for both 1.5 and 1.7 .... its making it interesting.
A full fix is immeasurably better. It can prevent this from happening again as well as making the ftb teams lives easier.
Full Fix never go half way may be more work but in the end its really less.
In this case we are most definately not awesome just a bit tired. As to Ray Herrrings solution, thats coming in the next launcher or at least our own version of
Gotcha. I think the only reason we would do a world reset right now is if red power were to come out... (that was a joke, please no one comment on that)
Would it be possible for us to switch our 1.1.1 direwolf world to the unleashed 1.1.1?
For what it's worth, the Unleashed pack had some conflicts too. ID for both force gems and gate copier was 6000, and IDs in the 12000 range were assigned to both Extra Trees and MFR.
And, yes, a proper fix that will fix things is far better than a patch.
Mistakes happen, it really isn't a big deal. That said, it is better to deal with the pain now and keep the packs the consistent. Restarting a new world isn't that big of a deal, I could always use creative mode to get myself back to where I was.
@dragonboy1127 i know man, i know.
BUT, we must remember that GREAT job this guys are doing. I mean, I try to do a mod pack for my own, for me and friends, this is a LOT of work, and we have this at one click with FTB.
Just thanks for effort and love that you put on this.
And, know what... Let's beat down that trees
EDIT: perhaps a release prediction help on anxiety
I've run servers both FTB and before, and I believe that it is absolutely imperative long-term that consistent and universal Block IDs be used between all FTB Mod Packs. Therefore, I am decidedly on the side of a good, honest, long-term fix so that this very incident doesn't occur again in the future. I'll be able to sell a one-time world restart to my players a heck of a lot easier than a series of interruptions and custom 'quick fixes' as this continues.
Also, Slow, Thanks for your candor about the issue.
At this early stage of the mod pack, I think a full fix would be best.
Full fix.. I've seen some weird stuff..
Full fix i have not done much on my server so it will not bother me don't think anyone has done much yet as i told them i going to do full reset for 1.6 anyway which is what i waiting on.
Finally this forum sent me a email tried so many times to get it to send me a email.
Oh cool, thanks for that Slow. Really annoying having to download the entire pack each time, even worse when the internet blips for a second or so and causes the download to just give up.
Also means you guys won't have to host the mods themselves. What i like about mcupdater is that it can follow adf.ly links and the like.
The other bonus is not only making changes becomes a bit easier, you have to host less, and changelogs become very easy, simple 'diff' between the old xml file and the new one to pull out what mods changed.
I would like a full fix, the iic community server has suffered loads with world regenerations and bugs and world gen!
We need all of this to stop and we keep loosing members because of this, lag is more common now then in 1.4.7!