I'm trying to add permission rewards on one of my quests, the rewards are 2 spells (From Magicspells) and a pex permission removal. Example: "c teach [player] "Wind release: Rushing Wind dragon,c teach [player] "Wind style: Rasengan, pex user [player] remove element".

See, it works, but not all of it. It just adds some of it, as there isn't enough space to add more. Is there a way to add more permissions? Instead of just 2 lines.

It looks like this,

- c teach [player] "Wind release: Rushing wind dragon
- c teach [player] "Wind style: Rasengan

But sadly, it doesn't add the pex user [player] remove element due to not enough space to write more.

I want it to give all 3, like:

- c teach [player] "Wind release: Rushing wind dragon
- c teach [player] "Wind style: Rasengan
- pex user [player] remove element

Hi,

As for this limitation you're mentioning, I have not encountered this myself as of yet; as a possible solution, you could try editing the quests.yml to manually add it to your quest, rather than using the in-game quest editor.

This comes with a warning however; create a backup of your quest.yml file before editing, as it's easy to make a mistake in your coding; resulting in the file not parsing when reloading the plugin.

Then a question of my own; could you show me the variable you're using to target the player that's completing the quest? If I put [player] or "[player]" down, I find a new entry in my permissions.yml file called [player], rather than a permission having been added to say, myself.

Furthermore, I'm not the Owner of the server. So I can't really access the
.yml file.
On Sat, Aug 6, 2016 at 12:43 AM massive mmortal [email protected] wrote:

It is

On Fri, Aug 5, 2016 at 11:19 PM LeafyMitsuwa [email protected]
wrote:

Hi,

As for this limitation you're mentioning, I have not encountered this
myself as of yet; as a possible solution, you could try editing the
quests.yml to manually add it to your quest, rather than using the in-game
quest editor.

This comes with a warning however; create a backup of your quest.yml file
before editing, as it's easy to make a mistake in your coding; resulting in
the file not parsing when reloading the plugin.

Then a question of my own; could you show me the variable you're using to
target the player that's completing the quest? If I put [player] or
"[player]" down, I find a new entry in my permissions.yml file called
[player], rather than a permission having been added to say, myself.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#385 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATm2C1yW88EpFhVbYuYn2SGGKZoQs4sTks5qdCdYgaJpZM4JQzXE
.

It is

On Fri, Aug 5, 2016 at 11:19 PM LeafyMitsuwa [email protected]
wrote:

Hi,

As for this limitation you're mentioning, I have not encountered this
myself as of yet; as a possible solution, you could try editing the
quests.yml to manually add it to your quest, rather than using the in-game
quest editor.

This comes with a warning however; create a backup of your quest.yml file
before editing, as it's easy to make a mistake in your coding; resulting in
the file not parsing when reloading the plugin.

Then a question of my own; could you show me the variable you're using to
target the player that's completing the quest? If I put [player] or
"[player]" down, I find a new entry in my permissions.yml file called
[player], rather than a permission having been added to say, myself.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#385 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATm2C1yW88EpFhVbYuYn2SGGKZoQs4sTks5qdCdYgaJpZM4JQzXE
.

Hai,

Thank you for your feedback, is what does it for me, thank you very much!

As for your limitation, then I guess you'll have to ask the server administrator/owner for access to the file, or request a pull request for that file, since editing that file is not limited to the same limitation as in-game chat sets.

My advice for you, set placeholders for yourself, so when you do have access to the file, you can easily replace multiple placeholders, for say, dialogue or rewards, without straining the administrator/owner with every update you make -- just trying to offer efficiency tips.

Goodluck!