Skip to content
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

Stop writing images directly to the .minecraft folder #60

Open
NatoBoram opened this issue Sep 25, 2021 · 5 comments
Open

Stop writing images directly to the .minecraft folder #60

NatoBoram opened this issue Sep 25, 2021 · 5 comments

Comments

@NatoBoram
Copy link

I think it's disrespectful to invade the user's .minecraft folder, especially since the .minecraft/config folder and the .minecraft/voxelmap are already used by VoxelMap. There are many, many mobs now that are all shown in this folder for no good reason. It would be appropriate to put them in their own folder, either .minecraft/config/VoxelMap or .minecraft/voxelmap.

@fooeyround
Copy link

I agree its a big clutter, also is the code here not complete or is it just weirdly written and without the build files?

@0xfeeddeadbeef
Copy link

The code looks "weirdly written" because it is a decompiled source code of a discontinued mod named "Zan's Minimap".

@fooeyround
Copy link

Hmm but where is the voxelmap code that is in the mod? Is it not open or?

@NatoBoram
Copy link
Author

It's closed source, just like Zan's Minimap. It's also probable that fantahund99's fork will be closed source.

@fooeyround
Copy link

Wait then how do they get the source to fork? Do they tediously just bring it from.intermediary to yarn and remake build scripts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants