Mcers

No es la comprensión, es que he leído mal el tendremos. xD

Things are progressing nicely towards our first development build of CraftBukkit for Minecraft 1.7.2. Although this update did not provide or add as much feature-wise as previous Minecraft updates have, this is probably one of the more complicated and larger updates we've had to work with from a mod development standpoint. With "almost all of [the code in Minecraft] having been changed - be it little or big" (according to Mojang), there has been significant shifting around of code and logic - to the estimated tune of 220k lines changed - within Minecraft, resulting in our slowest and most involved update yet.

Managing expectations - information about our initial CraftBukkit 1.7.2 builds
Five days ago (on November 10th) I sent out a tweet trying to describe what our initial findings were regarding the impact this Minecraft update has on the project but it's frustratingly very difficult to communicate everything I want or need to in 140 characters. Nonetheless, sending out tweets is still our best form of communication that doesn't push other important topics out of view (like the potential structure loss PSA).

The tweet was meant to explain that while we will definitely have development builds, our analysis and evaluation of the update (through reading the code and following Minecraft feedback/bug reports from the community) has revealed that there are issues in Minecraft that may prevent us from getting anything stable or reliable out. This was purely meant to assist us with managing expectations as to the quality, stability and reliability of any builds we're able to give out.

As for the 'issues we cannot fix' aspect of the tweet, this is due to the nature and policies of the Bukkit project: it is not so much that we are unable to fix the issues ourselves (though this can sometimes be the case), but rather that the issues present are not the project's responsibility to fix and, instead, would be better addressed by Mojang. While we do sometimes make exceptions if we have a really good reason to do so (like to fix a security issue), we try and avoid altering the way Minecraft itself behaves and functions. This is both a conscious decision as a project and a necessity, as too many changes to Minecraft's inner workings can mean significant increases in the complexity and amount of work required for the update process.

It's not so much that we choose not to fix these issues, but rather that we need to be fully conscious and aware of the impact doing so could have on the update process and our day-to-day maintaining of the project. If the fix for an issue touches too many internals within Minecraft, for example, it usually makes the update process significantly more complex, resulting in (what could be an avoidable) increase in the amount of time it takes us to update. As much as we'd like to fix every issue we come across, doing so would mean updating to new Minecraft versions will take even longer than they currently do.

This is why we have the minimal diffs policy (a policy which eliminates unnecessary changes to the Minecraft code), it results in a speedier and less buggy update for everyone. Although it undoubtedly limits the developers in our project, I think you'll agree that it's a worthy sacrifice and limit to impose upon ourselves in order to ensure that the downtime of your server between updates is as minimal as we can possibly achieve.

If we were not personally responsible for updating the core of our project, we'd have much more freedom to experiment. As it is, however, the Bukkit project handles updating, development and the maintaining of both a plugin API (Bukkit) and a Minecraft server mod (CraftBukkit) in order to produce the server you all know and love.

To be clear:
There WILL be development builds; we're still working towards getting our first one out.
Due to significant changes in how Minecraft works, it will take us a while to get our Bukkit API updated. Hence, it is highly unlikely that all the plugins you are using will work on our initial development builds.
There will MOST LIKELY be promoted builds, but they'll be lower quality than you could usually expect from us due to issues we can't address.
What does updating CraftBukkit involve?
To give you an idea as to why this update is taking longer than usual, I need to briefly touch on what our update process involves. Every time a Minecraft update is released, we have to go through a repetitive, time consuming and dry multi-step process.

A simple breakdown of the process is as follows: decompile the server -> learn the new names (they change with every update) -> figure out how they apply to Bukkit's naming system -> learn what changed/what's new in the update -> update the changes we make to the server to support Bukkit -> get the code to compile -> fix issues that come up.

Since we're working with a code base that is unfamiliar to us, we can sometimes find ourselves having to jump back to a previous step. For example: we may come across a piece of code that we're not familiar with and once we're able to figure out what it does, we realise that we've named something incorrectly which we then have to go back and fix. It is this fluid and unpredictable aspect of the update process that makes it difficult to come up with a communicable ETA or any progress/status updates.

Though this process may seem inefficient or ineffective, this is the same process that we've used and improved upon to get all of our updates out (even our fastest ones) over the 3 years the project has existed. Bear in mind, the overview provided here barely touches the surface of our update process and is intended to give you a remote idea as to what we have to deal with for every update. This brief and simplified breakdown of our 'steps' does little to explain the varying level of difficulty or complexity of each step, for example.

How can I help?
The best way to help us out is to get involved.

If you're a server admin: once we have our first development build out, we'd appreciate any testing you could perform and any issues you can report. Please bear in mind that development builds are unsupported and should not be run on production servers.

