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

Feature request: add "additional parameters" argument when using sm_forcertd #87

Closed
Tiagoquix opened this issue Dec 22, 2023 · 1 comment

Comments

@Tiagoquix
Copy link
Contributor

The new RTD major update with its default values brought a lot of cool things, but, at the same time, it ended up removing certain aspects of the Old RTD™.

I would like to create a new argument when using sm_forcertdRTD mode:

[SM] Usage: sm_forcertd <player> <perk id>* <time>* <override class restriction (0 / 1)>* <additional parameters>

This argument would cause the effect specified via ForceRTD to use a different mode/attribute etc. than the configured defaults.

The argument, of course, would be optional. If none was given, the default behavior would be assumed.

For instance:
sm_forcertd @me 4 60 1 mode;1 -> would make myself have the Flying effect, but with the Noclip mode.

sm_forcertd @me 0 60 1 mode;1;uber;1 -> godmode with normal self-damage and uber (overriding default values); use default "resistance" value from server config.

sm_forcertd @me 0 60 1 mode;-1;resistance;0.75 -> no self-damage, use default "uber" value in server's configuration file, and 25% resistance.

sm_forcertd @me 35 10 1 force;8192 -> Firework with double force.

And so on.

Basically, the idea is to be able to customize anything inside the settings section from individual effects directly from the command.

It would be cool to have this feature implemented.

Thanks for reading.

@Phil25
Copy link
Owner

Phil25 commented Dec 22, 2023

Hey thanks for the issue! I actually had this idea already and planning to add it to the future 3.0.0 version.

I’m gonna close this as a duplicate of #76.

@Phil25 Phil25 closed this as completed Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants