Am having an issue (apologies if this has been asked before). I'm currently on a server using the 1.12.2 liteloader client with forge chained in. Voxelmap was included in the modpack. Every time I disconnect and reconnect, only the waypoints i have set are saved/displayed. The chunk tiles (except for those in my immediate render distance.) are not. All other server users report that this is not the case for them, but we all installed via the same process.
Right now we are in the 1.13.1 Snapshot on our server. At SOME point we look forward to the intersection between LiteLoader, the version we are running on the server, and VoxelMap. I've been strongly urging people to support the Mods and Plugins they enjoy, because I know if we don't show our appreciation for the things we treasure, we may find they are no longer around.
What's the best way for my wife and I to show our appreciation? A donation now or a donation after the 1.13.something release? At this point, it looks like "1.13.0" is more a "snapshot" than a release, and we all may be better off just pretending like 1.13.0 didn't happen and skip to 1.13.1.
right on time for 1.14, VoxelMap for 1.13 is nearing completion
As we are still lacking Forge or Liteloader for 1.13, I am currently using Rift to get things running and be able to make the transition to 1.13 with my code. If my preferred loader doesn't make an appearance by the time I feel like VoxelMap is ready I could certainly release using it. Of course it seems stuck at 1.13 at the moment, and I assume Liteloader will proceed straight on to 1.13.1+ once it comes out, so well see
right on time for 1.14, VoxelMap for 1.13 is nearing completion
As we are still lacking Forge or Liteloader for 1.13, I am currently using Rift to get things running and be able to make the transition to 1.13 with my code. If my preferred loader doesn't make an appearance by the time I feel like VoxelMap is ready I could certainly release using it. Of course it seems stuck at 1.13 at the moment, and I assume Liteloader will proceed straight on to 1.13.1+ once it comes out, so well see
Nice!! I'd be glad to come back with VoxelMap soon!^^ Is RIFT your own modloader? First time I see that name, haven't checked on these forums lately ahah xD
Rollback Post to RevisionRollBack
MagicLauncher is the best launcher I ever used! Hoping the developer would update for 1.13.x and 1.14.x
all new mobs added. Tropical fish icons reflect their full diversity
now shows underwater plants and transparent blocks
some biome colors tweaked so you can see the border between them when the biome overlay is enabled
added optional keybind for toggling in-game waypoints
turning off coordinate display on the minimap also turns it off on the worldmap
red lines when grid view is on now reflect Minecraft regions (instead of quarter regions)
For years I've been using Liteloader, even though that isn't a lot of peoples' preferred mod loader. Well now I'm going a little more obscure: Rift. As it happens, there is no Liteloader or Forge for 1.13 yet. Rift has allowed me to port to 1.13 and test, so hopefully people are OK with trying a new modloader (it's just about the only one out so far!)
All the new mobs' icons are done. Fish are just the fish from the sides, and displayed smaller. Tropical fish show all their variety. Bats' icon has been shrunk too. All of them (on a per mob type basis) can of course be turned off. I tend to have squid, bats and fish off.
Working OK with Optifine (though optifine itself seems a little shaky on 1.13 still) and random entities, where resource packs can add (multiple) new skins for mobs. See the squid icons in the screenshot a couple posts above. If Forge ever appears for 1.13 I'll have to test compatibility with it, but nothing should break too badly.
The downside to 1.13: all your world maps will have to start over. Mojang has for ages been saying not to store block data as integers. Over a year ago, to get ready for this, I moved away from storing as int. Each block is stored as its blockstate, so if the underlying ints change they would still show up on the map just fine. HOWEVER in 1.13, Mojang went and changed a bunch of the blockstates, so that was basically for nothing. They wrote a big old converter to convert old worlds to the new values, and I am not going to replicate that so maps are unfortunately wiped. Hopefully they don't change blockstates any more (ie the flattening should allow them to have more or less final values) so this shouldn't happen again, but it is a thing.
In singleplayer worlds, the world map will generate to cover the whole area that has already been explored (and saved to disk) but there are occasional glitches and some chunks will just be black squares until you visit them again with the map active. BUT worlds that have been converted from previous versions of minecraft will not have their world map regenerate automatically. It seems some of the conversion doesn't happen until you actually visit, so loading the level data from the disk to create the world map doesn't work. For those maps, you will have to visit places with the map active, like you would need to for multiplayer worlds.
It's a bother, but having a map at all should be a good thing.
curseforge takes a while approving files sometimes. Previous version was a tad buggy so I took it down in the meantime. It will appear there as soon as they approve it, which seems to be taking longer and longer lately
Actually, apparently you should be able to use this instead of the "Open to LAN" button: https://minecraft.gamepedia.com/Commands/publish
Sadly, there is no Russian version of that page available, it seems. :/
Thanks to Chocohead and ZombieHDGaming for the tip.
I executed command /publish 25565
Translation (manual): Local server was opened at port 3257
thank you Robijn for testing out (or helping someone test out) publish. Next version will have some reworked network detection that may fix the issue of not detecting LAN worlds (and not using the variable port number for saves), but this is good to know in the meantime
to be fair to him, Rift isn't out yet for 1.13.2. And it's not really "some people" who have gotten it to work with 1.13.2, it's me heh. Once there's a Rift release for 1.13.2 I'll have a version of VoxelMap for it ready to go
still wish there was a keybind for toggle biome overlay...
Am having an issue (apologies if this has been asked before). I'm currently on a server using the 1.12.2 liteloader client with forge chained in. Voxelmap was included in the modpack. Every time I disconnect and reconnect, only the waypoints i have set are saved/displayed. The chunk tiles (except for those in my immediate render distance.) are not. All other server users report that this is not the case for them, but we all installed via the same process.
Right now we are in the 1.13.1 Snapshot on our server. At SOME point we look forward to the intersection between LiteLoader, the version we are running on the server, and VoxelMap. I've been strongly urging people to support the Mods and Plugins they enjoy, because I know if we don't show our appreciation for the things we treasure, we may find they are no longer around.
What's the best way for my wife and I to show our appreciation? A donation now or a donation after the 1.13.something release? At this point, it looks like "1.13.0" is more a "snapshot" than a release, and we all may be better off just pretending like 1.13.0 didn't happen and skip to 1.13.1.
right on time for 1.14, VoxelMap for 1.13 is nearing completion
As we are still lacking Forge or Liteloader for 1.13, I am currently using Rift to get things running and be able to make the transition to 1.13 with my code. If my preferred loader doesn't make an appearance by the time I feel like VoxelMap is ready I could certainly release using it. Of course it seems stuck at 1.13 at the moment, and I assume Liteloader will proceed straight on to 1.13.1+ once it comes out, so well see
Nice!! I'd be glad to come back with VoxelMap soon!^^ Is RIFT your own modloader? First time I see that name, haven't checked on these forums lately ahah xD
almost there
So excited! Your gonna make my liver quiver hehehe
New release!
1.8.0 (for MC 1.13)
For years I've been using Liteloader, even though that isn't a lot of peoples' preferred mod loader. Well now I'm going a little more obscure: Rift. As it happens, there is no Liteloader or Forge for 1.13 yet. Rift has allowed me to port to 1.13 and test, so hopefully people are OK with trying a new modloader (it's just about the only one out so far!)
All the new mobs' icons are done. Fish are just the fish from the sides, and displayed smaller. Tropical fish show all their variety. Bats' icon has been shrunk too. All of them (on a per mob type basis) can of course be turned off. I tend to have squid, bats and fish off.
Working OK with Optifine (though optifine itself seems a little shaky on 1.13 still) and random entities, where resource packs can add (multiple) new skins for mobs. See the squid icons in the screenshot a couple posts above. If Forge ever appears for 1.13 I'll have to test compatibility with it, but nothing should break too badly.
The downside to 1.13: all your world maps will have to start over. Mojang has for ages been saying not to store block data as integers. Over a year ago, to get ready for this, I moved away from storing as int. Each block is stored as its blockstate, so if the underlying ints change they would still show up on the map just fine. HOWEVER in 1.13, Mojang went and changed a bunch of the blockstates, so that was basically for nothing. They wrote a big old converter to convert old worlds to the new values, and I am not going to replicate that so maps are unfortunately wiped. Hopefully they don't change blockstates any more (ie the flattening should allow them to have more or less final values) so this shouldn't happen again, but it is a thing.
In singleplayer worlds, the world map will generate to cover the whole area that has already been explored (and saved to disk) but there are occasional glitches and some chunks will just be black squares until you visit them again with the map active. BUT worlds that have been converted from previous versions of minecraft will not have their world map regenerate automatically. It seems some of the conversion doesn't happen until you actually visit, so loading the level data from the disk to create the world map doesn't work. For those maps, you will have to visit places with the map active, like you would need to for multiplayer worlds.
It's a bother, but having a map at all should be a good thing.
bugfix release
1.8.1
once more
1.8.2
curseforge takes a while approving files sometimes. Previous version was a tad buggy so I took it down in the meantime. It will appear there as soon as they approve it, which seems to be taking longer and longer lately
it's back up. should stay there for a while, unless anyone points out any big bugs. Believe I got them all this time!
Hello. Can you tell me, how to save waypoints if you play by local network (port are different whenever and waypoints being in a different files)?
(sorry for my bad english, because im russian)
I executed command /publish 25565
Translation (manual): Local server was opened at port 3257
thank you Robijn for testing out (or helping someone test out) publish. Next version will have some reworked network detection that may fix the issue of not detecting LAN worlds (and not using the variable port number for saves), but this is good to know in the meantime
also
Nice to see its still going in 1.13.2! <3
Not sure how some people got this to work on 1.13.2 but is there an estimate on when this will be updating to 1.13.2?
Did you read page 1 of this thread?
It explains how it must be done for 1.13 including a requirement for Rift (I'm not sure that is),
Did you try that?
Links to pdf format, downloadable, command lists for (these often clarify/expand descriptions, and where possible link to the author's posting):
MoreCommands: http://www.mediafire.com/view/qjc9c6klcnp660e/CmdLstMoreCommands.pdf
WorldEdit: http://www.mediafire.com/view/bi7r00xd9rgxrrt/WE_Commands.pdf
to be fair to him, Rift isn't out yet for 1.13.2. And it's not really "some people" who have gotten it to work with 1.13.2, it's me heh. Once there's a Rift release for 1.13.2 I'll have a version of VoxelMap for it ready to go
1.13.2 is out. needs Chocohead's Rift for 1.13.2 https://jitpack.io/com/github/chocohead/rift/2c400465c7e0b5abf4e643372fbd9a7e6d39e3ff/rift-2c400465c7e0b5abf4e643372fbd9a7e6d39e3ff.jar
has some fixes I'll backport to 1.13 and 1.12.2 when I get a bit