07-23-2022, 12:01 AM
Firstly, roll can be used in a constructive way, or it can trivialize roleplay. We used it on Halo for a time, but staff had to instructed not to use it. We had a few issues, firstly, it's easy for a failed roll to be turned into a stupid outcome (take for example, failing to knock out a prisoner without a gun, so as a result, the prisoner is up and shooting with a new spawned gun) - this issue isn't an issue if the GMs are good and/or the staff manager keeps an eye on things. The other issue is more insidious, it is that someone could roleplay a lot, or roleplay a little, then be told to roll, and have a 50/50 regardless of the thought put into roleplay. It makes useless the thought and care put into solving a problem. A solution here is again good GMs and management, and more technically, something like a difficulty class from tabletop games like d&d, where a success isn't 51+, it is set to be higher or lower depending on the difficulty of the task, and the roleplay of the player.
Rolling can be done wrong. If rolling is added, that should be kept in mind
Next, I did make a change to the roll command to try and prevent cheating on Halo, so I do probably have that code if needed. The addon on the workshop formatted it as 'Lexa has rolled a 30.' which makes it easy to /me, the changed version formatted it as 'Lexa has rolled a: 56.', in addition, if a staff member (as defined by a ULX permission) was too far away to see the text, they would see '[Roll] Lexa has rolled a: 56.'. This was especially needed for Halo, where a significant amount of roleplay is predicated on staff involvement, but on GoM, local chat might be enough (maybe always with the red [Roll] to prevent atlas chat fuckery). A caveat is that I had to change half a dozen DarkRP functions to add the third colour whilst keeping the code similar to the style of the surrounding code, so I'd need to cut around my work to be sure I have everything.
If it's helpful, and the /roll on the workshop is the only formatting out there (the /me exploitable kind), I do have code to halp
Rolling can be done wrong. If rolling is added, that should be kept in mind
Next, I did make a change to the roll command to try and prevent cheating on Halo, so I do probably have that code if needed. The addon on the workshop formatted it as 'Lexa has rolled a 30.' which makes it easy to /me, the changed version formatted it as 'Lexa has rolled a: 56.', in addition, if a staff member (as defined by a ULX permission) was too far away to see the text, they would see '[Roll] Lexa has rolled a: 56.'. This was especially needed for Halo, where a significant amount of roleplay is predicated on staff involvement, but on GoM, local chat might be enough (maybe always with the red [Roll] to prevent atlas chat fuckery). A caveat is that I had to change half a dozen DarkRP functions to add the third colour whilst keeping the code similar to the style of the surrounding code, so I'd need to cut around my work to be sure I have everything.
If it's helpful, and the /roll on the workshop is the only formatting out there (the /me exploitable kind), I do have code to halp
Sign in to vote | +1
