• Inventory Split Incoming

    MassiveCraft will be implementing an inventory split across game modes to improve fairness, balance, and player experience. Each game mode (Roleplay and Survival) will have its own dedicated inventory going forward. To help players prepare, we’ve opened a special storage system to safeguard important items during the transition. For full details, read the announcement here: Game Mode Inventory Split blog post.

    Your current inventories, backpacks, and ender chest are in the shared Medieval inventory. When the new Roleplay inventory is created and assigned to the roleplay world(s) you will lose access to your currently stored items.

    Important Dates

    • April 1: Trunk storage opens.
    • May 25: Final day to submit items for storage.
    • June 1: Inventories are officially split.

    Please make sure to submit any items you wish to preserve in the trunk storage or one of the roleplay worlds before the deadline. After the split, inventories will no longer carry over between game modes.

Archived X

  • Thread starter Thread starter Violettee
  • Start date Start date
This suggestion has been archived / closed and can no longer be voted on.
This suggestion has been closed. Votes are no longer accepted.
I remember this feature was enabled on massive back 5+ years ago. Dont believe there were any negatives.
 
I'd be in favor of this idea under the condition that it was opt-out. For example, roleplayers necessarily don't want to see "<X> joined the game", so an implementation into MassiveChat with the command, oh let's say /c wm <on|off> (wm being welcomemessage and c being the root command) would be the only feasible implementation for such an idea.

Tagging @CS_Birb and @TheComputerGeek2 for their thoughts.
 
I'd be in favor of this idea under the condition that it was opt-out. For example, roleplayers necessarily don't want to see "<X> joined the game", so an implementation into MassiveChat with the command, oh let's say /c wm <on|off> (wm being welcomemessage and c being the root command) would be the only feasible implementation for such an idea.

Tagging @CS_Birb and @TheComputerGeek2 for their thoughts.
We could potentially accomplish this with the implementation of a "welcome chat" channel if I am not mistaken.
 
We could potentially accomplish this with the implementation of a "welcome chat" channel if I am not mistaken.
After speaking with Birb on this, Tech agrees that introducing a chat channel specifically for these announcements would be the best way to go.
 
I think this is a good idea. But that depends if Tech can get it done without it impeding on sharding work.
 
This idea will be added to Techs list of tasks. It will be low priority because of obvious high priority issues (Sharding and TPS issues etc.) Great idea, nonetheless.