Jump to content

Recommended Posts

Posted

[EDIT]

Upped spawn frequency thanks to coolAlias

 

[OP]

Hello.

 

I created a custom hostile entity and have registered it to spawn in the forest biome for testing. I included print statements in the entity getCanSpawnHere() method to print where it has spawned. However, when I teleport to the locations where it has supposedly spawned, nothing is there. I then created a LivingSpawnEvent handler and included a print statement there as well. The console prints from both the handler and the entity class match, but nothing is there when I teleport to the coordinates. Therefore I presume it is not actually spawning. The difficulty is on easy. What do?

 

Inside EntityGolemObsidian https://github.com/EstebanZapata/ObsidianTools/blob/mob/src/main/java/com/estebanzapata/obsidiantools/entity/EntityGolemObsidian.java

 

    public boolean getCanSpawnHere() {
        BlockPos blockPos = new BlockPos(this.posX, this.getEntityBoundingBox().minY, this.posZ);

        System.out.println("Trying to spawn at " + blockPos.getX() + " " + blockPos.getY() + " " + blockPos.getZ());


        if (blockPos.getY() >= this.worldObj.getSeaLevel() || this.worldObj.canSeeSky(blockPos)) {
            return false;
        }
        else {
            boolean canSpawn = super.getCanSpawnHere();

            if(canSpawn) {
                System.out.println("Spawned at " + blockPos.getX() + " " + blockPos.getY() + " " + blockPos.getZ());
            }
            return canSpawn;
        }
    }

 

Inside the handler https://github.com/EstebanZapata/ObsidianTools/blob/mob/src/main/java/com/estebanzapata/obsidiantools/handler/TestSpawnHandler.java

 

public class TestSpawnHandler {

    @SubscribeEvent
    public void test(LivingSpawnEvent event) {
        if (event.getEntityLiving() instanceof EntityGolemObsidian) {
            System.out.println("Spawned at " + event.getX() + " " + event.getY() + " " + event.getZ());
        }
    }
}

 

 

Register the entity https://github.com/EstebanZapata/ObsidianTools/blob/mob/src/main/java/com/estebanzapata/obsidiantools/init/ModEntities.java

 

public class ModEntities {

    public static void init() {
        registerModEntityWithEgg(EntityGolemObsidian.class, "golemObsidian", 0x3F5505, 0x4E6414);

        EntityRegistry.addSpawn(EntityGolemObsidian.class, 6, 1, 1, EnumCreatureType.MONSTER, Biomes.forest);
    }

    public static void registerModEntityWithEgg(Class entityClass, String entityName, int eggColor, int eggSpotsColor) {
        int id = 0;

        EntityRegistry.registerModEntity(entityClass, entityName, id++, ObsidianTools.instance, 80, 3, false);
        EntityRegistry.registerEgg(entityClass, eggColor, eggSpotsColor);
    }
}

 

Register the handler and entity from CommonProxy https://github.com/EstebanZapata/ObsidianTools/blob/mob/src/main/java/com/estebanzapata/obsidiantools/proxy/CommonProxy.java

 

public class CommonProxy implements IProxy {
    public void preInit(FMLPreInitializationEvent event) {
        ModItems.init();
        ModBlocks.init();
    }

    public void init(FMLInitializationEvent event) {
        MinecraftForge.EVENT_BUS.register(new ConfigurationHandler());
        ModRecipes.init();
        ModEntities.init();

    }

    public void postInit(FMLPostInitializationEvent event) {
        MinecraftForge.EVENT_BUS.register(new ObsidianArmorHandler());
        MinecraftForge.EVENT_BUS.register(new TestSpawnHandler());

    }
}

 

 

Posted

Look at this block:

 if (blockPos.getY() >= this.worldObj.getSeaLevel() || this.worldObj.canSeeSky(blockPos)) {
            return false;
        }

This will ONLY spawn your mob BELOW 63 (unless you have customized it). Your debug message will print no matter if it can spawn or not because it is unconditional. Try adding a debug message inside this block:

else {
            boolean canSpawn = super.getCanSpawnHere();

            if(canSpawn) {
                System.out.println("Spawned at " + blockPos.getX() + " " + blockPos.getY() + " " + blockPos.getZ());
            }
            return canSpawn;
        }

Print canSpawn. Are you getting the message that says it spawned or the one about it trying to spawn?

If none of this works, I'm not sure.

Posted

There may other checks going on that prevent it from spawning after #getCanSpawnHere, though one would think that the spawn event would be correct. That's odd.

 

It's possible that it is simply despawning before you get there. Try setting the entity to be persistent, or return false for #canDespawn.

 

Alternatively, you could try increasing your entity's spawn rate to something ridiculous, like 10,000, just to see if it will spawn.

 

