Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changing the name #594

Open
MEOW2006 opened this issue Dec 10, 2021 · 1 comment
Open

changing the name #594

MEOW2006 opened this issue Dec 10, 2021 · 1 comment
Labels
NEW New issue, needs to be classified Type: Support Request for support with configuration/setup

Comments

@MEOW2006
Copy link

hi
i want when player buy a shop region
the shop region name change to the player name

@MEOW2006 MEOW2006 added NEW New issue, needs to be classified Type: Support Request for support with configuration/setup labels Dec 10, 2021
@iiMilan
Copy link

iiMilan commented Jun 23, 2022

I found this in the default.yml files:
Maybe you can change some things of this to get your thing you needed.

  ##### Run commands when an event happens.
  # Commands at a 'before' section will execute before the region details are changed in the AreaShop system
  # and before any other actions occurred (setting the owner, saving/loading schematics, etc.),
  # the 'after' commands will be run when all changes are done.
  # You can add a list of commands to 'before' and 'after'.
  eventCommandProfile:
    created:
      before:
      after:
    #  - "say An AreaShop region has been created: %region%"
    deleted:
      before:
      after:
    rented:
      before:
      after:
    extended:
      before:
      after:
    unrented:
      before:
      after:
    bought:
      before:
      after:
    sold:
      before:
      after:
    resell:
      before:
      after:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NEW New issue, needs to be classified Type: Support Request for support with configuration/setup
Projects
None yet
Development

No branches or pull requests

2 participants