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.

Featured Replies

Posted

This is not a rant about JSON.

 

--

 

In an effort to ease myself into 1.14, I've taken up the task of updating a 1.10 decorative mod with a largish (2000+) number of blocks.  I'm about to create the loot tables for them, which, it appears, means an additional .json file each.

 

This is fine -- automating their creation will take upwards of a few minutes.  BUT -- is there a Better Way?  This is a task that, at first glance, seems to be better done in code.  But I also acknowledge the move toward data packs, which the code solution precludes.  So, if creating all those .json is the Right and Good Way, then super!  I'll do so and get on with my day.  If not, well, that's good to know too.

 

Second.  I would like to organize these myriad of files into sub-directories because, well, because it feels better to have them organized.  I can do so by including a \path at the start of the registry name.  "foo\mynewblock" will happily let me use \models\block\foo\mynewblock.json, etc.

 

Which is what I want, but it feels weird.  Recipes, /give, and whatever else that needs the block name now have to deal with the 'foo\' prefix, which I've never seen done before.  As such, I'm interested in opinions and/or alternate solutions here.  Keep the prefix and have the files organized, or just dump them into a single directory and move on?  Or other?

 

As always, thanks for your thoughts.

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...

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.