• 4

    posted a message on Wither Skeletons stopped spawning
    This should be fixed in CraftBukkit b2452 and will make it in to our next beta release of CraftBukkit for Minecraft 1.4.
    Posted in: Recent Updates and Snapshots
  • 0

    posted a message on Feedback Wanted: Minecraft API Proposal System
    Minecraft API JIRA - Tell us what you'd like to do with the Minecraft API! http://goo.gl/bkQxz
    Posted in: Mods Discussion
  • 0

    posted a message on Feedback Wanted: Minecraft API Proposal System
    Quote from varradami

    Thanks for getting back to us.

    Can you tell us what license you plan to use for the Minecraft API? Or at least whether you plan to release it under an open-source license. Obviously this will affect the community's ability to provide direct coding assistance (which you seem to be assuming, given you talk about how to incorporate pull requests).


    Unfortunately no, we haven't made any decisions on this just yet.

    ---

    Here's a draft of the proposed workflow I'm thinking we'd like to follow for the JIRA:
    • Developer tries to use the API, finds that we don't provide what they're looking for
    • Developer submits a ticket detailing their API addition
    • Ticket goes through public vetting process (as detailed in the MAP system breakdown), volunteer flags it as vetted (labels it with 'checked' or sets ticket status to "Waiting For Reply") and brings it to our attention
    • Mojang discusses the ticket amongst ourselves and comment on the ticket to communicate our decision/concerns
    Posted in: Mods Discussion
  • 5

    posted a message on Feedback Wanted: Minecraft API Proposal System
    Hi everyone,

    Thank you so much for the overwhelming response to our call for feedback on the Minecraft API proposal process! We've been reading and considering each and every bit of feedback people have provided regarding the MAP process since we began this discussion. We hope that discussions like these will help us develop a suitable means for us to work efficiently and effectively with the community to build a powerful and usable Minecraft API.

    I'm glad to see that the Minecraft community is so passionate about the Minecraft API that we kept branching off into discussions on what the API should provide and so on, but I ask that you hold off on that kind of discussion and focus on this one, as that's what this proposed process is for! We want to provide the community with a stage to voice their ideas in a way that is manageable and workable for both the developers in the Minecraft community and us at Mojang and having discussions like this one will greatly help us with achieving that.

    Moving forward, we intend on continuing to collect feedback on the MAP process to help us evolve it and shape it to our needs as we feel is necessary. This process is not set in stone and will definitely be changing over time, but based on the discussions that have been taking place so far, I feel that we are moving in the right direction. That being said, I'll be contacting some developers in the Minecraft community to help us test run the process with early access to the JIRA and then, hopefully, we'll have the entire process up and running soon.

    We were hoping that this discussion might have people suggesting alternative systems to use instead of JIRA, and I'm happy to see that several people have done so. Unfortunately, I've already evaluated quite a few different solutions and, so far, we believe that JIRA will provide us with most of what we need, for the most part and for the time being. While developing a suitable solution ourselves (perhaps with the help of the community) might be an option, I'd be more inclined to use an already established solution as it has been tested and has been proven to be scalable and stable. If you do feel that you have a better solution than JIRA, please feel free to post about it in this thread and we'll see if we can evaluate the suggestion.

    Although I can see the merits of having a wiki as being a part of this process - I understand how it allows for easier and quicker collaboration on fleshing out an idea - I feel like it would just add complexity to this process that we do not need at this time. However, that isn't to say that we won't consider providing something of that nature in the future. We'll just have to see how things go and adapt and change accordingly.

    Please follow me on Twitter for updates on news and communication regarding the Minecraft development community we're hoping to develop over time: http://twitter.com/EvilSeph
    Posted in: Mods Discussion
  • 52

    posted a message on Feedback Wanted: Minecraft API Proposal System
    The following is the breakdown of the system we're looking to use to gather and handle Minecraft API changes. We're planning to employ the use of a JIRA project for proposal gathering, organisation and discussion and GitHub Pull Requests once code becomes involved (and a proposal has been accepted).

    The Minecraft API proposal system is a set of guidelines developers are expected to follow if they want to contribute to the Minecraft API. A Minecraft API proposal (MAP) is a design document detailing the specifications, justification, challenges faced and need for a new addition to the Minecraft API. Every proposal submitted to the official Minecraft API JIRA Project is required to follow the provided template and to meet the following requirements.

    Minecraft API Proposal Requirements:
    • A specific, to the point, summary (JIRA ticket title) should be provided. Vague summaries like "Awesome new feature!" will result in the proposal being rejected.
    • The description of the MAP should contain detailed and justified specifications and challenges faced.
    • The appropriate labels and components should be set to help with organisation and searching of MAPs.
    MAP Template and example:
    Summary: Trading API

    Description:
    Proposed addition:
    Developers should be able to make use of the trading system in the game to set up their own trading system, inventory, prices and results. The trading API should allow developers to attach the ability to trade to any container, not just villagers.

    Specific features:
    • Trade recipe editing
    • Trading related events
    Justification and Use Case:
    A trading API would allow developers to construct a sophisticated merchant system using the chest container.

    Challenges faced:
    None discovered at this time.

    Affects Version/s:

    Component/s:

    Label/s: trading

    After a MAP is properly submitted, each submission has a 2 week grace period before a decision can be made about the proposal, with some exceptions. This is to allow for ample time for the Minecraft developers community to review and comment on each proposal. However, while we are busy building the API for the first time, we may opt to skip the 2 week grace period on a per proposal basis to speed up the API design and development process.

    The original author of the Minecraft API Proposal is expected to present their idea in a convincing manner and garner support from other developers in order to build up a community consensus. Alongside this public vetting process, the Minecraft team will be looking over each MAP and providing input as we feel is necessary and, ultimately, deciding to accept or reject a proposal. If we find that a proposal is popular but we need to reject it for whatever reason, we will usually look into alternatives, fixes or changes to address the issues we have with the proposal.

    Once a MAP is accepted, a reference implementation will be worked on and the entire development process moves over to GitHub and its Pull Request system. In order for a reference implementation to be considered, each pull request has to meet the following requirements.

    Minecraft API Pull Request (MAPR) Requirements:
    • The relevant MAP should be clearly associated and mentioned in the Pull Request title (see the template for an example of the expected format).
    • The relevant MAP should be clearly linked to so discussions about the MAP can be read over if need be.
    • Detailed information from the relevant MAP should be included in the Pull Request's description for easier managing of proposals.
    • Submitted code is expected and required to adhere to our coding guidelines.
    • A vetted MAP covering the Pull Request has to exist before a Pull Request is made.
    Minecraft API Pull Request template and example:
    Title: [MCAPI-1] Trading API

    Description:
    Associated MAP:
    [MCAPI-1] http://link.to.MAP.here

    Proposed addition:
    Developers should be able to make use of the trading system in the game to set up their own trading system, inventory, prices and results. The trading API should allow developers to attach the ability to trade to any container, not just villagers.

    Specific features:
    - Trade recipe editing
    - Trading related events

    Justification and Use Case:
    A trading API would allow developers to construct a sophisticated merchant system using the chest container.

    Challenges faced:
    None discovered at this time.


    Thoughts and feedback on this process are greatly appreciated. We'll be constantly revising this system based on the lessons we learn from it being used and your input will help us with that immensely.
    Posted in: Mods Discussion
  • 0

    posted a message on Minecraft API Discussion - Sat, 20:00 CEST, #minecraftdev on Esper
    Sorry for the lack of followup on the #Minecraft API meeting everyone, I'm busy moving!

    Here are some unofficial summaries/logs from the first Minecraft API meeting:
    Logs (meeting starts at 18:03):
    http://sbnc.khobbits.co.uk/log/logs/old/minecraftdev_[2012-06-30].htm

    Summary:
    https://docs.google.com/document/d/1puSEflHIqFNgSpoHUjr3esYTyYkifkMf0vQ6JDoaGmM/edit
    Posted in: Mods Discussion
  • 3

    posted a message on Minecraft API Discussion - Sat, 20:00 CEST, #minecraftdev on Esper
    I would love to allow more people to participate in the meeting, but we're probably already over the acceptable limit as it is. That being said, I will be playing it by ear - based on how manageable the meeting is with the current amount of people, we may have to add or remove participants accordingly to keep things under control.

    For those of you that are on the list of participants, please join us ahead of time to make sure you are able to talk. If you find that you are unable to talk, please contact me and I will get you sorted out. If you're connecting to the chat and do not already have a registered nickname, please PM me on the forums to verify your identity in the chat.

    Please make sure you keep checking the list of participants as it is subject to change and has probably changed since the last time you looked at it. If you haven't looked at it recently, you might find that you may have been invited to join us in the meeting.

    Furthermore, we will not hesitate to remove any participants both in the meeting channel and in the open discussion channel that are misbehaving to ensure we get the most out of this opportunity. We will be actively monitoring both channels either personally or through a team of volunteer moderators.

    Thanks for your interest in being a part of the beginning of our initiative to involve the community in the API development process! I'm really excited to see how this first meeting goes, based on the list of participants I think it will be pretty awesome :)
    Posted in: Mods Discussion
  • 0

    posted a message on Minecraft API Discussion - Sat, 20:00 CEST, #minecraftdev on Esper
    List of attendees has been updated, though it is not set in stone.
    Posted in: Mods Discussion
  • 0

    posted a message on Minecraft API Discussion - Sat, 20:00 CEST, #minecraftdev on Esper
    Whoops, looks like we lost some important information along the way as we tried to clarify things. We've updated the announcement with the missing information and more. Hopefully this addresses all the concerns people have brought to our attention!
    Posted in: Mods Discussion
  • 0

    posted a message on Minecraft API Discussion - Sat, 20:00 CEST, #minecraftdev on Esper
    Please bear in mind this is an informal meeting and we will not be able to cover everything. But it is also only the first meeting and the beginning of our initiative to involve the community in the API development process.
    Posted in: Mods Discussion
  • 1

    posted a message on Minecraft API Discussion - Sat, 20:00 CEST, #minecraftdev on Esper
    Based on discussions already taking place, it's clear that we need to clarify some things.

    To keep things manageable, we'll most likely have to limit the amount of people that are able to talk. As such, we'll be giving representatives from modding groups that develop a modding platform, like Bukkit, Spout, etc. priority when selecting who will be provided with voice. If we feel that more participants will be manageable, we'll provide other modders with the ability to participate. We wish we could just let everyone talk, but that would be a bit too crazy, sorry.

    I've updated the announcement to reflect this change in information.
    Posted in: Mods Discussion
  • 22

    posted a message on Minecraft API Discussion - Sat, 20:00 CEST, #minecraftdev on Esper
    Note: This is a post from EvilSeph, part of the Minecraft development team.


    Hi everyone!

    While we continue working on the foundation of Minecraft itself, we'd like to get started on our promise to involve the community in shaping the official API by having our first planned Minecraft API discussion. This Saturday we're hoping to have an informal discussion on the community's thoughts and ideas on what they feel the API should provide and how it should be shaped. We already have some topics in mind of our own that we'd like to cover, but we encourage you to prepare some of your own topics of interest for the discussion for you and us to get the most out of the opportunity.

    To keep things manageable, we'll most likely have to limit the amount of people that are able to talk. As such, we'll be giving representatives from modding groups that develop a modding platform, like Bukkit, Spout, etc. priority when selecting who will be provided with voice. If you're a part of a group that is interested in attending, please elect two representatives (one backup in case the first can't make it) and RSVP in a post below.

    If we feel that more participants will be manageable, we'll provide other modders with the ability to participate. We wish we could just let everyone talk, but that would be a bit too crazy, sorry. If you believe that there is a better way to go about doing this, feel free to mention it in a post below and we'll take it into consideration.

    If you're interested in joining us for the discussion, we're planning to hold the meeting this Saturday at 20:00 CEST on the Esper IRC network in the channel #minecraftdev. If you can't make it, we'll be providing logs of the meeting after the fact. For people who won't be actively participating in the meeting, we'll have another channel #minecraftdev-discuss where anyone is able to discuss the current topic in the meeting.

    Who:
    To keep things manageable, we'll most likely have to limit the amount of people that are able to talk. As such, we'll be giving representatives from modding groups that develop a modding platform, like Bukkit, Spout, etc. priority when selecting who will be provided with voice. If we feel that more participants will be manageable, we'll provide other modders with the ability to participate. We wish we could just let everyone talk, but that would be a bit too crazy, sorry.

    If you're a part of a group that is interested in attending, please elect two representatives (one backup in case the first can't make it) and RSVP in a post below.

    What:
    An informal discussion to get an idea for what future discussions should be about, a feel for what ideas people have regarding the API and so on.

    When:
    This Saturday, June 30th 2012, at 20:00 CEST (check what time this is in your time zone).

    Where:
    Moderating meeting will take place in #minecraftdev on the Esper IRC network, irc.esper.net. Regular discussion will be taking place in #minecraftdev-discuss.

    List of Attendees:
    • Afforess from Spout
    • Searge from MCP
    • Amaranth from Bukkit
    • UltraMoogleMan of WEDGE fame
    • RoyAwesome of Spout GUI fame
    • TkTech of #mcdevs and MCEdit fame
    • Jarvix from Canary
    • LexManos from Minecraft Forge
    • FlowerChild of Better Than Wolves fame
    • ShaRose of GuiAPI and ID Resolver fame
    • Cojo of Tropicraft fame
    • Corosus of ZombieCraft and Tropicraft fame
    • medsouz of SocialMiner fame
    • Xie of Xie's Mods fame
    • Snowl of MCForge (classic) and LibMinecraft fame
    • DV8FromTheWorld from Minecraft Port Central
    • Kulttuuri from MinecraftEDU
    • Eloraam of Minecraft Forge and RedPower fame
    • sk89q of WorldEdit, WorldGuard and CraftBook fame

    Agenda:
    • Our plans for involving the community in the API development process for the future.
    • Our considerations on how we might handle contributions.
    • Our plans for keeping the community in the loop.
    • The direction we're taking to prepare for the API.
    • General Q&A.

    Hope to see you there!

    // The Minecraft Team
    Posted in: Mods Discussion
  • 0

    posted a message on 1.1 map structure gets overwritten by 1.2.3 structure.
    Please take this to the thread on the Bukkit forums so I don't have to watch both threads.

    http://forums.bukkit.org/threads/parts-of-map-deleted-after-converted-to-1-2-3.63414/
    Posted in: Legacy Support
  • 0

    posted a message on Introducing Bukkit - a new Minecraft Server mod
    I'm happy to finally announce that a Recommended Build for Minecraft 1.5_02 compatibility is now available.

    See this article for more information:
    CraftBukkit for Minecraft 1.5(_02) available | Bukkit Forums
    Posted in: Minecraft Tools
  • 0

    posted a message on Introducing Bukkit - a new Minecraft Server mod
    Quote from Warpizzle »
    I'm just being impatient here. When will Bukkit be updated to Beta_1.5? All my favorite servers aren't working and I keep getting the errors:

    End of Stream
    or
    Internal Exception: java.netSocketException: Connection reset

    It's really starting to bug me now. Pretty much ALL the good servers that I go to, run on Bukkit...
    :Pig:


    Quote from Sledgehammer123 »
    this really does need to be upated..... its been a while....

    most servers i use ALL use bukket and are in temp worlds making me unable to even finish some of the stuff i have built.....


    We have had a 1.5_02 compatible update done for a while now (2 days ago, infact!). We're just sorting out some really annoying issues before we promote a recommended build.

    See this for more information:
    http://forums.bukkit.org/threads/when-w ... 1-5.13701/

    You can get the test build here, but please remember that it is a TEST ONLY build and shouldn't be used on a production server until you're sure it's fine:
    http://goo.gl/s4pHU

    Sorry that I don't check these forums that often..it always logs me out...
    Posted in: Minecraft Tools
  • To post a comment, please or register a new account.