# How to give feedback on modules/projects and reach the developer

**URL:** <https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184>\
**Category:** Site Feedback\
**Created:** [June 1, 2026, 2:50pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184 "2026-06-01T14:50:25Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 1, 2026, 2:50pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/1 "2026-06-01T14:50:25Z")

</div>

This thread is a copy of another thread ( [Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/9)) so as to not highjack that thread with the discussion on providing feedback on a project and reaching the developer. Following posts are quotes from the original thread.

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 1, 2026, 2:51pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/2 "2026-06-01T14:51:57Z")

</div>

From @JoelCFC25:

> [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/2):
>
> Module-specific questions are best posed directly to the creator, otherwise you have to hope they’re reading these forums. Visit [the module’s project page](https://vassalengine.org/library/projects/Blackbeard) and you can click their username to send a private message.

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 1, 2026, 2:52pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/3 "2026-06-01T14:52:50Z")

</div>

From Joel (@uckelman)

> [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/3):
>
> > [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/2):
> >
> > Module-specific questions are best posed directly to the creator, otherwise you have to hope they’re reading these forums.
> 
> This is something I’d like to change, but I’m not sure how… One could include an `@` for the module’s maintainer in such messages to make it more likely that they’d see them, but that still won’t bring them to the forum.

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 1, 2026, 2:53pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/4 "2026-06-01T14:53:35Z")

</div>

From @JoelCFC25

> [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/5):
>
> My own view is that module creators should always include a minimal help document in their modules that includes contact details so users don’t have to resort to sending out general inquiries without any certainty they’ll be seen by the right person. But that’s obviously not enforceable.

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 1, 2026, 2:54pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/5 "2026-06-01T14:54:34Z")

</div>

From Rob McCray

> [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/6):
>
> I know this is a pretty lofty idea, but I’ve always wished there was a more direct connection to module’s project page where questions about that specific module could be originated from the project page and mirrored in the forum for general viewing. This would appear like the chat window to the right of a youtube live stream, although, functionally, it would remain part of the forum, historically, it would give users a more centralized collection of queries about that module. I also believe it would encourage interaction because it would feel more direct because people would find it easier to provide feedback directly to the project page.
> 
> That said, I get that it is a technical leap to develop such a concept if it’s possible at all.

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 1, 2026, 2:56pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/6 "2026-06-01T14:56:54Z")

</div>

From myself (@cholmcc)

> [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/7):
>
> …
> 
> > [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/2):
> >
> > Module-specific questions are best posed directly to the creator, …
> 
> Click the user name in the project page, and then click the big blue _Message_ button. Remember to specify a meaningful subject line (i.e., it should contain the module name).
> 
> > [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/2):
> >
> > … otherwise you have to hope they’re reading these forums
> 
> For the specific module in question, the author is @LeeSmith who’s been active in the forum lately, so there’s a good chance that the author - in this case - will read a post - but it will help to give a link to the _specific_ module.
> 
> > [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/3):
> >
> > This is something I’d like to change, but …
> > 
> > > [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/6):
> > >
> > > I know this is a pretty lofty idea, but …
> 
> In the meantime, as long as a `@`-mention doesn’t trigger an email notification (as it does on - say - GitHub), and there’s project specfic “forum”, I think the best practise is
> 
> 1. Write a direct message (DM) to the module author(s) by clicking the user name and then the big blue _Message_ button.
> 2. If the project mentions some sort of hosting platform - say GitHub or GitLab - use the _Issue_ interface to submit an issue (bug report).
> 3. If there’s no reply within a reasonable amount of time, post a message in the forum, making sure to
> 
> - Mentioning the project name in the subject - perhaps in square brackets `[...]`
> - Provide a link to the specific project page
> - Post to the _Module discussion_ sub-forum
> 
> The new Game Library actually makes this all a bit easier, as the module author user name is mentioned and linked to that user’s forum profile. In the Wiki-based library, one had to rely on the author having filled in the appropriate email address.  
> …

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 1, 2026, 2:58pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/7 "2026-06-01T14:58:11Z")

</div>

From Rob McCray

> [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/8):
>
> > [@Blackbeard AH module 2.0 questions/criticisms](https://forum.vassalengine.org/t/blackbeard-ah-module-2-0-questions-criticisms/90177/7):
> >
> > In the meantime…
> 
> As I said, lofty. And to be clear, I’m not suggesting the current method is broke. It works pretty well. I just think it would be great someday to have module specific comments on the module pages. It’s admittedly partly vanity, but it would also be of some benefit to have the history of comments on a module all in a single stream in one location on that module’s page but mirrored in the Forum. This is already being accomplished for News that shows up on the main Vassal page but also shows up in the forum timeline. Same concept but definitely complicated by the question of how the user or the software identifies which module is being discussed.
> 
> In my mind’s eye I would envision that if you are originating a message from the Forum, the first action would be to enter or select the module that matches the list of modules in the library search, or if entering the post from the module page, the software automatically assigns module information from the current page.

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 1, 2026, 3:04pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/8 "2026-06-01T15:04:23Z")

