-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request] node map #29
Comments
This has been suggested in the past. I would love to add it to jouneymap, but its closed source. As to adding a separate UI, it goes beyond what I want the mod to do. I just wanted a simple way to track nodes. |
You might ask in the IRC channel "#journeymap" on esper.net if Techbrew has an API or something similar. I'm curious myself, as I want to make a similar mod to TCNodeTracker for use with ChromatiCraft, and if I could have it plug into JourneyMap (maybe eventually Zan/Voxel, MapWriter, or Rei's... I don't use any of them, so the priority is lower) then it would be a LOT more functional. |
@TomeWyrm suggestion for your pylon tracker: repeater position planner (hud indicator of optimal repeater positions (with or without terraforming)) |
I'm not playing with world files to try and figure out shortest distance paths in 3D with terrain obstructions. That was already planned... though I have NO idea how to implement any of it. I'd be using this mod as an excuse to learn Java. |
it would be nice to have a map which shows the positions of the nodes
1st way: addon for journeymap
2nd way: seperate UI (terrain view would be awesome, but the feature would also be useful without), maybe even with some sort of "aspect influence map" to help choosing base/outpost position.
nodes should have a tooltip which displays all aspects (not just primals). UI could display distance you->cursor. node types, primals and existance of non-primals should be clear without looking at tooltip (eg. colored rays from the node, with a sort of rainbow one for non-primals; aspect size equals brightness/size of related ray)
The text was updated successfully, but these errors were encountered: