• designer10
• designer11
• designer12

Since some don't work with WASD, so I propose that we make it toggleable, either using blocks/code or using WASD

Adventuruer:

• adventurer01
• adventurer02
• adventurer03
• adventurer04
• adventurer05
• adventurer06
• adventurer07
• adventurer08
• adventurer09
• adventurer10
• adventurer11
• adventurer12
• adventurer13
• adventurer14

Agent:

• agent01
• agent02
• agent03
• agent04
• agent05
• agent06
• agent07
• agent08
• agent09
• agent10
• agent11
• agent12

Aquatic:

• aquatic01
• aquatic02
• aquatic03
• aquatic04
• aquatic05
• aquatic06
• aquatic07
• aquatic08
• aquatic09
• aquatic10
• aquatic11
• aquatic12

Designer:

• designer01
• designer02
• designer03
• designer04
• designer05
• designer06
• designer07
• designer08
• designer09

Functionality:

• functionality01
• functionality02
• functionality03

Increase parity with other versions of Minecraft

• make redstone not power instantly
• Make pistons not break when pushing a block that another piston is pushing
• Allow redstone to power through blocks

Remove jquery from the code for optimizations.

Integrate Blockly, and add custom blocks for exposing the following functions:

• Mob AI,
• Agent programming,
• Player programming,
• Custom JS execution,
• Setting world time,
• Direct world/level/map modification.

If there are more APIs we should expose, feel free to comment them.

Migrate to either Phaser-CE (2.7.0+) or Phaser 3.

• Yeet jQuery: It's not needed at all. Easy; high priority.
• Clean-up HTML and CSS code. Easy; medium priority.
  Clean-up JSON files. Difficult; high priority.

I'm probably missing something, will add it later.

There are numerous pull requests open on code-dot-org/craft which introduce new features to the game. Provided they function, they should be merged over here with credit given to the original author of the commits.

The following features should be implemented:

• Inventory. It's internally implemented, so expose it. Easy; high priority.
• Basic mob AI (e.g. zombies following players, creepers exploding). Difficult; medium priority.
• Level saving. Easy; low priority.
• Level generation. Medium difficulty; Medium priority.
• Crafting. Unknown difficultly; Medium priority.

Something else? Feel free to propose new features.

Some maps depend on the day night cycle, however in the current build it is frozen and never advances.

I suggest we implement a tag that can be added to a level’s definition allowing us to freeze or unfreeze day/night cycle in a specific level, aswell as a tag for starting state, either day, or night.

When defining levels we are able to define terrain features and starting player/mob positions. I move that we should also have an api for defining starting code.

While this would introduce some inconsistencies, specifically in the mob spawning api (spawning mobs via the level api vs spawning them using api code run on level load) I think it would benefit both users of craft-engine and level designers overall.

For level designers it would allow them to hardcode mob ai, as well as set up block interactions.

For end users it would allow easy modding, just load a level and modify its code. It would also let users gain more familiarity with the level’s they are playing without also compromising the original play style of craft.