Protector:tool: separate param2 defaults for compatible protector nodes

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
lua
Domain
game-dev

Research direction

Start by tracing how param2 is cloned between badge and block protector nodes, comparing protector:protect with protector:protect2. Clarify the intended defaults and whether cloning should be configurable; done means each compatible node uses the appropriate param2 behavior without breaking orientation preservation.

Written by the indexing model from the issue text.

Description

enhancement question

Protector nodes that are marked compatible with parent protector should have their own default settings for param2 and also ability to disable param2 cloning.

Currently for example protector:protect does not use param2 but protector:protect2 uses it for orientation.
Should param2 be always 0 for former and only cloned for latter.

Currently cloning param2 from badge to block and vice versa allows keeping orentation of badge even if blocks are placed in between. This can be seen as benefit.

Does having useless param2 on block cause any harm?

Dominant language
Lua
Stars
4
Forks
7
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mt-mods/protector

All issues in mt-mods/protector

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.