Minecraft – Why will minecraft’s NEI search only search mod names

minecraft-java-editionmods

A friend of mine recently made a custom modpack for the technic launcher, but when we use the NEI search function, the only thing that works for searches is the names of modpacks.

For example, searching for "open" shows everything for openblocks, which might be normal, but searching for "iron" shows only items in the iron chest mod, no iron ore, iron bars, iron tools, nothing.
enter image description here

I did see that normal functionality is that @ will search by mod name, but that WAILA might be overriding it. On a whim I tried a few other things and found that if I do #iron, I get what (I think) is a list of all items with iron in the name. Perhaps WAILA or another mod is changing the expected functionality…
Any specific ideas?

Update
It seems that the format @text is a subset search in NEI, i.e. @leg shows a list of all leg slot items. This is different behavior than I'm seeing with no prefix, searching for "leg" gets me no hits.

Update 2

#text does not appear to search for items containing that word, or at least not all items. #comp yielded compressed dirt, but not the opencomputers computers.

Best Answer

its because you have the waila mod and it searches in the mod name too so it will get really confusing but if you do "iron i" it should get an iron ingot but the subsets you used are also possibly affecting it so try using the @(subset tab) instead for certain mods

Related Solutions

Minecraft – Bukkit DefaultCommands Permissions

In my opinion, your best bet here is to use Essentials' GroupManager. It's simple to set up, gives OPs all available commands and lets normal users play with basic permissions. All you have to do is download the Essentials Suite from here, paste the Jar files into your plugins directory and start the server to let it generate the default files.

Then, open plugins/GroupManager/Worlds/World/Groups.yml with your favourite text editor and tweak it a little. By default, new players will be added to the default group, which has no building permissions. If you change build: false to build: true under the info section, they'll be able to place and destroy blocks, and use a very basic set of commands.

groups:
  Default:
    default: true
    permissions:
    - essentials.help
    - essentials.helpop
    - essentials.list
    - essentials.motd
    - essentials.rules
    - essentials.spawn
    inheritance: []
    info:
      prefix: '&e'
      build: false
      suffix: ''

  ...

If you want to give your users some more freedom, change default: false to default: true for the Builder group. You can also remove some commands you don't want them to have while still conserving the other ones, such as essentials.kit and essentials.kit.tools. You can also change the group of the already existing users editing plugins/GroupManager/Worlds/World/Users.yml.

For more advanced Permission management, I'd recommend Permissions 3.x before DefaultCommands.

Edit: Here's a really useful command reference for GroupManager: forums.fragnet.net/minecraft/588-essentials-command-reference.html

Minecraft’s FiniteWater mod: what is counted as “low in mass”

I asked on the mod creators' forum and got the answer of, by default, the limit is 1024. If you open up your Minecraft folder, go to .minecraft\mods\DJoslin, there is a finite_liquid.txt that can be opened (with, say, notepad) and change the OceanToLakeLimit ; 1024 number to something higher, say, 2048. I've tried 4096 which has worked on my laptop without issues and there is no apparent reason why higher numbers wouldn't work.

I do notice a larger area can be pumped out now.

Related Topic