NLthijs48
Execute command when walking into or exiting a region: title and action bar messages
By NLThijs48: Current solution, use WorldGuard Extra Flags
HI
I just want to know if you can ADD titles when player enter inside an areashop region.
It will be MUCH better than the chat messages. Also, I think you should remove the message that say to the areashop region owner: greeting-rented: "%region% is rented by %player% until %until%." It was not necessary I think.
Thank you so much
Until realization this may be partially achieved by using a plugin called WorldGuardExtraFlags. This allows to to execute commands on player entering/leaving a region. To say execute a title message for a certain player. However it is not a direct integration into AS, therefore all these flags have to be set manually.
@EvilOlaf And for this: Also, I think you should remove the message that say to the areashop region owner: greeting-rented: "%region% is rented by %player% until %until%." It was not necessary I think.
Is it possible?
Go to flagProfiles: section and simply comment or remove the line beginning with greeting:
@EvilOlaf I disable EVERY greeting: things and I continue to see the:
It was my OWN shop. Is it possible to hide this message ONLY for the areashop region owner? But display it to all other players?
Thank you
@maxlehot1234 You can only have the message active for anyone, or for nobody, it cannot be different per player. AreaShop simply uses the greeting flag of WorldGuard regions, which only offers this option.
The reason that the greeting sticks is that AreaShop only touches the flags that you told it to change. Simply change the greeting lines to greeting: '' instead of commenting them out and AreaShop will remove the greeting flags when you reload.
@EvilOlaf
Might also want to consider that WGExtraFlags has a hard dependency on WG 6.1.3 or higher.
A lot of servers (mine included) still use WG 6.1.2 bc of things like custom plugins & custom flags which work perfectly with that WG version.
More info: 6.1.2 -> 6.1.3 is actually a major version change. 6.1.3 is the version that WG added their own custom flags API, which broke the WGCustomFlags plugin on bukkit. This is the plugin that keeps a lot of servers running WG6.1.2. This plugin and WG6.1.3 handle custom flags differently, so 6.1.3 rekt this plugin, but everyone's custom plugins relied (still rely) on WGCustomFlags which only supports 6.1.2
