I agree with Stuee147 (and many others) on this: Leave the original texture pack alone, and even leave it included with Minecraft, and have the new pack included with it. Minecraft has a pretty good texture pack handling system, so even if they create new blocks down the road, so long as their new pack is the "base" layer, people would still be able to keep the classic textures for everything that existed prior to now, and will just see the new textures for the new blocks. That would be the system working as intended, and it would allow them to keep everyone on both sides of the fence happy.
I mean, this is why we have texture packs, right? Because Mojang wanted to allow everyone to make their MC look the way they wanted it to look! So why force a change to the default appearance when a lot of people like that look?
As a thought, they could even follow the example of the change that added the "auto-jump" feature. Some people liked it, some don't. But when they implemented it, they defaulted it to "enabled." so that everyone would experience it at least once. So they could implement their new textures, make it the "top-level" resource pack so that everyone sees the changes. And those that don't like it can switch the order around in the resource pack screen just like we've been able to do for ages now, and set the "classic MC" pack to be the top level one. Presto, problem solved. None of this "it has to be one or the other" stuff required.
0
0
Time frame: Random. Sometimes we'll play for hours with no problems. Sometimes server sits online for hours with noone online without issues, and sometimes it crashes after five minutes of launching. If it crashes I reboot the whole system, though.
Info:
OS: Windows 7 (fully updated)
MC Server: 1.6.2 (given 1Gb RAM, although I've never seen it use that much)
Java: 7u25 (64bit)
Both Server and clients are all pure Vanilla. The only change is launching via bat script to set the RAM higher.
Hardware: mid-high end gaming system with 16Gb RAM. (less than a year old)
Tried looking at mojira for bug reports and nothing seems particularly relevant, but everything remotely resembling server crashes seems to be getting merged as duplicates into a not particularly relevant one, so I'm not terribly confident of posting there.
If anyone can offer any help, it would be much appreciated.
0
0
This particular problem is rather simple: The hitbox for torches are permenently visible. Doesn't matter if I am aimed at it, close to it or far away. The hitboxes are always visible, sometimes almost more so than the torches themselves. Actually, in general they are *more* visible far away than they are up close. Changing graphics settings (such as Fancy and OpenGL) do not have any impact. Changing settings in Catalyst (such as disabling AntiAliasing, maxing it out, and changing other settings) likewise have no impact on this bug.
I submitted a bug report on it at https://mojang.atlassian.net/browse/MC-27018 which has promptly been marked as a duplicate of a bug reporting texture and game rendering issues (which has been closed as invalid, attributed to graphics drivers, not minecraft). Anyway, I posted a screenshot there which probably explains things better than I can. https://mojang.atlassian.net/secure/attachment/38055/2013-07-24_07.59.48.png is my screenshot.
Technical info:
Running vanilla Minecraft 1.6.2 (with default texture pack)
Java 7u25 (64bit)
Windows 7 (fully updated)
GPU: Radeon HD 7770 (with Catalyst 13.4)
If anyone can provide any help in fixing this issue, I would very much appreciate it.
Thank you,
Zitchas
0
Tree houses are pretty fun too, although less secure...