Package Details: amulet-map-editor 0.10.55-1

Git Clone URL: https://aur.archlinux.org/amulet-map-editor.git (read-only, click to copy)
Package Base: amulet-map-editor
Description: The new age Minecraft world editor and converter that supports every version since Java 1.12 and Bedrock 1.7
Upstream URL: https://www.amuletmc.com/
Keywords: amulet editor map minecraft
Licenses: LicenseRef-custom
Submitter: tamamizu
Maintainer: Kimiblock (lilac)
Last Packager: lilac
Votes: 8
Popularity: 0.002269
First Submitted: 2023-03-25 15:26 (UTC)
Last Updated: 2026-04-08 12:37 (UTC)

Pinned Comments

Kimiblock commented on 2025-12-23 11:18 (UTC)

Please buy a license before using this software

https://www.amuletmc.com/

Latest Comments

1 2 3 4 Next › Last »

Kimiblock commented on 2026-03-18 00:17 (UTC)

Dependency updated

Kimiblock commented on 2026-03-17 09:25 (UTC)

Yes, I'll fix that later

eris commented on 2026-03-17 07:05 (UTC)

this fails to launch for me, seems to want rocksdb. probably this? https://pypi.org/project/amulet-rocksdb/

Kimiblock commented on 2025-12-23 11:18 (UTC)

Please buy a license before using this software

https://www.amuletmc.com/

Kimiblock commented on 2025-12-11 07:02 (UTC)

@hockeymikey In which package OpenGL-accelerate is required? I checked the namcap log for this amulet-map-editor package but couldn't find any reference. Could be a dependency which pulls it in...

hockeymikey commented on 2025-12-11 04:00 (UTC)

We need to include https://aur.archlinux.org/packages/python-opengl-accelerate as a dep.

gwuensch commented on 2025-10-31 03:27 (UTC)

Thanks! Most Python packages on the AUR don't have this problem as they are built from tarball releases with unique names, instead of directly cloning the Git repo. Of course, both is valid, but from what I've seen tarball releases are also preferred by the official repo packagers.

Kimiblock commented on 2025-10-31 03:08 (UTC)

Ah, makes sense. Will be in next release

gwuensch commented on 2025-10-31 02:59 (UTC) (edited on 2025-10-31 03:00 (UTC) by gwuensch)

Of course this doesn't happen in a clean chroot, but PKGBUILDs generally shouldn't require to be built in a clean chroot every time. Building for one's own system is not the same as packaging for a public repo. Also see my other comment on this topic.

Kimiblock commented on 2025-10-31 02:45 (UTC)

Please try in a clean chroot build because we haven't seen any build issue on the community server