free to use if you don't make any money off the modpack. No hosting behind an ad link. I also used to ask that people link to my page, but there really isn't one now, so please provide credit. That's it!
Also, 1.8!
The rabbit icon was crated by VoxelMap's auto icon creation code. I haven't gone in and tweaked it (I will, to add some space between the ears). It got pretty close without any hand holding though
Any download links for the 1.8 edition yet, or you don't consider it stable enough for public release ??? I'm not putting pressure here, take the time you need to finish it up if it needs to be.
Any download links for the 1.8 edition yet, or you don't consider it stable enough for public release ??? I'm not putting pressure here, take the time you need to finish it up if it needs to be.
The MCP preview was released today, I don't think he hardly started yet.
free to use if you don't make any money off the modpack. No hosting behind an ad link. I also used to ask that people link to my page, but there really isn't one now, so please provide credit. That's it!
Also, 1.8!
The rabbit icon was crated by VoxelMap's auto icon creation code. I haven't gone in and tweaked it (I will, to add some space between the ears). It got pretty close without any hand holding though
I was sure he used something else like some impatient modders do, I was sure that Forge for 1.8 would be heavily delayed due to the fact they probably want to build a server API in it to replace bukkit seems I was wrong.
I was sure he used something else like some impatient modders do, I was sure that Forge for 1.8 would be heavily delayed due to the fact they probably want to build a server API in it to replace bukkit seems I was wrong.
Some "impatient modders" do what MCP does but manually, but he still have to wait for LiteLoader, unless he makes a basemod first...
yeah, it's a jarmod for now. Still waiting on liteloader, but making a jarmod let's me get adapted to 1.8 and get errors ironed out. It's pretty easy to switch back and forth. The base classes are identical, all that differs is if it's called from GuiIngame or a litemod class. It's almost ready now, so once liteloader is ready, I can switch over in a blink.
Interaction with MCPatcher's custom colors and CTM is a bit odd yet, but MCPatcher is still heavily beta. Getting that ironed out could take a while still. There is also a lot I can do under the hood to make it more 1.8-like instead of just running in 1.8. At any rate, I can release within an hour or two of liteloader updating, and polish other bits later
Great, thanks for updating us on your hard work, lets see if liteloader will release faster than forge team or not, I was sure liteloader needed forge to be updated because even if Forge isn't required to install liteloader he may still use some parts of the code of it and integrate it into his loader, but I could be totally wrong with this, have no knowledge on programming at all, except some basic Visual Basic stuff learned during high school and I didn't like this at all.
it's quite possible liteloader will need to wait for forge so Mumfrey can check that chaining etc works properly. That doesn't affect my code at all, aside from the waiting part. I don't use Forge myself, though the map works fine with Forge, thanks to Liteloader (which again is why everything might need to wait for Forge). Unless jarmod!
it's quite possible liteloader will need to wait for forge so Mumfrey can check that chaining etc works properly. That doesn't affect my code at all, aside from the waiting part. I don't use Forge myself, though the map works fine with Forge, thanks to Liteloader (which again is why everything might need to wait for Forge). Unless jarmod!
Just spied some conversations at the Forge forums, we could have to wait a lot for an official Forge release for 1.8 or even more if Mojang release a patch like 1.8.1 or something like that, they have the loader part finished but Mojang did so many changes in MC1.8 that for them it would take time to get something working well, or I've totally misunderstood what I've read. Not complaining here at all, they have to make sure it works well and is stable enough to be used by anyone, still its a major waiting game like in MC1.7 serie.
I really wouldnt be expecting to play 1.8 modded for a good 6 months at least. 1.7.10 is out and devs are working crazy hard on updating to the new block system. I will happily wait till they are ready to be released by the devs, no rush. keep up the good work guys and gals
it's quite possible liteloader will need to wait for forge so Mumfrey can check that chaining etc works properly. That doesn't affect my code at all, aside from the waiting part. I don't use Forge myself, though the map works fine with Forge, thanks to Liteloader (which again is why everything might need to wait for Forge). Unless jarmod!
Any idea where I can post a crash log, please? If you happen to see this, I have already posted the report on another mod's github here (you'd have to scroll about half way down for the VoxelMap report), else the full log is here. Crash occurred on respawn after death and relates to the rendering of the death waypoint. Thank you
Any idea where I can post a crash log, please? If you happen to see this, I have already posted the report on another mod's github here (you'd have to scroll about half way down for the VoxelMap report), else the full log is here. Crash occurred on respawn after death and relates to the rendering of the death waypoint. Thank you
Man I have been using Voxel/Zans Map religiously for over a year now, I always liked it better than the other maps. Haven't really tried updating any mods since 1.7.2. I saw the 1.8 picture, is it actually released?
Can anyone tell me what the modpack license is on Zan's/VoxelMap
Also, 1.8!
The rabbit icon was crated by VoxelMap's auto icon creation code. I haven't gone in and tweaked it (I will, to add some space between the ears). It got pretty close without any hand holding though
The MCP preview was released today, I don't think he hardly started yet.
1.8? But Forge isn't out for 1.8 yet ....ooh.
Some "impatient modders" do what MCP does but manually, but he still have to wait for LiteLoader, unless he makes a basemod first...
Interaction with MCPatcher's custom colors and CTM is a bit odd yet, but MCPatcher is still heavily beta. Getting that ironed out could take a while still. There is also a lot I can do under the hood to make it more 1.8-like instead of just running in 1.8. At any rate, I can release within an hour or two of liteloader updating, and polish other bits later
Just use Forge then.
Any idea where I can post a crash log, please? If you happen to see this, I have already posted the report on another mod's github here (you'd have to scroll about half way down for the VoxelMap report), else the full log is here. Crash occurred on respawn after death and relates to the rendering of the death waypoint. Thank you
PM me