Minecraft Forums

Quote from MamiyaOtaru»

change the keybind in the Minecraft controls menu

millenaire does not let you change keybinds

Quote from MamiyaOtaru»

change the keybind in the Minecraft controls menu

thanks heaps

Quote from Comentador37»

millenaire does not let you change keybinds

yea it worked, gotta go into the controls and it shows what each mod can change. it was the last thing i even thought of.

new version time

1.5.8

• manually select which world you are in on multiworld servers that don't communicate with the client via world_info/journeymapServer/voxelPlayer plugins. Credit to cubic72 for the selection screen
• configurable zoom levels. zoom out 4 times as far as before, if your memory can handle it
• configurable region cache size. again, if memory can handle it, increasing the size of the cache makes regions less likely to unload (to reload later) as you pan around
• now cache map data on disk for singleplayer worlds too instead of creating from scratch every time from the anvil files (mostly because loading from the voxelmap disk cache is twice as fast)
• fix for crash when opening the worldmap with coloredLights mod installed

Hello,

I use MultiMC, and when I go onto different worlds, the waypoints from one world carry over. Is there a way to stop this?

-Nick

that can happen if the worlds have the same name.

1.5.8 actually no longer saves to the users home, it only saves to the data dir of the current miencraft instance. You can delete the .points files from %appdata%/minecraft if you want and waypoints will be instance specific (only do this if you are not running Minecraft out of %appdata%, otherwise that is in fact the only place the waypoints are stored)

Quote from Comentador37»

millenaire does not let you change keybinds

VoxelMap does, which is what I was referring to

Quote from Bars96»

1.5.8? For 1.7.10? One minute... Okay, you win. Thx

bars, I released a new version for 1.7.10 yesterday. it's version 1,5,8 for minecraft 1.7.10. If you want to keep trucking with 1.2.3 you go right ahead but you don't get to complain about bugs that have been fixed in the meantime. 1.2.3 is not the latest anything

how hard is this to understand? you want a bug fixed, use the latest version, where it is fixed.

you can lead a horse to water, but you can't make him drink

Is there a way to make some way points only visible in a specific world for servers with MultiVerse?

hit the multiworld button on the world map (new in 1.5.8)

waypoints created before that will still show on all worlds. either edit the points file or make new ones

Seems to work now. I somehow got the 1.5.7 version instead of 1.5.8 from Curse this morning.

Edit: It's not remembering which world is which, but it remembers what world name the waypoints are set to.

Quote from Kzitold»

Seems to work now. I somehow got the 1.5.7 version instead of 1.5.8 from Curse this morning.

Edit: It's not remembering which world is which, but it remembers what world name the waypoints are set to.

there's really no way for it to remember which world is which, you'll need to tell it each time. Unless the server has a plugin like world_info or journeymapServer installed, it doesn't tell the client anything about which world it is in. I'd have to try to do something monstrously difficult like programming in some pattern recognition, but that's something humans are a lot better at so asking the player each time is the easiest, and really the only, way to go

I might add an option to have the selection screen come up automatically each time you join or switch worlds instead of the player having to remember to open it each time

just dumping thoughts about pattern recognition: I could compare the map data for the current coordinates with the map data for those coordinates on all known worlds, and if it's the same as one of them, decide we are in that world. BUT if it needed to be a 100% match, it would break if someone placed a block. So you add some wiggle room. But what if there are two worlds that are both superflat? Even with 100% matching you could get the wrong one. It's just easier for the player to know which portal he just walked through, by reading the sign next to it or something

I understand that. I guess I'll have to bug the MultiVerse coders about it. XD

2 more things!

There is a bug this causes with Damage Indicators where the screen goes black when I target some mobs.

Could you add a hexadecimal input box to the color select?

that would really be the best. If multiverse would send a packet on new world loads, like this project: https://github.com/coaster3000/WorldInfo/ VoxelMap and JourneyMap would work out of the box, and anything else could use them too

I sort of like the simplicity of the color selector as is, but I wouldn't rule it out

Damage Indicators: it's a 1.8 thing. I'm seeing the issue there. Also looking at other mobs makes everything fullbright. I had a quick look at his code; he's calling openGL directly a lot, instead of going through the StateManager. This is bad because http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/modification-development/2231761-opengl-calls-glstatemanager#c1 1.7.10, from before the State Manager, predictably does not have that issue.

Note since first writing that post I've changed my mind about how useful the State Manager is (see the crossed out stuff and added images). It actually does take a significant load off the CPU. Whether or not it does though, all mods need to be using it. He's making changes directly, so Minecraft (and other mods that use the State Manager) don't know about them and so they don't bother to undo them. There is likely nothing I can do about this, it's his issue to fix (note the post I linked has in a spoiler some code that might make the switch easier)

I have a problem : the game is not to see events[/pre]

So I should demand rich1051414 to switch to StateManager?