Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Synchronet Synchronet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 222
    • Issues 222
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

This GitLab instance has migrated as of Nov-5-2022 to a new server: hardware, OS, SSH key

The v3.20a development branch has now been merged to the master branch. Sysops upgrading from earlier versions must run 'jsexec update'

  • MainMain
  • SynchronetSynchronet
  • Issues
  • #316
Closed
Open
Issue created Dec 31, 2021 by VIncent Macaluso@nolageek

Changes in text.dat are not reflected when using DDMsgReader

Could DDMsgReader be updated to allow @ msg codes in strings? I'm trying to customize prompts but it's limited since the strings do not allow @ codes like SUB or GRP.

In the same vein, would be nice to pull SBBS default strings like "Subboard, Group, or All" from the text.dat so that changes and substitutions done there (and substitutions made in our login.js file) are also used in the MsgReader and Msg Scans, etc... Reference these text.dat strings in the this.txt block where default values or stored in case they're not configured in the theme's .cfg file.

However as per my first suggestions, right now, changing scanScopePromptText: bbs.text(621) in this this.txt block doesn't expand the @ tags contained within the substition for string #621

Assignee
Assign to
Time tracking