troymccann you mean on the discussion page, not in the discussion composer ?
It should be doable because the code is already inserting into the post body anyway https://github.com/FriendsOfFlarum/mason/blob/master/js/src/forum/addFieldsOnDiscussionPost.js
But I think you might also be able to achieve it with some custom CSS.
Not sure if it's worth an addition to the extension. But you can of course fork and make your changes.
How can we specialize a mason field for a special tag?
For example;
When user opened a post in Gaming tag, mason will ask him/her for "In-game Username". However, in other tags there is no field will show as "In-game Username"
Chenzy there's no such feature at this time.
There was some talk to crowd-fund its development but I didn't have much time to look into it the last few months.
It would be very nice to create god tier community @clarkwinkelmann
If you want to improve it one day. Please let me know about it. 
I am trying to integrate an application system with my forum. The custom fields show on every category and not just a specific one, the applications tag that is. Can you please add an option in the settings of the fields to only allow certain fields to show up on a specific tag. I hope you understand what I mean by this.
Edit: Just saw the other posts above this, this is another reason the limit to a specific tag feature needs to be added.
Now that the extension(mason) has become incompatible and faces certain responsive issues (as discussed in this PR), here's a workaround through which I overcome those.
Issue: I needed two custom(mandatory) fields along with every discussion threads. After installing this extension, I inserted those two required fields from Admin Dashboard. The problem was the alignment and responsiveness of 'Composer Box'(box used to start the discussion) on both desktop and mobile view. It misaligned those custom fields along with everything that comes after title. Mainly:
Solution: Since the available PR was made 2+ years back, it was around 20 commits behind the current master branch. So the only way-out was to mess with core css and js. Here's what I did:
For adjusting the composer height on desktop, I inserted this JS in 'Custom Header' on Admin> Appearance page:
<script>if (!localStorage.getItem("composerHeight")) { localStorage.setItem("composerHeight", 317);
}</script>Here, I fixed the height at 317 pixels because I need only 2 fields that are aligned in parallel. (you may change it accordinly)
Note: I'm targeting a crowd with less users on tablets. So if you want tablet compatibility, you may have to add some additional JS for adjusting the height in case of tablet users.
Also, don't forget to clear your localstorage memory in browser before testing the change.
For adjusting the alignment issues in mobile view, I tried changing some core CSS. We need to edit a minified css file located @ yourdomain.com/assets/forum-somerandomnumber.css. Go to 13th line and search for :
.Composer:not(.minimized). Now in its declaration box, change height:350px !important; to height:auto !important;. This solves the issue by displaying every elements of composer without considering other stylings.
Hope this will help you to have a temporary workaround on these existing responsive issues. I don't endorse this method and so do it on your own risk. Let's wait for an update from someone, in which all these are properly addressed.
FriendsOfFlarum is this available for bita 12 version?
Hi everybody, I wrote an update to this powerful extension with a feature a lot of people have asked for –
UntrustableRus specific tag ... > Chenzy Gaming tag...
pyxxl I just wish that this extension had the option to limit fields to specific tags.
– the ability to turn fields on/off for specific Tags. It's still very much beta but it works well on my dev installs. Before I do the final polish, though, if anyone needs this feature right away they can grab a copy of my version at Github.
@clarkwinkelmann I forked and renamed it Mason Plus for dev purposes so I could run both versions, but let me know if you want me to submit it as a PR to the original.
At the very least being able to tweak an existing extension has taught me a lot about how Flarum works inside and out. Also, as someone who's asked a lot of questions around here, it's nice to be able to contribute something back to the community. Here's a quick video explaining the new features:
raafirivero Great work! This is exactly what I am looking for. But since I'm new to Flarum, how can I try using this? Thank you.
bgkurt hmm, you should be able to download it via github and install it in your /packages folder right away without Composer. I have to figure out how to make it an official extension so that you can install more easily with Composer. Give me a day or two to release it that way.
raafirivero I have to figure out how to make it an official extension so that you can install more easily with Composer. Give me a day or two to release it that way.
Updates on this?
raafirivero you should publish the package on packagist
The little issues have been fixed and the package has finally been migrated over to FriendsOfFlarum.
This extension replaces Flagrow Mason.
Please backup your data before attempting the update!
You can upgrade from any of the older versions of the Flagrow extension.
Then upgrade from the old extension to the new one:
composer remove flagrow/mason
composer require fof/masonWhen you enable the new extension, the permissions, settings and the data from Flagrow Mason will be moved to FoF Mason.
raafirivero yes, PRs welcome! You will probably need to rebase your code on the new FriendsOfFlarum version though.
All the layout-related PRs and issues are still on hold until proper reviews can be conducted.
is it possible to only allow custom fields on discussions of a certain tag?
regds
CSDA1 that feature does not exist at this time. You can read above in the thread to learn about the many challenges and questions about that. That's however a feature I've been working on for my premium forms extension.
raafirivero Please let us know when you update your extension option. Looks amazing
Aleram and @Mark73 Hey sorry, I've had a pretty dramatic change in my work situation since June and basically haven't been able to work on my Flarum project at all since then. You're welcome to fork it on GitHub and run it on your own install (it was working great on mine before I had to leave). Trying to find time to get back to working on it but it won't be until November at the earliest.
raafirivero if/when able, please create a new Extension discussion (or maybe under Dev if it's still under development) for your own extension so that users have a place to comment about the fork.
This discussion is about the official FoF Mason extension and I'd like to avoid as much confusion as possible. Maybe we should have a GitHub issue somewhere if we want to discuss merging your features back to the main extension. Feel free to create an issue on our GitHub repo 
