Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Search the Community

Showing results for tags 'feature'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Minecraft Forge
    • Releases
    • Support & Bug Reports
    • Suggestions
    • General Discussion
  • Mod Developer Central
    • Modder Support
    • User Submitted Tutorials
  • Non-Forge
    • Site News (non-forge)
    • Minecraft General
    • Off-topic
  • Forge Mods
    • Mods

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


XMPP/GTalk


Gender


URL


Location


ICQ


AIM


Yahoo IM


MSN Messenger


Personal Text

Found 3 results

  1. Hey, I've been recently playing a lot with TRSRTransformation class and I realized that it could probably be easier to use a builder for it rather than passing a million arguments (I know it's just 4, but it looks neater). Let me show you what I mean. First, a few arguments why I even created a TRSR Util class: 1) I didn't know that there were cornerToCenter and centerToCorner methods and at first, they confused me since any rotation I do happens around the center of the block. (I think the majority of modders want it like that). 2) Quaternions. I don't think anybody uses quaternions to in their head to picture a rotation. I know that there are static methods in the TRSRTransformation class to get a quaternion from XYZ degrees, but that makes a horrible mess. 3) Readability. Tell me what is easier to read: TRSRTransformation tr = new TRSRTransformation(new Vector3f(0, 10F, 0), new Quat4f(0, 0.125F, 1, 0), new Vector3f(1, 1.25F, 1), null); VS TRSRTransformation tr = new TRSRTransformation.Builder() .translate(0.125F, 0, 0) .rotate(0, 90, 0) .scale(2, 2, 2) .postRotate(90, 0, 0) .build() You could even specify in the Builder's constructor if you want to use the corner or center version as a boolean variable (true - center, false - corner). And then, the Builder would do all the messy work, while you would just move on with your life. I can even provide a working Builder class I made myself if you all think that this would be a great addition, no matter how small it is, it would help modders a lot.
  2. Hey guys! I just recently reset my entire computer and started to reinstall certain programs. This time, I plan on trying to slimline my IDEs (I had about 5 in total: Visual Studio Code, Visual Studio Community, IntelliJ, Eclipse, and Android Studio).The one I plan to converging everything under is Visual Studio Code, as I can add in different plugins to work with it, especially since I'm starting to use that IDE for developing my Powershell program to run my server. Just curious if I can squash down my several IDEs (with the exception of Android Studio) into one.
  3. Hi, I'm currently struggling with the hole energy system stuff. I've worked myself so far into the Capabilities that I can work with the Tesla Energy system and Forge Energy system and I know that mods who support both have some kind of internal energy. My problem now is that I've got no idea how I can combine all the pieces of Forge Energy and Tesla Energy together, so that my machines can work with boths. And I definitly don't want to have thousands of lines twice just because if-else cases for checking the which energy system is used and stuff like that, because that would be very inefficient. Before someone now says, look into EnderIO because it does those things: I know that EnderIO has exectly what I want, that machines can support both energy systems, but even after looking into the forge docs and into the source code 20 times... I just don't understand why it is done there in that way and for what some of those methods are.... So I hope there is someone who can help me with getting all those pieces together. Thx in advance. Bektor
×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.