If you're a plugin developer: once we have our first development build out with proper API support, we'd appreciate if you could test the build out and report any missing or broken API to our bug tracker.

If you're looking to help us out with the update, you'll have to work towards that goal by getting involved in other aspects of the project first. Due to the sensitive and extremely team oriented nature of the update process, we require that you build a relationship and demonstrate your commitment to the project before getting involved with updating will benefit the process. As the update process is incredibly repetitive and mundane, intense commitment is a key requirement for the team.

We know this update is taking longer than usual but I assure you we are working our hardest to get it done. Thanks for your patience and continued support, it makes a huge difference and really helps us push onward!

Demasiado texto en inglés, no estoy con ganas de traducir tanto xD

Pues yo diría que si es un bug que impide sacar nada mejor que una dev version, creo que es lo suficientemente crítico como para que hicieran algun tipo de hotfix. Vamos, digo yo...porque si no esto se va a alargar hasta la 1.7.3. O más.

Por cierto, a menos que dbu instale esa dev build, me da que hasta 2014 nada de nada.

Bueno que siguen desesperados con los grandes cambios que ha hecho mojang en minecraft y que hay para rato.

Edit: También vuelven a insistir en que están trabajando en ello aunque tarden.

Me quedo con una duda. ¿No se dijo hace varias versiones que Mojang colaboraría en el desarrollo de Bukkit y similares facilitándoles la información antes? ¿Que estaban en contacto y tal?

Si fuese Mojang y tuviese los ingresos que han tenido, no me habría planteado dos veces incorporar al equipo de Bukkit y ponerles un sueldo. El que trabajen en su tiempo libre les limita muchísimo y Minecraft Vanilla no está ni de lejos preparado para mantener servidores públicos como este.

Ya red, eso es de lógica. Pero hablamos de Mojang. Por lo que he leído en sus tweets, prefieren viajar por todo el mundo yendo de guays y snobs por la vida a chorraexposiciones que hacer bien su trabajo. Típico ejemplo de burbujapuntocom, y de una empresa a la que solo les van bien las cosas porque uno de sus productos ha tenido un éxito demencial.

Casi hasta me entran ganas de que suba algún clon del MC a su nivel, aunque sea sólo para que eso les espabilen un poco, y se pongan las pilas.

Y ya sé que esta opinión es un tanto injusta e hipócrita para updates que, al fin y al cabo, recibimos gratis. Pero qué quereis que os diga, preferiría mil veces pagar 2 o 3 pavos por update mayor (cada 1.x, no 1.0.x), y que esa update incluyera de una santa vez el MOD api, la reescritura del motor de render, el Bukkit incorporado y demás features que la comunidad lleva pidiendo desde hace SIGLOS, que no el sistema actual. Y creo que ni al mendigo de la esquina le daría un infarto por 3 pavos cada 3-4 meses.

26 Nov

Seeing rumours; we're NOT withholding a @CraftBukkit 1.7.2 dev build. None exist yet. We're still working hard towards our first one #bukkit

No tienen una versión de desarrollo para la 1.7.2 aún. Siguen trabajando.

Even though #Minecraft 1.7.3 is out next week, seems like it is mostly client fixes, so likely won't affect progress on @CraftBukkit 1.7.2

El lanzamiento de la 1.7.3 no repercutirá en Bukkit

27 Nov

We'll likely have an unsupported, unstable @CraftBukkit 1.7.2 dev build this week if nothing comes up: first dev build that simply compiles

Puede que tengan una versión inestable y sin soporte para la 1.7.2 esta semana, solo para enseñar como será en la 1.7 y ponerse a corregir bugs.

Best bug we've caught before @CraftBukkit dev build? Inivisible, unextinguishable, infinite fire on the ocean floor and everywhere else.

El mejor bug que hemos tenido antes de una versión de desarrollo? Invisible, inextinguible e infinito fuego en el fondo del mar.

Habemus developement build

Since Minecraft 1.7.2 was released on October 25th we've been putting in a ridiculous amount of work non-stop towards a CraftBukkit for Minecraft 1.7.2 and I am happy to finally be able to announce that we now have development builds available. We strongly suggest that you only use this build if you would like to help us get a Beta build out sooner and are experienced with using unsupported development builds.

WARNING: Minecraft 1.7.2 is an update that requires clients to update before being able to connect.

What is a Development Build?
A Development build is provided AS IS and COMPLETELY UNSUPPORTED. You should only be running these builds if you are completely aware of how to properly make use of them. Support requests of ANY KIND will be removed without warning. If you have to ask where or how to get the development build, you should NOT be running it and posts of that nature will be deleted.