</div>

Perhaps the simplest way to implement a way for forum discussion to be closer tied to individual projects, would be to allow forum messages to be tagged with a project. Then, one can query the forum for messages related to specific projects, and the project pages could provide link to such a query.

Of course, that is easier said than done. The Game library runs on custom code, and it is possible to query the database. But, the forum runs on Discourse platform, and it is not straight forwardly easy to see how that platform can query the Game library database - it may be possible, or it may be difficult to implement.

Yours,  
_Christian_

---

<div class="post-metadata">

**Author:** ![clanmacrae](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/c/e8c25b/32.png) [@clanmacrae](https://forum.vassalengine.org/u/clanmacrae)\
**Post date:** [June 1, 2026, 3:37pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/9 "2026-06-01T15:37:00Z")

</div>

Agreed. These are the two categories that would need to require that tag before submitting or at least offer the option to tag. But if at all possible, the requirement is the better option, otherwise you end up with a system that half works, and as with the current method, a great majority of posters start out by not properly identifying which module they are referring to, requiring a moderator to request specificity.

The other consideration of course is whenever you place a pass/fail step into a process, users may give up if they don’t understand what is being asked, or if they can’t properly identify which version of The Russian Campaign they should select.

 ![image](https://forum.vassalengine.org/uploads/default/original/2X/b/b0a5a4c1e822b57fc2b1b68de6a5e5c122d33375.png)

---

<div class="post-metadata">

**Author:** ![marktb1961](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/marktb1961/32/231_2.png) [@marktb1961](https://forum.vassalengine.org/u/marktb1961)\
**Post date:** [June 2, 2026, 11:12am UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/10 "2026-06-02T11:12:19Z")

</div>

a +1 for the idea of linking discussions to their project, whilst acknowledging that implementation would depend on someone else to implement it.

Something like this is done on the [commandsandcolors.net](http://commandsandcolors.net) platform. The platform uses a (with apologies, just my experience) horrible CMS called Joomla but, with dedicated manual admin, as a new [Scenario](https://www.commandsandcolors.net/napoleonics/articles/ccn-related/napoleonics-scenario-statistics-full.html) is added, a new forum topic is created for that scenario.

The latest posts appear on the bottom of the scenario page, along with links to the forum thread itself, as in [this example](https://www.commandsandcolors.net/napoleonics/maps/peninsular-war-1808-1814/001-rolica1-17-august-1808.html).

The Forum Structure itself comprises a dedicated forum for scenarios with a thread per scenario, so the easiest way into a discussion is via the scenario page itself. I imagine a similar approach being feasible as a bridge between the custom project pages and Discourse discussion categories - if it is possible to implement sub-categories…

Discourse sub-categories on “Module Discussions” - sub-category per Project, or better still, one sub-category per Project. This would be a lot of categories but my expectation would be that users would access the category via a link on the project page, as in the example above.

I’m assuming that it would be possible to automatically populate Project pages with a link to the forum category/sub-category using the project name as the sub-category.

This wouldn’t accomplish being able to see the forum posts directly on the project page - great if that could be done - but at least with the link in place it would be easy to access and users would be directed to the forum. One advantage over the C&C .net example is that the project discussion would still have it’s own thread structure rather than everything being held in a single post.

---

<div class="post-metadata">

**Author:** ![clanmacrae](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/c/e8c25b/32.png) [@clanmacrae](https://forum.vassalengine.org/u/clanmacrae)\
**Post date:** [June 2, 2026, 2:40pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/11 "2026-06-02T14:40:07Z")

</div>

> [@marktb1961](#):
>
> a +1 for the idea of linking discussions to their project, whilst acknowledging that implementation would depend on someone else to implement it.

Yeah, that’s kind of where I am, unfitunately.

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 2, 2026, 3:14pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/12 "2026-06-02T15:14:00Z")

</div>

> [@marktb1961](#):
>
> would depend on someone else to implement it.

One option would be to use the [Mentionables plugin](https://meta.discourse.org/t/mentionables/192948).

When a user types, when composing a post, `+Af`, then the user will be presented with a drop-down with all project names that match `Af` - e.g., `Afrika Korps`.

This requires an external Google Sheet document. That Google Sheet should map mentionables to urls. That Google Sheet can be created from the Game Library database and then made available to the above plugin. Of course, the Google Sheet needs to be updated when a new _project_ is made (or removed), which doesn’t happen _that_ often.

It is not clear that one can do a reverse search - i.e., search for forum posts that mentiones a specific _mentionable_ which would. be needed to link back from the project page to the forum post.

Another option is to use the [Discourse Tag Rest API](https://docs.discourse.org/#tag/Tags) to push new tags to Discourse when a new project is created or removed. I’m not sure how one would limit certain tags to certain tag categories though. The project pages can do a reverse [search](https://docs.discourse.org/#tag/Search/operation/search) based on the tag of the project.

Yours,  
_Christian_

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 2, 2026, 3:19pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/13 "2026-06-02T15:19:03Z")

</div>

Perhaps the project pages doesn’t really need to contain the posts directly, but rather provide a link to a search query based on the projects tag value. Otherwise, it could be a simple embedded frame that contains the result of the query on the projects tag. In that way, no Discourse code have to be integrated into the Game Library.

Yours,  
_Christian_

---

<div class="post-metadata">

**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\
**Post date:** [June 2, 2026, 5:24pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/14 "2026-06-02T17:24:58Z")

</div>

If there were one tag per project, that would mean 3500+ tags right now. How do users interact with tags? Is the system for selecting tags in Discourse able to handle this number of tags?

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 2, 2026, 9:39pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/15 "2026-06-02T21:39:43Z")

</div>

> [@uckelman](#):
>
> If there were one tag per project, that would mean 3500+ tags right now.

Right - a butt-load of tags. That’s why they should preferably be restricted to specific categories / such as #Module Discussion and #Module Support .

> [@uckelman](#):
>
> How do users interact with tags?

Tags can be specified when starting a new thread, using the drop-down in the toolbar of the post editor. But tags can also be made in-post by typing `#`, and then auto-completing on known tags - for example #tutorial .

Ideally, if a user starts a new thread in either #Module Support or #Module Discussion , then the user would select the appropriate project tag too. Then that thread will be tagged with the project, and can therefore be shown or linked to from the project page itself.

Of course, a user could also add a project tag later on - even in later replies - which could be beneficial when referring to a specific project for inspiration, comparison, etc.

> [@uckelman](#):
>
> Is the system for selecting tags in Discourse able to handle this number of tags?

No idea. Off-hand, I don’t see why it shouldn’t. But, I’m no expert on Discourse, so better consult with someone who knows or read the documentation.

Another option, would be to put a link on every project page - say _Give feedback_, _Request Support_, _Start discussion_, or something like that, which takes the user to the forum with a new thread editor with the subject line pre-filled with the project name and possibly a project tag.

Then, perhaps, one can close direct posting to #Module Discussion and #Module Support so that users are forced to go through the project page to post to those categories.

Note that tags does not allow for associating a URL with the tag, as far as I can see. The above mentioned [Mentionables plugin](https://meta.discourse.org/t/mentionables/192948) _does_ allow that.

On the other hand, using Mentionables requires that the user enters `+`, followed by a selection in the drop-down menu, somewhere in the body of the post. And, as I said above, it is not clear if one can query the API for posts that have a specific Mentionable.

Yours,  
_Christian_

---

<div class="post-metadata">

**Author:** ![marktb1961](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/marktb1961/32/231_2.png) [@marktb1961](https://forum.vassalengine.org/u/marktb1961)\
**Post date:** [June 2, 2026, 10:26pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/16 "2026-06-02T22:26:46Z")

</div>

I think what is needed is sub-categories, rather than tags. From my brief research e.g. [here](https://meta.discourse.org/c/documentation/contributing/168), it appears that using sub-categories would avoid cluttering up the general Discourse forum front-end.

I suggested earlier that a link from the Project page would be the standard entry point to a Module Discussion Sub-Category, though perhaps Discourse offers a sensible way to navigate a large number of sub-categories.

There’s the question of whether it’s really helpful to have forum categories for orphan projects (I assume, the vast majority). I think that the idea would be no worse than the current situation but with the benefit of a forum structure providing an unambiguous link to the project.

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 3, 2026, 9:30pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/17 "2026-06-03T21:30:27Z")

</div>

First off, I’m not advocating any particular solution. My main concern is to find a solution that is simple to implement and requires the least maintenance from our ~~dear~~ busy leader 😄, and at the same time provides as much as possible of the wanted functionality.

> [@marktb1961](#):
>
> I think what is needed is sub-categories, rather than tags.

Tags has the the advantage over sub-categories that more than one tag can be applied to a thread for example if a question/comment/complaint/… is relevant to more than one project.

> [@marktb1961](#):
>
> From my brief research e.g. [here](https://meta.discourse.org/c/documentation/contributing/168)

Not quite sure which post on this forum you are referring to or if you want to illustrate the use of sub-categories. In the latter case, I think [this](https://meta.discourse.org/c/documentation/10) would be more illustrative, but also high lights another issue with sub-categories: The interface would be relatively cluttered by the shear number of sub-categories (even if orphaned projects are filtered out).

Sub-categories has the benefit that the distinction is quite clear, and that project owners could “subscribe” (i.e., get email notifcations) to specific sub-categories. They probably need very little in terms of set-up, though sub-categories would need to be added and removed as projects are added and removed from the Game Library.

However, there’s something to be said for the messages on specific projects show up in a general sub-forum. Often, third-party users will comment and give advice _even if_ the project owners are replying too.

> [@marktb1961](#):
>
> There’s the question of whether it’s really helpful to have forum categories for orphan projects (I assume, the vast majority).

If the interface for starting a thread on a particular project originates on the project page (_Give feedback_, _Ask question_, _Start thread_, or similar), then that interface could also create the needed tag, mention, or sub-category. In that way, only those projects are are discussed will have an associated tag, mentionable, or sub-category.

> [@marktb1961](#):
>
> … but with the benefit of a forum structure providing an unambiguous link to the project.

For that, I think the above mentioned _Mentitonables_ are perhaps the best option. One could implement in Discourse a [custom field](https://meta.discourse.org/t/creating-and-configuring-custom-user-fields/113192?tl=en) presented in the thread interface, what would allow a poster to select the project(s) (Mentionables) that the thread is related to.

Yours,  
_Christian_

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 4, 2026, 6:23am UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/18 "2026-06-04T06:23:42Z")

</div>

While we figure out how to address this issue, I found a way to do some of what we talked about - namely, providing links from the project page to forum posts and a way to make a new thread with pre-filled in information.

As an example, see [Anzio Beachhead](https://vassalengine.org/library/projects/anzio_beachhead_cholmcc) - scroll down to the heading **Forum Posts**.

There are two sets of links

- One to the category #Module Support
- One to the category #Module Discussion

For each, there two links

- One that searches that particular category for `anzio+beachhead` or `anzio_beachhead_cholmcc`
- One that starts a new thread in that category with the title pre-filled with `https://vassalengine.org/library/projects/anzio_beachhead_cholmcc`

These links fulfils two tasks - albeit in a poor-mans way 😄

1. Provides a way for users to discover topics that relates to a specific project
2. Provides a way for users to post a new topic specifically tied to a project.

As I said, perhaps not the best solution, but at least it gets us part of the way.

The links could be automatically put in by the Svelte templates in the module library. The templates would use the project slug and title to search for posts, and the project URL for the new thread links.

Yours,  
_Christian_

---

<div class="post-metadata">

**Author:** ![clanmacrae](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/c/e8c25b/32.png) [@clanmacrae](https://forum.vassalengine.org/u/clanmacrae)\
**Post date:** [June 4, 2026, 2:42pm UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/19 "2026-06-04T14:42:48Z")

</div>

This looks like a good start. Counting the number of times you have responded to posts with the interview questions “Which project/module are you referring to” and "have you tried contacting the project owner’ is indicative of why a system solution for these two questions should be resolved with every user post for a specific module.

Is it possible for the project owner(s) to be automatically tagged in the post as well?

---

<div class="post-metadata">

**Author:** ![cholmcc](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/cholmcc/32/8319_2.png) [@cholmcc](https://forum.vassalengine.org/u/cholmcc)\
**Post date:** [June 8, 2026, 10:35am UTC](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184/20 "2026-06-08T10:35:53Z")

</div>

> [@cholmcc](#):
>
> The links could be automatically put in by the Svelte templates in the module library. The templates would use the project slug and title to search for posts, and the project URL for the new thread links

@uckelman if you could point me to some way of running a test build/setup of the [Game Library](https://github.com/vassalengine/game-library), I will happily make one or more PRs against it. I think there should be buttons in the **Project** section of a project page. The kind of buttons would be

- Post new topic to #Module Discussion and #Module Support
- Search #Module Discussion and #Module Support
- Direct message to project owners (see [here](https://meta.discourse.org/t/creating-pre-filled-personal-message-links/35984))

Yours,  
_Christian_

[Next page](https://forum.vassalengine.org/t/how-to-give-feedback-on-modules-projects-and-reach-the-developer/90184.md?page=2)