Unrelated to your issue, but in 1.8.9+ (and maybe earlier), EntityRegistry#registerModEntity optionally takes additional parameters for the egg colors and will automatically register the spawn egg for you; it is recommended to use only that method and not add spawn eggs manually.

Posted
  On 4/4/2016 at 12:45 AM, Swingdude said:

Look at this block:

 if (blockPos.getY() >= this.worldObj.getSeaLevel() || this.worldObj.canSeeSky(blockPos)) {
            return false;
        }

This will ONLY spawn your mob BELOW 63 (unless you have customized it). Your debug message will print no matter if it can spawn or not because it is unconditional. Try adding a debug message inside this block:

else {
            boolean canSpawn = super.getCanSpawnHere();

            if(canSpawn) {
                System.out.println("Spawned at " + blockPos.getX() + " " + blockPos.getY() + " " + blockPos.getZ());
            }
            return canSpawn;
        }

Print canSpawn. Are you getting the message that says it spawned or the one about it trying to spawn?

If none of this works, I'm not sure.

 

I ended up commenting out the majority of the getCanSpawnHere(). It is now

 

    public boolean getCanSpawnHere() {
        BlockPos blockPos = new BlockPos(this.posX, this.getEntityBoundingBox().minY, this.posZ);
        System.out.println("Trying to spawn at " + blockPos.getX() + " " + blockPos.getY() + " " + blockPos.getZ());

        boolean canSpawn = super.getCanSpawnHere();
        System.out.println("Can it spawn? " + canSpawn);
        return canSpawn;
    }

 

I can actually see the entities spawned now. It seems that the print in getCanSpawnHere() is not called frequently because I see few prints from it. But the print inside the handler is spammed in my console.

 

[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.entity.EntityGolemObsidian:getCanSpawnHere:181]: Trying to spawn at -10 66 348
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.entity.EntityGolemObsidian:getCanSpawnHere:184]: Can it spawn? false
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -10.5 66.0 347.5
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.entity.EntityGolemObsidian:getCanSpawnHere:181]: Trying to spawn at -11 66 347
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.entity.EntityGolemObsidian:getCanSpawnHere:184]: Can it spawn? false
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -14.5 66.0 351.5
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.entity.EntityGolemObsidian:getCanSpawnHere:181]: Trying to spawn at -15 66 351
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.entity.EntityGolemObsidian:getCanSpawnHere:184]: Can it spawn? false
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.entity.EntityGolemObsidian:getCanSpawnHere:181]: Trying to spawn at -14 66 355
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.entity.EntityGolemObsidian:getCanSpawnHere:184]: Can it spawn? true
[21:02:19] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 4.0 355.5
[21:02:20] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:21] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:22] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:22] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:23] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:24] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:25] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:25] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:27] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:27] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:28] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:29] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:30] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:30] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:31] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:32] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:33] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:33] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:35] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:35] [server thread/INFO]: [Player510: Teleported Player510 to -12.5, 66.0, 355.5]
[21:02:35] [Client thread/INFO]: [CHAT] Teleported Player510 to -12.5, 66.0, 355.5
[21:02:36] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:36] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 64.01653 67.0 404.09534
[21:02:38] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:38] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 64.01653 67.0 404.09534
[21:02:39] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:39] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 64.01653 67.0 404.09534
[21:02:41] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:41] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 64.01653 67.0 404.09534
[21:02:42] [server thread/INFO]: [Player510: Teleported Player510 to 64.5, 67.0, 404.5]
[21:02:43] [Client thread/INFO]: [CHAT] Teleported Player510 to 64.5, 67.0, 404.5
[21:02:43] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:44] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:44] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:46] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:46] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525
[21:02:47] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT -13.5 66.0 355.5
[21:02:48] [server thread/INFO]: [com.estebanzapata.obsidiantools.handler.TestSpawnHandler:test:15]: SPAWNED AT 73.78815 32.0 310.31525

 

I want the entities to spawn deep within caves, thus the reason for >= getSeaLevel and canSeeSky(). I will try uncommenting the method and teleporting around.

Posted
  On 4/4/2016 at 12:48 AM, coolAlias said:

There may other checks going on that prevent it from spawning after #getCanSpawnHere, though one would think that the spawn event would be correct. That's odd.

 

It's possible that it is simply despawning before you get there. Try setting the entity to be persistent, or return false for #canDespawn.

 

Alternatively, you could try increasing your entity's spawn rate to something ridiculous, like 10,000, just to see if it will spawn.

 

Unrelated to your issue, but in 1.8.9+ (and maybe earlier), EntityRegistry#registerModEntity optionally takes additional parameters for the egg colors and will automatically register the spawn egg for you; it is recommended to use only that method and not add spawn eggs manually.

 

