HitscanBows
Look at how much fun they're having! (Laser beams are optional, can be turned off)
Plugin description
Finally, a true hitscan bow plugin! Unlike other plugins out there, HitscanBow does not just set your arrow's speed to some arbitrary number. Instead it uses mechanics similar to those in popular FPS games to check if a target is hit. This lightweight plugin can be implemented in minigames, used to enhance the survival experience or even simply as a unique feature to make your server stand out. Works with Bukkit and Paper Minecraft servers.
Features
- Highly customizable
- Works with arrow variants
- Optional permissions system
- Optional particle effects
- Optional: Custom arrows
Commands
/hitscanreload - Reloads the plugin's configuration
/hitscanitem - Spawn a new bow and crossbow that uses hitscan mechanics, only if item checks are enabled in the config (Read bow.yml for more information)
Permissions
hitscan.use - Lets a player use the plugin. Doesn't do anything by default unless permission is enabled in the settings
hitscan.admin - Grants access to all the commands
Configuration
The configuration is split into settings.yml, messages.yml and bow.yml and crossbow.yml for each weapon respectively.
settings.yml
Code (YAML):
# What a line in messages.yml will start with if you don't want to use messageformat
# For example "Plugin > some message" is the default message
# You can change it to "some message" if you replace the default with the following in messages.yml
# example: "--some message"
negateformat : "--"
# Sets if only bows with specified characteristics (defined in bow.yml and crossbow.yml) are affected
# The way it works is by checking the name and lore of the item that shot the arrow
# You can remove either checks by changing the respective field in the aforementioned yml files.
item : false
# The range of hitscan, in blocks
range : 100
# Sets if mob and player arrows are affected
mob : true
player : true
# Sets if players require permission "hitscan.use" to access hitscan mechanics
permission : false
# Sets if bows and crossbows will be affected
crossbow : true
bow : true
# Sets if the 'ding' sound is heard upon hitting a target
sound : true
# Sets if lasers, sparks and blood are enabled. Ignore the respective settings below for each disabled feature
laser : true
sparks : true
blood : false
# The number of blocks downwards from shooter's eye level to the start of laser beam
laseryoffset : 0.4
# The number of blocks forwards from shooter to the start of laser beam
laservectoroffset : 0.65
# Size and density of lasers
lasersize : 0.4
laserdensity : 5
# How packed the laser will look, the bigger the number, the more spaced out
lasercloseness : 0.05
# The number of extra blocks a laser will travel after reaching the edge of an entity's hitbox
# Settings this too low will result in the laser not reaching the target; too high will make it go through the target
laserpenetration : 0.5
# The number of blocks from the edge of an entity's hitbox towards the entity where blood will spawn
bloodoffset : 0.1
# The density of sparks created when a block is hit
sparkcount : 10
# Whether sparks will be created when an entity is hit
sparksentity : false
# For example "Plugin > some message" is the default message
# You can change it to "some message" if you replace the default with the following in messages.yml
# example: "--some message"
negateformat : "--"
# Sets if only bows with specified characteristics (defined in bow.yml and crossbow.yml) are affected
# The way it works is by checking the name and lore of the item that shot the arrow
# You can remove either checks by changing the respective field in the aforementioned yml files.
item : false
# The range of hitscan, in blocks
range : 100
# Sets if mob and player arrows are affected
mob : true
player : true
# Sets if players require permission "hitscan.use" to access hitscan mechanics
permission : false
# Sets if bows and crossbows will be affected
crossbow : true
bow : true
# Sets if the 'ding' sound is heard upon hitting a target
sound : true
# Sets if lasers, sparks and blood are enabled. Ignore the respective settings below for each disabled feature
laser : true
sparks : true
blood : false
# The number of blocks downwards from shooter's eye level to the start of laser beam
laseryoffset : 0.4
# The number of blocks forwards from shooter to the start of laser beam
laservectoroffset : 0.65
# Size and density of lasers
lasersize : 0.4
laserdensity : 5
# How packed the laser will look, the bigger the number, the more spaced out
lasercloseness : 0.05
# The number of extra blocks a laser will travel after reaching the edge of an entity's hitbox
# Settings this too low will result in the laser not reaching the target; too high will make it go through the target
laserpenetration : 0.5
# The number of blocks from the edge of an entity's hitbox towards the entity where blood will spawn
bloodoffset : 0.1
# The density of sparks created when a block is hit
sparkcount : 10
# Whether sparks will be created when an entity is hit
sparksentity : false
Code (YAML):
# The format that all messages will follow unless negated with prefix stated in settings.yml
messageformat : "&eHitscanBows &8> &f{message}"
nopermissions : "You can't use that command!"
usage : "Usage: {usage}"
messageformat : "&eHitscanBows &8> &f{message}"
nopermissions : "You can't use that command!"
usage : "Usage: {usage}"
Code (YAML):
# This file decides what a hitscan bow will look like
# If item is set to false in settings.yml, ignore this file
# Use /hitscanitem in game to spawn an example of the item defined here (Make sure to reload the plugin first if you made changes!)
# Whether bows are hitscan
# Set to false to disable
enabled : true
# Name of an bow with hitscan mechanics
# Do disable name checks, uncomment the line below and delete the original line
#name: "-"
name : "&6Hitscan Bow"
# Lore content of an bow with hitscan mechanics
# You can set 1 or more lines
# Set to the following to disable lore checks
#lore:
# - null
lore :
- "&bThey can hide but"
- "&bthey cannot run"
# Still confused? Ask the developer any question here: https://www.spigotmc.org/threads/hitscanbows.562714/
# If item is set to false in settings.yml, ignore this file
# Use /hitscanitem in game to spawn an example of the item defined here (Make sure to reload the plugin first if you made changes!)
# Whether bows are hitscan
# Set to false to disable
enabled : true
# Name of an bow with hitscan mechanics
# Do disable name checks, uncomment the line below and delete the original line
#name: "-"
name : "&6Hitscan Bow"
# Lore content of an bow with hitscan mechanics
# You can set 1 or more lines
# Set to the following to disable lore checks
#lore:
# - null
lore :
- "&bThey can hide but"
- "&bthey cannot run"
# Still confused? Ask the developer any question here: https://www.spigotmc.org/threads/hitscanbows.562714/
If you found a bug or have a suggestion, add a comment
Satisfied? Leave a review!
Looking for tracking arrows instead? Check this out!
Resource Information
Author:
----------
Total Downloads:
489
First Release:
Jul 1, 2022
Last Update:
Jul 5, 2022
Category:
---------------
All-Time Rating:
2 ratings
Version
-----
Released:
--------------------
Downloads:
------
Version Rating:
----------------------
-- ratings