Will plugins break with this build?
Minecraft 1.7 is one of the most involved updates to date, with Mojang having touched a reported 220k+ lines of code. As a result, a significant amount of the code base has shifted making it difficult to ensure any stability with regards to our API. That being said, it is difficult to determine if plugins will be breaking with our 1.7.2 update and the state of the API in our earlier development builds should NOT be relied upon in any way.

Enviado desde mi Nexus 4

Traducción cutre con algunos trozos que no entiendo y he recurrido a google pero sin hacerle caso del todo:

Desde que la versión de Minecraft 1.7.2 fue lanzada el 25 de octubre hemos estado con una ridícula (así literal parece que sea poco xD) cantidad de trabajo sin pausa hacia CraftBukkit para Minecraft 1.7.2 y estoy contento de que finalmente poder anunciar que ahora tenemos versiones de desarrollo disponibles. Pedimos que solo uses esta versión si quieres ayudarnos a conseguir la versión Beta más rápido y tienes experiencia usando versiones sin soporte.

ALERTA: Minecraft 1.7.2 es una actualización que requiere que los clientes se actualicen antes de poder conectarse. (Creo que se refiere a lo de pasar de tener tu cuenta de Minecraft a cuenta de Mojang).

¿Qué es una versión de desarrollo?
Una versión de desarrollo se proporciona tal cual se ha hecho (sin testear) y está completamente sin soporte. Solo debes usarlas si eres completamente consciente de como usarlas correctamente. Las solicitudes de apoyo de cualquier tipo serán borradas sin previo aviso. Si tienes que preguntar donde o como conseguir la versión, no debes ("be running it", ni idea) y todos los posts de este tipo serán borrados.

¿Los plugins funcionan con esta versión?

Minecraft 1.7 es una de las actualizaciónes más complicadas hasta la fecha. Mojang ha cambiado o borrado más de 220 mil lineas de código. Como resultado, una cantidad significativa del código base ha cambiado haciendo que sea difícil asegurar cualquier estabilidad respecto nuetra API. Lo dicho (aquí me he medio inventado esto con ayuda de google), es difícil determinar qué plugins se romperán con nuestra actualización 1.7.2 y el estado de la API en el temprano desarrollo no es de confianza.

Aleluia! Habemus Papa (Bukkit)!

Al final mi vaticinio del finde del 10 de Enero para el reset se va a cumplir y todo

27 versiones de desarrollo después, 1 semana después... El lugar donde se reportan los bugs marca que hay 40 bugs sin resolver. Poco a poco

https://bukkit.atlassian.net/issues/?jql=project%20%3D%20BUKKIT%20AND%20issuetype%20%3D%20Bug%20AND%20affectedVersion%20in%20(%22Bukkit%201.7.2-R0.1%22%2C%20%22CraftBukkit%201.7.2-R0.1%22%2C%20Future)%20AND%20status%20in%20(Open%2C%20Reopened%2C%20%22Waiting%20For%20Reply%22)

Forge no tiene la misma suerte...

Mik_C escribió:

Forge no tiene la misma suerte...

Hay una cosa con la que no me aclaro...¿el Forge y el Minecraft Coder Pack son para mods del cliente, y el Bukkit API es para mods del servidor, o como va eso?

Me he acostumbrado a usar mis modcitos de cliente, pero por mí pasaría de ellos una temporada si es menester...preferiría que hubiera reset después de que volvieran a actualizar el Bukkit (que por lo que parece por esa lista de bugs, la beta está relativamente próxima), y no tener que esperar también a que actualizaran esos otros dos.

...aunque si se hace la actualización del Bukkit entre el 18 y el 8 de Enero...esperadmeeee, porfiii, que no estaré ;_(

mas o menos:

MCP es una herramienta para crear mods tanto para server como para cliente. Si haces un mod con MCP lo tienes que hacer todo a pelo y puedes tener problemas de compatibilidad con otros mods.

Forge usa MCP, Forge te proporciona una API y herramientas para facilitar la creación de mods (cliente o servidor), y facilita la comunicación entre la parte servidor y cliente de tu mod. También ayuda a tener mods compatibles entre si, tu mod no necesita sustituir las clases en el minecraft.jar.

Bukkit es una API para servidor. Define eventos y objetos que usaran los plugins.

Craftbukkit es una implementación de esa API, es un mod de servidor.

Para el servidor principal no necesitamos esperar a MCP o Forge para nada, simplemente que craftbukkit y los plugins sean estables.

¡Chachipiii!

(Abreviación de "Chachipiruli"...¡usadla a partir de ahora! ).