Jump to content

LexManos

Forge Code God
  • Posts

    9264
  • Joined

  • Last visited

  • Days Won

    66

Posts posted by LexManos

  1. It should be unlike the majority of other 'apis' out there, we are:

    open

    continuously evolving

    working with the community

    providing things modders needs

    trying to help prepare modders for the fabled api.

    etc...

    If you're a modder, you should try out forge. It make take a little bit to get used to, but it is worth it.

     

  2. Not going to dig through all of your code, so linking to specific files would help.

    But I dont get the 'merging together' part, seems to me like you're fucking something up if things are getting merged together.

    its not difficult to transfer something over the network and pick it up on the other side.

  3. With the imminent drop of 1.3.2 we've decided not to release officially for 1.3.1. {Though as you can see, there are plenty of builds that work for 1.3.1}

    Current jenkins builds are for 1.3.2, so get to testing.

    As long as we get good feedback. I plan on making a official release when 1.3.2 drops.

     

  4. I was going to take a look into this after the first official release.

    What I was going to do was add a pair of arrows to the open space on the top right in the main square.

    And just have it cycle through 'pages' of tabs.

    That way you keep the sexy look that is the new creative gui, but allow for an arbitrary number of pages.

  5. How exactly is having one item overwrite another not conflicting?

    Things may not explode right away no. But I'm sure modders would fuck something up and expect oen things from the item that isnt there if it's overwritten.

    Like reading the item from the list and trying to cast it to it's internal class, for example.

    Either way, advocating id conflicts is still retarded.

    Modders just need to learn to work together.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.