Mikulib configuration tutorial Mikulib minecraft game

This MOD uses SQLITE storage configuration files, and the modification configuration is hundreds of more cumbersome.

The configuration file is the miku.db file in the .minecraft directory. You can use tools such as DB4S to view and edit.

Data table

As of version 1.6.10, there are 7 tables in the database.

The Config table contains conventional configuration. The MODID in the Hidden_mods table is not detected by Loader.ISMODLOADED () in the Hidden_mods table. D_Class table contains disabledClass, the banned_guis table is in the R.I.P. state, and it may cause collapse at will.

Config table

The record in the Config table contains the primary key (Text) named Name and the value named Value.Name is the configuration name.It currently includes the following configuration options:

Whether the debug_mode is a debug mode, the value value should be true or false.

Auto_range_kill value is true or false, and the developer items will automatically remove the entity after the developer items are set to True.

FIRST_RUN will think that the database is generated as long as there is this record.Do not reset the database by deleting this record.Remove in version 1.6.10.

Example:

 update config set value = 'true' where name = 'debug' 

Hidden_mods table

The records in the Hidden_mods table include only the primary key named ID.At the beginning of the pre -initialization event of FORGE, the Modid that existed in this table will be removed from the NamedMods in the Loader class.

Example:

 Insert Into Hidden_mods (ID) Values ​​('Project') 

Delete this record:

 delete from hidden_mods where id = 'project' 

Banned_mobs table

Records include only the primary key named ID.The entity cannot be generated when the entity's .getClass () values ​​were contained in the table.For example, if the pig is prohibited, the following statements can be performed:

 Insert Into Banned_mobs (ID) values ​​('class network.minecraft.entity.entitypig')--1.6.9 version

Insert Into Banned_mobs (ID) Values ​​('Net.mineCraft.entity.passive.entityPig')--1.6.10

To be allowed to generate pigs, the following statements are executed:

 delete from banned_mobs where ID = 'class network.minecraft.entity.passive.entitypig' --1.6.9 version delete from ban NED_MOBS WHERE ID = 'NET.MINECRAFT.Entity.Passive.Entitypig '--1.6.10 and subsequent versions 

Banned_items table

Disable items.Add to 1.6.10.

Example:

 Insert Into Banned_items (ID) values ​​('net.minecraft.itemfireball')-disabled

Delete from banned_items where id = 'net.minecraft.item.itemfireball'-lifting item

Banned_mods table

The function is similar to the happy bat.Add to 1.6.10.

 Insert Into Banned_mods (ID) Values ​​('Torcherino')-

Delete from banned_mods where id = 'Torcherino'-

Banned_class table

Store disabled classes.The disabled class is forced to exit when it is loaded.Add to 1.6.10.

 Insert Into Banned_Class (ID) Values ​​('COM.SCI.TORCHERINO.TORCHERINO')-

Delete from banned_class where id = 'com.sci.TORCHERINO.TORCHERINO'-lifted

Reference information

SQLite syntax, SQLite Insert statement, SQLite Update statement, SQLite Delete statement