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

Notes and pens: writing code needs an overhaul before they're added

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
backend

Research direction

Start with do_write in act_comm.cpp at line 387, then trace the listed restyle, object version refresh, extract, and purge paths that can replace object strings while writing is open. Review the skin checks in the editor and boot code as well. Done means the writing input remains valid across those paths and note type changes are handled safely; the issue does not identify tests to run.

Written by the indexing model from the issue text.

Description

No world has pen objects today, so nobody can write on a note. If notes
and pens are ever added, the writing code needs a review first:

  • do_write (act_comm.cpp:387) points the writer's input at the
    note's own text field (desc->str = &paper->action_description).
    Anything that changes or frees that field while someone is writing
    makes the next typed line go into memory that is no longer the
    note's.
  • Object skins refuse notes as a base (editor and boot), but a copy
    whose prototype changed type keeps its own note type, and restyle
    checks only the prototypes.
  • Check every path that replaces an object's strings while it may be
    open for writing: restyle, the object version refresh, extract and
    purge.
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.