Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Draco18s

Members
  • Joined

  • Last visited

Everything posted by Draco18s

  1. Because it doesn't call new every time.
  2. There's an AddCapabilities event. Register a listener for the ItemStack one, and when it fires, add an ItemHandler capability to it.
  3. Items don't have Capabilities, ItemStacks do.
  4. ....No. No it does not. Go learn some basic Java and come back in a couple weeks.
  5. Nested quotes are impossible to read (where does one quote start and the next one end?) Example: (Preview does not show the quotes)
  6. "Jump to new post" doesn't always jump me to the newest post, but rather the bottom of the page. https://dl.dropboxusercontent.com/u/7950499/2017-02-04 20-11-03.mp4 While that time there was only 1 new post, the last time I checked that thread there were at least three and I still ended up at the bottom of the page.
  7. Your link is 404
  8. I think that would be a Forge PR on github.
  9. That one isn't. https://dl.dropboxusercontent.com/u/7950499/2017-02-03 22-53-11.mp4
  10. EntityItem#getItem If I recall the method name correctly.
  11. Just discovered that I can't view spoiler sections. They just don't open. (No apparent JS errors)
  12. 1) You have posted in teh wrong section. This board is for people who write mods. You want the Support & Bug reports section. 2) Your error is in Chisels and Bits, so go bitch at them, not Forge.
  13. There isn't. The entire rendering system changed to use block and item JSON model files.
  14. The problem there is that block and metadata information is now encapsulated inside an IBlockState object.
  15. "I need help converting this" *Giant ass code block* No, do it yourself. If you want help with something specific, ask for something specific. We're not going to update your mod class by class for you.
  16. Also, !(a == b)? Why not a != b? Also, getBlock can never return null for a block in the world: every block is non-null even air, it's Blocks.AIR
  17. I was intending to be nice ("the style is pretty meh, but this very helpful button is in the worst spot, OH GOD WHY CAN'T I START THREADS"), but I had to fight with the forums to even post, and my patience ran out. It wasn't anger at Lex or the Forge team, it was anger at the forum software, just so we're clear. You can actually see my opinion degrade and my anger rise as my opening post goes on. Erf. I thought so, but I couldn't find anything that would have blocked said editor from doing its "thing" even after I disabled Ghostery, Greasemonkey, and Stylish. Errors... lets find out....
  18. OH FOR FUCK'S SAKE, IT STRIPS CARRIAGE RETURNS.
  19. You get a distinct "MEH" from me for the look and feel. That was until I found the "jump to new post" button being waaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaay off to the right from the thread title, past the number of views, number of replies author, and post date. Jesus christ, that is the worst location. In terms of functionality, I had to edit the fucking HTML just to make this thread. Take a wild guess where the "this is where your post content goes" text field is. That's right, it's hidden. Good jorb Invision Power Services. Well at least it'll keep people who don't know how to code from posting threads at least...if completely infuriate everyone else. Oh jesus fucking christ. Unhiding the text area makes it 3 lines tall and the entire screen wide and if I resize it larger it covers up the submit button. REVERT. REVERT. ABORT. RETRY. FAIL.
  20. new ItemStack(Items.DIAMOND_CHESTPLATE) You know... You could create this once rather than 30 times...
  21. there should be ||, thanks for spotting this You don't need an || either. Both values will always be identical. There is no need to check both. You only need to check one or the other. True || True / False || False is just as truthy as True / False is.
  22. if(stack.getTagCompound() != null && !(stack.hasTagCompound())){ Seriously? Both of these will only ever be both-True or both-False. If it doesn't have a tag compound, then that compound will be null, and vice versa. That said, here's your problem: if (nbt != null){ nbt.setBoolean("found", false); stack.writeToNBT(nbt); } Why the fuck are you writing the stack (in NBT format) to the item's tag? You've literally tried to write the tag to itself by doing this. No wonder you get an infinite loop.
  23. Post your code. If there's a problem, always post your code. What you have there is an infinite loop. Some part of your code is doing something very naughty with NBT.

Important Information

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

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.