Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

group all silently adds invisible followers, including imms

Open Beginner friendly
#485 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp
Domain
backend

Research direction

Start with the all branch of do_group in src/act_othe.cpp and compare its follower checks with the name-based lookup using get_char_room_vis. Check the room and visibility conditions described in the issue, then verify that group all only adds eligible followers and that the leader gets an appropriate message.

Written by the indexing model from the issue text.

Description

What happens

A mortal types group all while an invisible immortal is following them. The immortal is added to the mortal's group, and the mortal gets no message about it. The only sign is the immortal showing up in the MSDP group data.

Steps

  1. An immortal goes invisible (invis 100) and follows a mortal.
  2. The mortal types group all.
  3. The mortal sees nothing, but the immortal is now in the group (MSDP group data lists them).

Cause

The all branch of do_group (src/act_othe.cpp) adds every ungrouped follower who isn't on the other side. It never checks whether the leader can see the follower.

Grouping by name doesn't have this problem, because it finds the target with get_char_room_vis. So an invisible immortal can't be grouped by name, but group all adds them anyway.

It's silent because add_character_to_group sends "joins your group" with act()'s hide-invisible flag, and the leader can't see the immortal.

The same loop also has no same-room check, so group all adds followers who are in other rooms too.

History

The loop is the same in the oldest commit that has this file (ae69a1f8, 2018-03-23). PR #188 (2023) reformatted it without changing what it does.

Dominant language
C++
Stars
3
Forks
4
Avg merge
18h 36m
Merged PRs (30d)
87

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 returnoftheshadow/RotS_Live

All issues in returnoftheshadow/RotS_Live

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.