nss_pinboard 
Update v1.0.2 available
→ Results of automated processes are shown in discord more clear, e.g. “System” instead of character name.
→ Results of console commands are shown in discord more clear, e.g. “Marti McFly (via Console)”.
→ Add Config.DiscordWebhook.system_user_alias to config file, see example in config.demo.lua.
→ Add key discord_console_command to languages.
→ Fix to many linebreaks in poster text.
What must be considered during the update?
→ Update your config file with the new Config.DiscordWebhook.system_user_alias
value.
→ Update your language file(s) with the discord_console_command
key.
1 Like
nss_pinboard 
Version 1.1.0 available:
- Add possibility to pin a new notice everywhere at once. - Permissions of new feature is configurable for groups and character names (full names). - Add new language keys
discord_location_everywhere
, post_everywhere_at_once
, post_everywhere_at_once_every_where
and post_everywhere_at_once_only_here
. - Update discord webhook to show as location “everwhere” if someone uses the new feature. - Admins always have the permission to use the new feature.
What must be considered during the update?
- Update your config file with the new
Config.PostEverywhereAtOncePermissions
value (see config.demo.lua
for details. - Update your language file(s) with new keys (see above).
nss_pinboard 
Version 1.1.1 available:
- Bugfix: Order of text sections are now correct if inserted between two existing sections.
What must be considered during the update?
- Nothing. No configs or languages has been changed.
nss_pinboard 
nss_pinboard v1.1.2 available:
- Add
hide_blip
property for Config.Posters
. If set to true
no blip is shown on the map for the related pinboard. See config.demo.lua
for example.
What must be considered during the update?
nss_pinboard 
nss_pinboard v1.1.3 available:
- Add optional new config attribute Config.DiscordWebhook.webhook_url_new for only new pinboard notifications.
- Add optional new config attribute Config.DiscordWebhook.anonymous_new which hides the character name for webhook_url_new notifications. This have no effect to webhook_url notifications.
- Add optional new config attribute Config.DiscordWebhook.webhook_url_removed for only removed pinboard notifications.
- Add optional new config attribute Config.DiscordWebhook.anonymous_remover which hides the character name for webhook_url_removed notifications. This have no effect to webhook_url notifications.
- Change config attribute Config.DiscordWebhook.webhook_url to be optional. It still sends all types of notifications to the same webhook but all authors and removers are not anonymous.
- Add new translation discord_anonymous_user for anonymous characters for webhook_url_new and webhook_url_removed notifications.
- Moved changelog from README.md to CHANGELOG.md.
What must be considered during the update?
- Check the new config attributes in config.demo.lua and adapt your config.lua.
- Check the language files for the new translation key.
nss_pinboard 
nss_pinboard v1.1.5 available
- Add new restrict_create_by_jobs in Config.Posters to restrict the creation of new posters to one or more specific jobs. See config.demo.lua for more information and examples.
What must be considered during the update?
Was wondering if it would be possible to have individual webhooks for individual boards?
It is not planned that each Pinnborad gets its own webhook.
nss_pinboard 
nss_pinboard v1.1.6 available:
This update is recommended.
- Config.JobRemovePermissions now checks correctly if job grade is equal or higher than the required grade (before it was checked if the job grade of the player was equal or lower to remove notices - whats wrong)
What must be considered during the update?
nss_pinboard 
nss_pinboard v1.1.7 available:
- Discord webhooks are now optionally configurable each board.
What must be considered during the update?
- You find examples for the new feature in the config.demo.lua file.
nss_pinboard 
nss_pinboard v1.1.8 available:
- Add new required board property group. Restricts “post to all” feature to specific board groups.
- Add new optional board property restrict_view_by_jobs. Restricts the access to view a board (and blip) to one or more specific jobs.
What must be considered during the update?
- You find examples for the new config attributes in the config.demo.lua file.
- Add the new required group attribute to each board config to group you boards. If you only have public boards then name your group for example “Public”.
nss_pinboard 
nss_pinboard v1.1.9 available:
This update is recommended.
Fix jpeg support for images (currently jpg, jpeg, png and webm are supported).
What must be considered during the update?
Nothing.
nss_pinboard 
nss_pinboard v1.2.1 available: This update is optional.
- (Only) Update example
map/bulletin_boards_config.lua
and add missing group
property.
What must be considered during the update?
nss_pinboard 
nss_pinboard v1.2.2 available:
This update is optional.
Image urls with search params like https://example.com/image.jpg?xyz=123 are now supported, too.
What must be considered during the update?
Nothing.
nss_pinboard v1.3.0 available: 
This update is optional.
- Extend comments of
config.demo.lua
for more clarity.
- Add some debug prints to
actions.lua
because in newer versions of vorp_core
sometimes (especially on many players) no char data available if should.
- Add torn sheet for broken image (e.g. that can no longer be found).
- Add alternative style of bulletin board. See examples in
config.demo.lua
with new poster configuration attribute alternative_style
.
- Add new optional “close bulletin board on damage or combat” feature. See
Config.HideOnCombatOrDamage
in config.demo.lua
.
What must be considered during the update? 
- New language keys added (see
New since 1.3.0
marks). Please add it to your language file(s).
- Compare your
config.demo.lua
with your config.lua
to consider new options (see New since 1.3.0
marks).
nss_pinboard v1.3.2 available: This update is optional 
- Add optional
Config.UseZAxisForOpenPromptRadius
to enable z axis check for open prompt. See config.demo.lua
for more information.
What must be considered during the update?
- Compare your
config.demo.lua
with your config.lua
to consider new options (see New since 1.3.2
marks).