Open itsme-to opened 1 week ago
@svaningelgem if you want to make this really nice feature back again <3
_
can't be supported because it wont work with placeholders
_
can't be supported because it wont work with placeholders I see, so-
will work ?
_
can't be supported because it wont work with placeholders
Is it possible to get a bit of insight on how this placeholders work together with _
? So I can maybe think of another way around it (if at all possible)?
Yeah don't working fine currently
placeholder API hook uses _
delimiter for splitting
maybe -
can be supported safely, i need to check that though
maybe
-
can be supported safely, i need to check that though
Yes, without too much trouble, and it's still much simpler visually.
It's way better
In the latest release, Papi placeholders work well with -
, so it's really just the check that's causing issues in the latest dev build.
Ill try implementing it in a more proper way
Currently I will give you a temporary fix, however it still needs to be fixed in a more proper way so we can allow _
usage as well lol
artifacts.zip
Great it's work fine, can you add it to the dev build ? So my client can use it as well ?
Oh great, I didn't see it
possible to add _ back ?
possible to add _ back ?
But there is no way to make it work properly with placeholders
Description of Bug
In the latest devbuild, you can't use anymore
_
&-
inside quest id. It's maybe related to that commit, https://github.com/LMBishop/Quests/commit/aea66501e1019162bb670aa0f97761f637bae847The support of
-
and_
was added on this one https://github.com/LMBishop/Quests/commit/a184e76053aa55df4fb5f156fa6c5c0ecb8f811dSteps to Reproduce
Use the latest devbuild and try to create a quest with
_
or-
in the nameEnvironment
Agreements
Other
No response