lakeys / blockland-render

A survival horror mod for Blockland that introduces Render, a mysterious entity that haunts the game.

blockland-render's Issues

Render appears to mark frozen targets as 'missing'

Detector flickers when there are multiple attackers

Note: Still present, this was not corrected in 0bc8c4b

Upon being frozen, players can get stuck behind/inside vehicles if dismounted

'Group spawning' needs to be implemented

Group spawning is a planned mechanic where, in spawning, groups of players in the same area will be treated as a single player. This means that a group of players in close proximity will have the same spawn chance as a lone player.

This is important because the spawn chance becomes unbalanced with multiple players, forcing hosts to raise/lower the spawnrate based on player count.

"Observer" bots' disappear time should be based on distance

The intended functionality of this feature is for the bots to disappear quicker the closer they are.

AI Spawning: Branches should be prioritized by distance for balance

Currently, AI attackers are more likely to spawn close to obstructions. This is a result of branches being picked at random; when the majority of obstructions (particularly walls) are close to the player, the majority of spawns will be as well.

The proposed solution is to scale the chance for each branch by its distance to the player, '

EDIT: Fixed, see 55fa06b

Render can freeze targets that cannot look (even through walls)

Render plays the mount sound when freezing a player

Solution found: The vehicle/bot mount sound can be removed by packaging Armor::onMount

function Armor::onMount(%this,%player,%obj,%a,%b,%c,%d,%e,%f)
{
	if(%obj.dataBlock.getId() == RenderDeathArmor.getId())
		return;

	parent::onMount(%this,%player,%obj,%a,%b,%c,%d,%e,%f);
}

Fixed in commit af80863 in branch "v"

Daycycle check doesn't work in simple environment mode

Glitch gun is not removed from player's hand

Possibly related to an add-on

Render de-spawns rather than attempting to pursue targets that are out of view

Add a pref to toggle ambient sounds

AI/Debug: Upon killing a test bot, the AI waits for them to fully de-spawn before proceeding to another target.

Low priority because this only applies to testing bots spawned via Support_Render_Debug

AI: Cannot locate players that are in a vehicle.

When players are in a vehicle, the AI is not able to select them as a target.

Glitch detector datablock causes a console error when the add-on loads

"ShapeBaseImageData:: Could not resolve state "Ready" for image "GlitchDetectorImage""

AI (Observer): If a player aside from the target looks, target them instead

Observers are meant to always stare back at players when possible. This effect is not accomplished properly when an observer is looking elsewhere.

Frozen players float unusually and "bounce" in water

The add-on uses a "death mount" to freeze players. This mount appears to "bounce" on water, with the potential to launch players upward.

The intended effect is for players to float as normal.

See also: #66

Add event for the 'attack mode' pref

When Render takes damage (from weapons), there should be some form of visual indication

This makes it clear to the user that shooting Render actually does something

Death icon in chat should be changed so users can tell when Render is killing players

Add a preference for $Pref::Server::RenderMinSpawnDistance

EDIT: Decided against this for now.

Fix whiteout damage resetting to 0 if player doesn't die

This prevents a 'strobing' effect if the player cannot be killed.

Bots should automatically clear when spawnrate is set to 'disabled'

EDIT: Decided against this change for now

In singleplayer/LAN, Render bots are affected by weapons

Pref to disable lights needs to be implemented

Implement mini-game events for configuration

Planned feature: Mini-game hosts can use events to change the prefs of their own mini-game.

Ensure that 'killing a bot' points do not apply to Render (for both vanilla and Slayer minigames)

Complete; Render kills do not count as bot kills or player kills.

Render can freeze multiple players at once

Results in players getting stuck

Shrines don't un-register when wanded

Shrines do not take effect immediately after being placed

When in a shrine's range, Render should be unable to attack instead of disappearing (Requires AI changes)

AI would need adjustments to act accordingly around shrines. Optimally, AI attackers should back out of shrine ranges to continue attacking

Slayer: Add 'points for killing Render' pref

Passive attackers affect the detector

Observer bots can be viewed in third person

Should be able to fix this by increasing the view check FOV

AI (Movement): Render circles around its destination instead of moving elsewhere or stopping

Users should be notified if placing a shrine while shrines are disabled

It may be best to always tell the user what the current shrine range is set to

Detector gets stuck at a state above 0

Render attempts to spawn in range of shrines

AttackC should play on the player instead of client-side

Existing bots do not change datablock if tag mode is toggled

Glitch gun appears in the wrong position in first person

AI Movement: Detect when a player goes through a teleporter

Add explanation for glitch shrines

Add an evented message to all shrines that are placed. This will help users understand how it works.

Players can get stuck frozen if the attacker freezes them and de-spawns around the same time

Implement passive mode

Detectors are not implemented yet

Render spawns lights at 0, 0, 0; map turns dark (or bright with shaders off)

EDIT: Related to the following error: Render_Spawn_GetNewDirection - Returning blank
EDIT2: Issue still occurs after attempted fix; this appears to have multiple causes

Add a pref to allow attackers to be killed

This would add a defense factor to gameplay.

Maybe include adjustable health

Bots/lights cause the map to turn dark in some cases

All bricks turn completely dark until said bot de-spawns. When shaders are turned off, the map is pure white.
Also possibly related, some users report the sky turning blue.

Loaded shrines count toward the host's brickgroup instead of the actual brick owner

Replication:

1. Obtain a save with shrines placed by several other users
2. Replace temp.bls (base/server/temp) with this save
3. Launch a dedicated server, join, and type /reloadBricks
4. Place shrines until reaching the limit.
5. Count the number of shrines that you are allowed to place.
   Note that the total shrines you placed is equal to 32 minus the count of other users' shrines.