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

Skullblade

Members
  • Content Count

    102
  • Joined

  • Last visited

Community Reputation

1 Neutral

1 Follower

About Skullblade

  • Rank
    Creeper Killer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Good to know. Thank you for your help, and sorry for not understanding earlier.
  2. You know, the code thingy. In the DefaultBiomeFeatures you sent me to, each builder has a different p_ number thing, like p_243731_0_ or p_243734_0_. I didn't know if I needed one, but apparently event.getSpawns() works. The instructions about removing the bloodghastSpawns were unclear, but I think it should look something like this. You know, without the errors. The underlined section in red is asking for an EntityClassification, and I gave it an EntityType. But I don't believe I have a classification to give it. I tried 'classification' and 'PlaneswalkerEntities.classification' bu
  3. Which method is wrong and how would I use the event? I can't do much about it if you're not specific. In addition, I believe I had asked what the p_ builder number thing was for this specific instance. When looking at the farm animal code and the monster code, there were two different p_ things. (I don't know what they're called, I just dislike their existence)
  4. Ok, so I have this now. Is there a specific code I need to enter in genericName's place (I chose a temporary name because I didn't know what to use) or can I name it something easier to remember?
  5. Ok, how would I register it? Is there an annotation or something?
  6. I know this isn't all of what you were asking, but I wanted to know if I was on the right track. I'm not sure where to go from here. Not sure where to check for methods, or what logic to code in.
  7. They are examples for printing out text in the console whenever an event goes off, not for telling a custom entity what biomes and conditions it can spawn in. I've followed all of HarryTalks' 1.14/1.15 tutorials up to now (he has a play list in order on YouTube) and I haven't had problems like this before. I refuse to believe that I need to subscribe the event when he doesn't have to in the tutorial. Yeah, I know they're old, but the only change that I know of between those versions and the current ones is MCP to Mojang. I shouldn't have to deviate from the tutorial this much to make a simple
  8. 1. I have no clue where to put the code 2. There's barely any code to begin with So, I'm guessing here. I'm starting by creating an Event Handler class. I don't know what to put in it.
  9. I believe I already did up above when I sent those screenshots. If you need me to try/show something else, let me know.
  10. How would I get my code to that point then?
  11. Well, I guess I got a bad tutorial then.
  12. Even if I was to go back and find another Java tutorial, I would just end up coming back here to ask the exact same questions, because no regular Java tutorial would cover Forge. But, if you're okay with rehashing this conversation in a few days/hours/etc., then I'll do it.
  13. Pretty sure @SubscribeEvent is part of Forge, not Java. It wasn't covered in the tutorials I found online. However, if you could recommend a video or something of how to use @SubscribeEvent, that would be great. I searched for some on YouTube and I was only able to find tutorials on Event Listeners and stuff.
  14. It didn't work. I got an error that I couldn't put annotations anywhere other than the line directly above the start of the code, in this case, above public static void registerEntityWorldSpawn. I reread the article, and tried various things, but it's still not working. First, I tried to do what was shown in the first example and put the code in public class staticForgeEventHandler and subscribe the event inside, but I got this: After this didn't work, I tried to add that register thing at the end of the second example, but that didn't work at all.
×
×
  • Create New...

Important Information

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