TESTIFICATE (TBS) HORROR

● ● ●

ABOUT

Testificate adds new creepy interactions and visual effects to villagers, making encounters feel more mysterious and unpredictable.

Villagers can receive temporary custom face overlays and nose effects, synchronized to nearby players through a built-in networking system so everyone sees the same visual changes in multiplayer.

The mod also introduces a variety of random villager events that can interact with nearby players in different ways, creating unexpected encounters while exploring your world.

Villagers come with custom nametags but it can be applied to any configured entity, including modded entities, allowing for easy customization. (events and faces are tied to villagers only, and can be toggled.)

Nearly every feature is configurable, letting you choose how the mod behaves.

● ● ●

Q&A

Inspiration for the mod?

>...

I took inspiration from "The Broken Script" with the same concept of villagers spawning with nametags "TESTIFICATE" and are unable to trade. Also from Beta 1.9. with villager's first release. I wanted to add creepiness to the game.

Where can I run this mod?

>...

You can run this mod on both Client and Server side.

Does everyone need the mod installed to join my server?

>...

Yes. Both integrated or dedicated server needs to have mod installed and also every player who joins that server needs to have mod installed.

Can it be used with custom modded entities?

>...

Nametags will work on any modded entity. For trading, there is a good chance it will work if the entity uses a trading system similar to villagers.

Do villagers have weird behaviors?

>...

Yes they do, they can change textures of their faces and noses and they also have events where they interact with player in some ways. There aren't any custom mobs tho, mod flags a villager then gives him a random event. On multiplayer, mod checks minimum 5 random players to see if villagers are around them then chooses 1 villager.

What software was used for the mod's creation?

>...

It was created using Eclipse IDE.

● ● ●

CONFIG V1.2.5

"Configuration Options

>...

There is a JSON config file inside config/ called testificate-mod.json. Here is an example of how it can look:

{


  "entitiesUpdateOnEveryLoad": false,


  "aggresiveMode": true,


  "oldNames": false,


  "jumpscares": true,


  "teleport": true,

  "entities": [


 
 
 
  {


 
 
 
 
  "entity": "minecraft:villager",


 
 
 
 
  "nametag": "TESTIFICATE",


 
 
 
 
  "spawnrate": 0.5,


 
 
 
 
  "tradeable": true


 
 
 
  },


 
 
 
  {


 
 
 
 
  "entity": "minecraft:wolf",


 
 
 
 
  "nametag": "Helper",


 
 
 
 
  "spawnrate": 1.0,


 
 
 
 
  "tradeable": false


 
 
 
  }


  ]


}

"entitiesUpdateOnEveryLoad" controls how mobs will update their nametags. Setting this to true will update mobs on every single load, like unloading/loading chunks and they will always update their nametag even if player changes it.

If option is set to false only newly spawned mobs will be updated, mobs saved to disk will be skipped, and nametag can be changed.

"aggresiveMode" toggles the ability for villagers to change textures (faces and noses) and also toggles the events villagers can do.

"oldNames" allows villagers with previous nametag history to keep events and behaviors. If enabled, old names like "TESTIFICATE" or "ACT" will work the same as the most recent name "SERPENT" (history is located in testificate-names-mod.json). So e.g three villagers with three different names will keep their behaviors (like tradeable capabilities etc...).

"jumpscares" there is an event for testificates, when triggered it will jumpscare player and teleport it 100 blocks away.

"teleport" if teleporting caused by jumpscare event will also trigger.

"entities" holds the list of entities whose properties will be modified. Both natural spawns and spawn egg spawns are affected.

        "entity" holds mob ID, "nametag" displays name above mob (can be empty), "tradeable" toggles their

 
 
 
 
"spawnrate" the probability of mobs spawning with a nametag (ranges between 0.0 and 1.0 - 0% and
 
 
 
 
 
 
100%),
"tradeable" toggles their tradeable capabilities (false if not supported).

● ● ●

CONFIG READ-ONLY V1.2.0

"names", ["mob", "currentNametag", "previousNametag []"]

>...

There is a json file inside config/ called testificate-names-mod.json, used and modified by mod itself. Here is example how it can look like:

{


  "names": [


        {


          "mob": "minecraft:villager",


          "currentNametag": "Sony",


          "previousNametags": [


              "Color",


              "Orange7",


              "TESTIFICATE"


          ]


        }


    ]


}

Every time you change nametag of any entity inside testificate-mod.json, this file will update itself and take the current name you put and place it inside "currentNametag", and put previous name into the list "previousNametags" (duplicates and empty strings will be ignored). This file is used to update outdated villager names inside a world. If you example have a name "TESTIFICATE", and change it to "Cola", and if " entitiesUpdateOnEveryLoad": true, every time you load chunks it will search for outdated names like "TESTIFICATE", (and every name that was changed in the past) and automatically replace those villagers to the most recent name "Cola". This doesn't work only for villagers but any entity, this is just example.

Nothing in this file should be modified by hand, everything is already done by the mod. Only thing that is safe to change is "previousNametags", you can put any names you want inside. If this file becomes too large you can delete it and it will recreate itself.