Fill out this form to let me know which features to prioritize for a proper 1.13 update!

If you want to be notified of new alpha builds, click the subscribe button the right!

no I don't get any pretty subscribers stat.

So yea, this codebase is an abstracted mess based on the nearly-removed Item IDs. So getting this to 100% 1.13 compatibility is going to be a fairly arduous and time-consuming undertaking, similar to a rewrite due to its practically complete dependence of IDs and damage/data values in many areas throughout the codebase.

Here's a non-exhaustive list of some things to do if you wanna help out. https://ci.appveyor.com/project/RoboMWM39862/extrahardmode/build/artifacts for the latest development version. Make sure you include the output of /version ExtraHardMode when reporting issues!

Also, feel free to chat and/or idle: https://techfortress.robomwm.com/p/plugin-chat-support.html (yes it includes dumcord too...)

Thanks for making a start. Note that https://dev.bukkit.org/projects/fun-hard-mode/files/2628076 returns a 404.

Should be available now. I posted link before it got approved.

Hmm, I guess I should make a poll for some of these features. If the old metrics were still alive I'd be able to tell who used/disabled what.

I will do some testing. I assume that transferring data from 1.12.2 is a bad idea (although I'll probably try it); we should build anew.

If it's of any use, you can find my EHM 3.12.1 config here. Please let me know when you have it, or if you don't want it, so it can be removed.

Spigot 1.13.1 latest
EHM 1.13-alpha

plugin.yml is missing:

api-version: 1.13

With that added, EHM boots up. Moving in ...

(Further issues will be posted separately.)

I tested mining, farming, torch, and gravity mechanics. Much more to test. Please feel free to pitch in.

Huh, thought I added that to plugin.yml a while ago. I guess I forgot...

I don't mind if you post issues here, the update has a ways to go for few of the features. Will put up a poll later today.

For now, I'm going so assume that monster attributes have not changed, since they do not involve materials changes. Please advise if you find otherwise. For example:

Monster attributes

• More monsters spawn below Y=55.
• Monsters spawn even in partially-lit spaces below Y=40.
• Monsters spawn in previously-visited locations.
• Monsters drop nothing if at great disadvantage (for example, in water or damaged from falling).
• Monster grinders are detected and disabled.

Blaze attributes

• Blazes occasionally spawn near bedrock in the overworld, but do not drop any items.
• Blazes spawn more frequently in the nether.
• Blazes drop fire when damaged. Fire is bad (see above).
• Blazes explode when killed, but damage only players, not the environment.
• Blazes drop bonus loot when killed.

Creeper attributes

• Creeper explosions damage only players and other entities, not the environment.
• Creepers occasionally drop primed TNT when killed.
• Creepers explode if damaged by fire.
• Charged creepers explode when damaged.

EnderDragon attributes

• EnderDragons can respawn.
• EnderDragons drop dragon eggs, and sometimes villager eggs.
• EnderDragons call Blazes and Zombies as minions
• Endermen nearby will sometimes join the fight.
• Players cannot build protective structures in The End.

Enderman attributes

• Endermen can teleport the player, as well as themselves.

Ghast attributes

• Ghasts explode when killed, but damage only players, not the environment.
• Ghasts are harder to damage and kill, but drop more loot.

MagmaCube attributes

• MagmaCubes occasionally spawn with Blazes in the nether.
• MagmaCubes grown into Blazes when damaged.

PigZombie attributes

• PigZombies are always angry, but do not cause quite so much damage.
• PigZombies drop netherwart when killed in fortresses, and sometimes elsewhere in the nether.
• PigZombies spawn from lightning strikes in the overworld.

Skeleton attributes

• Skeletons sometime shoot snowballs, which cause blindness.
• Skeletons sometime shoot fireballs. Fire is bad (see above).
• Skeletons sometime shoot silverfish, which cause havoc.
• Arrows often pass through skeletons. Close combat is more effective, but more dangerous.

Spider attributes

• Spiders drop webs when killed, which slow movement.
• Spiders spawn more frequently underground.

Witch attributes

• Witches sometimes spawn baby Zombies to aid their attack.
• Witches sometimes cause explosions.
• Witches can teleport.

Zombie attributes

• Zombie hit causes the player to slow for five seconds. Subsequent hits increase the effect.
• Zombies occasionally drop heads and are resurrected when killed. Break the dropped head to stop the cycle.

Yea, all this stuff should be unchanged. I think the TemporaryBlock abstraction is based on material string ids instead if integer ids so that one is good. That one's also is used in very few places (only one feature that I know of), so yea.

New alpha build has been released! Details on this commit: af6d56d (Next time I'll mention this issue on a commit to automatically notify of a new alpha build.)

Download at https://ci.appveyor.com/project/RoboMWM39862/extrahardmode/build/artifacts

api-version still is not in plugin.yml

Wow, totally forgot about that. Thanks, lol. Just updated the alpha build, the link should always direct to the latest one.

Todo: Revert inclusion of Redstone torches for placement underground Nvm, I didn't do this in the first place.

Thanks. I'm trying to be religious about testing. Anything that makes life easier is good. :)

There looks to be a second 3.13-beta.jar and a new comment (mcstats removal). I am confused. cmp says they are different.

Now that EHM for 1.13.2 is in beta, could the builds go to the DEV releases page:
https://github.com/MLG-Fortress/ExtraHardMode/releases

Idk what cmp is, but yea I did make a few changes before releasing to bukkitdev.

If you can figure out how to make appveyor automatically publish releases (based on a certain commit message?) then I'd be ok with that. Or if you can find a way to automatically create a release/tag on commit.

I've stopped using github releases for release notes for most projects because it's time intensive to account for three different formattings (markdown to html to bbcode). Also I have to upload the jar twice (once here and again on bukkitdev).

Linux cmp compares binary files.

I have no idea how to automate releases. But having one unidentified release at .../artifacts/ is not ideal for users. (Also not a good idea to use the same version for two releases.)

Perhaps the comment could identify the version. That would help a lot.

Well I can add commit hash to version if it matters; since there's not a lot of users using this plugin (or at least these dev builds), I haven't bothered to do that. But I suppose I can add it.

Ok, I'm guessing EHM is basically ready for a 1.13 release. If nothing's found in the next several hours I'll be pushing a release, then as time permits, work on some of the requested features.

Agreed. Good work!