[PR #2798] [CLOSED] fix(core_messages.sh): use the proper variable to identify script source for logged events #3788

New issue

Closed

opened 2026-02-27 03:55:49 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 03:55:49 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/GameServerManagers/LinuxGSM/pull/2798
Author: @codingWithJimmy
Created: 4/2/2020
Status: ❌ Closed

Base: develop ← Head: develop

📝 Commits (3)

876288e Update core_messages.sh
3147c6c Revert "Update core_messages.sh"
4e1911d Revert "Revert "Update core_messages.sh""

📊 Changes

1 file changed (+6 additions, -6 deletions)

View changed files

📝 lgsm/functions/core_messages.sh (+6 -6)

📄 Description

Update to allow script action name to appear in log correctly.

Description

After digging into this issue, I found that "core_messages.sh" was using the incorrect variable for identifying which script was producing output in the script log.

Fixes #2797

Type of change

Small code update to correct the variable in core_messages.sh

Checklist

PR will not be merged until all steps are complete.

This pull request links to an issue.
This pull request uses the develop branch as its base.
This pull request Subject follows the Conventional Commits standard.
This code follows the style guidelines of this project.
I have performed a self-review of my own code.
I have checked that this code is commented where required.
I have provided a detailed enough description of this PR.
I have checked If documentation needs updating.

Documentation

If documentation does need updating either update it by creating a PR (preferred) or request a documentation update.

User docs: https://github.com/GameServerManagers/LinuxGSM-Docs
Dev docs: https://github.com/GameServerManagers/LinuxGSM-Dev-Docs

Thank you for your Pull Request!

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/GameServerManagers/LinuxGSM/pull/2798 **Author:** [@codingWithJimmy](https://github.com/codingWithJimmy) **Created:** 4/2/2020 **Status:** ❌ Closed **Base:** `develop` ← **Head:** `develop` --- ### 📝 Commits (3) - [`876288e`](https://github.com/GameServerManagers/LinuxGSM/commit/876288e9f915915e37efefb220bcf3ec766e245e) Update core_messages.sh - [`3147c6c`](https://github.com/GameServerManagers/LinuxGSM/commit/3147c6c21eb4fc2d3b662c9d9a60f5106fcbcce0) Revert "Update core_messages.sh" - [`4e1911d`](https://github.com/GameServerManagers/LinuxGSM/commit/4e1911d9606b7878f78e88cd397cf2ba51ae7d7a) Revert "Revert "Update core_messages.sh"" ### 📊 Changes **1 file changed** (+6 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `lgsm/functions/core_messages.sh` (+6 -6) </details> ### 📄 Description Update to allow script action name to appear in log correctly. # Description After digging into [this issue](https://github.com/GameServerManagers/LinuxGSM/issues/2797), I found that "core_messages.sh" was using the incorrect variable for identifying which script was producing output in the script log. Fixes #2797 ## Type of change * Small code update to correct the variable in core_messages.sh ## Checklist PR will not be merged until all steps are complete. * [x] This pull request links to an issue. * [x] This pull request uses the `develop` branch as its base. * [x] This pull request Subject follows the Conventional Commits standard. * [x] This code follows the style guidelines of this project. * [x] I have performed a self-review of my own code. * [x] I have checked that this code is commented where required. * [x] I have provided a detailed enough description of this PR. * [x] I have checked If documentation needs updating. ## Documentation If documentation does need updating either update it by creating a PR (preferred) or request a documentation update. * User docs: https://github.com/GameServerManagers/LinuxGSM-Docs * Dev docs: https://github.com/GameServerManagers/LinuxGSM-Dev-Docs **Thank you for your Pull Request!** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>