If it IS meant to be a bowl I guess it could be given some depth with shadows while 'empty'? I really like the inkmixer ui, I'm not sure exactly what the thing in the middle is meant to be even in the default one (a little shallow bowl of ink?) but your version portrays it fine. Just looking at things that I can see differ from the older mystcraft patch.īookui_cover isn't changed, could maybe do with one of those sphaxy angular shadow things in a bottom corner and some stitching or embossed sphax logo or something, doesn't need much from the default to make it fit, not sure where the texture is used though so it might not be important. Going through the zip now, I downloaded it yesterday but wasn't able to look at it. NintendoFan for the books which I tweaked slightly and the ink mixer and book binderĬadenDonuts for the books which I tweaked slightly *Tweaked lots of textures which were already nearly doneĬredits Sparkst3r, Akaisama & Slowpoke101 for starting the patch
*Updated: Writing Desk item, inkvial item and inkmask *Updated: Book GUIs (can't say I'm happy with the cover, but it'll do) #Added: inkwell, binder, linkmodifier models #Added: booster, folder, portfolio, wrapper items and scrollbar, tradeshop GUI And lastly for the power item and other input we could add multicables that are a bit like the old bundeled cables from the old rp 2 or like the EnderIO stuff that interact with the most common energy systems.*Updated: MC1.12 downloads to cover everything
When you create a microblock of a tileentity provider the craft will automatically write a method descriptor for the createTileentity method to the nbt of the created "microblock tileentityprovider" when that then gets added to the microblock the tileentity will call the method and add the tileentity to an array from where they can be called if for example someone clicks on the block and on a pixel that happens to be on the rendered texture of a tileentity providing microblock we can call the method of the specific tileentity.Īnd if a tileentity wants to call amethod to interact with the world it will be send to our own implememtation which can make it more fitting to ore microblock standarts. Our implementation of a microblock would generate a tileentity that has our own world implementation that is microlock centered, this world wil replace the internal worldObj variable of the captured tileentity. Sorry if this is a bit more on the techical side but I can't really express it in any other way.
0 kommentar(er)