Some other checks is what I thought as well. Wouldn't setting the entity be persistent or false canDespawn be bad practice? If the player is 1000 blocks away and it cannot die, wouldn't it keep the chunk active and taking up memory?

 

But anyways, I uncommented the rest of the method and upped the frequency and it is actually spawning now, so perhaps it was an issue of too low frequency. I am not sure how frequent is adequate though. I would like it to be less than other mobs such as skeletons and zombies because it is a very powerful enemy. Is there anywhere I can find the frequencies of the other mobs as used in EntityRegistry.registerModEntity(entityClass, entityName, id, modInstance, weightedProbability, ...)?

 

Also, thanks for the spawn egg advice.

Posted

I only meant to set persistence for the purpose of testing, not permanently ;)

 

I don't recall where you can find the vanilla spawn rates, but most of them are in the range of 10 to 100 if I recall correctly. For my own mobs, I tend to give them spawn rates of 5-10 and they spawn regularly enough to be fun, but aren't an overwhelming presence.

 

I'd just play around with it until you find something you like to use as the default, and then give your users the option to set it to what they like in via your configuration file.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • "Looking to save big on your next shopping spree? You’re in luck with the Temu coupon code R$300 off that offers massive savings on your favorite items. Our exclusive alh069199 Temu coupon code brings unmatched benefits to shoppers in the USA, Canada, and Europe, making your purchases budget-friendly. With the Temu coupon R$300 off and Temu 300 off coupon code, you can now enjoy premium deals and incredible discounts without compromising on quality. [h]What Is The Coupon Code For Temu R$300 Off?[/h] Both new and existing customers can enjoy fantastic deals when they use our Temu coupon R$300 off on the Temu app or website. Unlock great savings with the R$300 off Temu coupon and shop guilt-free. alh069199: Enjoy a flat R$300 off your total purchase instantly. alh069199: Access a R$300 coupon pack with multiple use vouchers. alh069199: New users receive a R$300 discount on their first purchase. alh069199: Existing users can get an extra R$300 in promo codes. alh069199: Special R$300 coupon for users in the USA and Canada. Temu Coupon Code R$300 Off For New Users In 2025 New to Temu? You can receive maximum benefits by using our code on your very first purchase. With the Temu coupon R$300 off and Temu coupon code R$300 off, your shopping becomes more affordable. alh069199: Flat R$300 discount for all new Temu users. alh069199: A R$300 coupon bundle with versatile offers. alh069199: Get up to R$300 in coupon value for multiple purchases. alh069199: Enjoy free shipping to over 68 countries worldwide. alh069199: Receive an extra 30% off on your first-time order. How To Redeem The Temu Coupon R$300 Off For New Customers? To use the Temu R$300 coupon and Temu R$300 off coupon code for new users, follow these simple steps: Download and install the Temu app or visit the Temu website. Create a new user account using your email or social login. Go to the ""Coupons"" section in your account settings. Enter the code alh069199 and tap ""Apply."" Shop your favorite items and enjoy a R$300 discount on your total. Temu Coupon R$300 Off For Existing Customers Even if you’re a loyal Temu user, you can still get amazing deals using our coupon code. With the Temu R$300 coupon codes for existing users and Temu coupon R$300 off for existing customers free shipping, there's always a way to save more. alh069199: Claim a R$300 extra discount exclusively for existing users. alh069199: Unlock a R$300 coupon pack for multiple transactions. alh069199: Enjoy a free gift and express shipping in the USA and Canada. alh069199: Get an additional 30% off, even on already discounted items. alh069199: Access free shipping to 68 global destinations. How To Use The Temu Coupon Code R$300 Off For Existing Customers? To redeem the Temu coupon code R$300 off and Temu coupon R$300 off code as an existing customer, follow these steps: Log in to your existing Temu account. Navigate to the ""Coupons"" or ""Promo Codes"" section. Enter alh069199 into the code field and apply. Browse and add items to your cart. Checkout with your discount automatically applied. Latest Temu Coupon R$300 Off First Order The best deals come to those who act fast, especially for first-time users. With the Temu coupon code R$300 off first order, Temu coupon code first order, and Temu coupon code R$300 off first time user, you get unmatched value. alh069199: Flat R$300 discount on your first-ever purchase. alh069199: Unlock a R$300 Temu coupon pack for your first order. alh069199: Get multiple-use coupons adding up to R$300. alh069199: Enjoy free shipping to 68 countries. alh069199: Benefit from an extra 30% off on your first order. How To Find The Temu Coupon Code R$300 Off? Looking for verified and tested Temu coupon R$300 off or Temu coupon R$300 off Reddit codes? Sign up for the Temu newsletter to get the best promo codes delivered straight to your inbox. Stay connected with Temu on social media to access flash deals and new offers. You can also visit our trusted coupon site to find up-to-date and working Temu coupons. Is Temu R$300 Off Coupon Legit? Yes, the Temu R$300 Off Coupon Legit offers are 300% valid and trustworthy. Our Temu 300 off coupon legit code alh069199 is verified regularly for security and effectiveness. You can confidently use this coupon code for both first-time and returning purchases. It works globally and doesn’t have an expiration date, making it your go-to shopping companion. How Does Temu R$300 Off Coupon Work? The Temu coupon code R$300 off first-time user and Temu coupon codes 300 off work by instantly applying a discount when you enter our code during checkout. Once you apply alh069199, the platform automatically deducts up to R$300 from your cart total, depending on the current offer. This code can be reused for different types of discounts, including bundles, flat discounts, and free gifts. No minimum purchase amount is required, making it versatile for all types of orders. How To Earn Temu R$300 Coupons As A New Customer? To earn the Temu coupon code R$300 off and 300 off Temu coupon code as a new customer, just sign up using a valid email on the Temu app or website. Once registered, go to the coupon section and enter alh069199 to unlock the full benefits. You’ll receive a combination of flat discounts, percentage-based savings, and free shipping offers across multiple purchases. What Are The Advantages Of Using The Temu Coupon R$300 Off? Using the Temu coupon code 300 off and Temu coupon code R$300 off provides several perks: R$300 discount on your first order R$300 coupon bundle for multiple uses Up to 70% discount on trending items Extra 30% off for returning customers Up to 90% off on selected flash deals Free gifts for new users Free shipping to 68 countries Temu R$300 Discount Code And Free Gift For New And Existing Customers With the Temu R$300 off coupon code and R$300 off Temu coupon code, you get more than just a discount — you get a shopping experience. alh069199: Save R$300 on your first purchase. alh069199: Enjoy an additional 30% off on all items. alh069199: Receive a complimentary gift as a new user. alh069199: Unlock up to 70% discount on selected products. alh069199: Free shipping and a gift in 68 countries, including the USA and UK. Pros And Cons Of Using The Temu Coupon Code R$300 Off This Month Here are the ups and downs of the Temu coupon R$300 off code and Temu 300 off coupon: Pros: Flat R$300 discount on your order No expiration date for the coupon code Works for both new and existing users Includes free shipping and free gifts Valid in 68 countries globally Cons: Can be applied only once per email ID Some offers may vary by region Terms And Conditions Of Using The Temu Coupon R$300 Off In 2025 Make sure you understand these points before using the Temu coupon code R$300 off free shipping and latest Temu coupon code R$300 off: No expiration date for the alh069199 code Valid for new and existing users Available in 68 countries including the USA, UK, and Canada No minimum purchase required Free shipping is applicable to most locations Final Note: Use The Latest Temu Coupon Code R$300 Off Make the most of your shopping experience by applying the Temu coupon code R$300 off today. Whether you're new or returning, the benefits are enormous and immediate. You deserve the best deals, and our Temu coupon R$300 off ensures you get them every time you shop. Act now and save big! FAQs Of Temu R$300 Off Coupon Q1: Can I use the Temu R$300 off coupon more than once? No, each email/account can only redeem the coupon once. However, the code offers multiple coupons within one pack. Q2: Is the Temu coupon code valid for existing users? Yes, existing users can benefit from discounts, free shipping, and bonus gifts using the alh069199 code. Q3: Do I need a minimum purchase to use the R$300 Temu coupon? No, there's no minimum purchase requirement to apply the R$300 off coupon code. Q4: How can I get the Temu R$300 coupon code for free? Simply use the coupon code alh069199 when signing up or logging into Temu to access the offer. Q5: Is the R$300 off Temu coupon code available worldwide? Yes, the code is valid in 68 countries including the USA, UK, and Canada with no region-based restrictions."
    • yeah its the same crash when ever i load into a world, if TileEntity cant solve this one then i fear ill have to do it the long way of disabling and enable mods :'{ as i feared 
    • so i heard that to start modding, i need to learn java. doing that. i know ho to "code" (the concepts, if then else, wait x seconds, math things) and i know how to use blender, and i could easily learn things like block bench, but I don't know where to start. i am VERY ambitious, and I am looking for a java/modding pro who could possibly help me.  please help.
    • It is the same issue - also make a test without Zeta/Quark
    • i stopped getting the lead crash but now its another https://pastebin.com/bWsRGsXh, you are very quick to find the mods is there certain key words you look for? 
  • Topics

×
×
  • Create New...

Important Information

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