My favorites | Sign in
Project Home Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 99: Remove need for 1/0 after chat commands
4 people starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  ----


 
Reported by DEMONI...@gmail.com, Jun 10, 2010
Of course, I don't see any reason to remove the 1/0 altogether, but it'd be nice if Evolve could automatically detect that "randomguest10-2-infinity" was granted !nolimits, so when I go to restore his prop limits, I don't have to type "!nolimits random 0", but instead can simply type "!nolimits random".

If it isn't obvious why the 1/0 should remain, though... If I simply don't remember whether or not I restored randomguest10-2-infinity's prop limits, I can easily type "!nolimits random 0" to ensure he doesn't have them.

Also, on that note, it'd be cool if Evolve told me "This user is already ignited!" when I try to re-ignite someone who is already ignited, etc. Not a big deal at all, but while you're writing checks for this suggestion (should you choose to tackle it), I'm sure this wouldn't be very hard to add, since all it'd be is in the event that a user DOES use the 1/0 to force/check that a flag has been applied to a player. (Again, this bit isn't a big deal though, and I wouldn't mind if it never made it in.)

Thanks again! :D
Jun 11, 2010
Project Member #1 overv161@gmail.com
I have wanted to do this for a long time, but I'm not sure how to handle multiple players with toggling yet.
Status: Accepted
Oct 14, 2010
#2 samsnatw...@gmail.com
This should be easy to do, i have always wanted this it is kinda anoying to do 1/0 all the time. But ti would also be cool to have both so it detects if there is a 1 and then gives them no limits when you do "!nolimits person 1" or detects if they have limits or not then when you do "!nolimits person" they have nolimits because they had limits before. That would be nice and work for all people.
Oct 14, 2010
Project Member #3 overv161@gmail.com
Ehm, I was talking about handling this situation:

ply1 has noclip enabled
ply2 has noclip enabled
ply3 doesn't have noclip enabled
ply4 doesn't have noclip enabled

!noclip ply1 ply2 ply3 ply4
Oct 16, 2010
#4 thatcute...@gmail.com
For non 1:1 situations, taking the percentage of the toggle states of the players and using the greater percentage to override the current state for all players. e.g.

ply1 noclip enabled
ply2 noclip disabled
ply3 noclip disabled

Assume ALL are disabled.

For the 1:1 situations, I think some sort of bias would be needed, maybe one that can be changed via chat command, and perhaps a different bias for different states based on the nature of the command (though that might be a little much overkill, still nice though)  Here's a situation

Assign Igniting with a bias of 0 or off, as you're more likely to turn it off than on (unless you are an evil admin.

ply1 is ignited
ply2 is ignited
ply3 is not ignited
ply4 is not ignited


In pseudo,  

globalbias = 0
if percentage on == percentage off  then
        if globalbias == 0 then  extinguish all players
        else  ignite all players

Not the best pseudo I know, I think it gets the point across though. What thinks other people? Sure a few refinements to this idea are floating about :)

Side note, I guess just number comparison instead of doing percents is less work, both for coder and interpreter . Whatever you prefer :P

Oct 16, 2010
#5 thatcute...@gmail.com
Another side note- I think keeping the 1/0 argument as an master override would be good too. A little direct control for the people that enjoy commandlines :P  Sorry for the Comment spam.  <3
Nov 29, 2010
#6 dancedan...@deadvalley.net
Perhaps it could call for a new line of commands t that needs to be issued,
eg: !blind
    !unblind
However, it would only make sence for a few of the commands.
Nov 29, 2010
#7 DEMONI...@gmail.com
Agree with #6 (and #5 was mentioned in the first line of the bug tracker, haha, but yeah, it'd be super handy for someone wanting to make SURE you're not on fire anymore instead of accidentally setting you on fire again, etc).

So, I suppose the question though is... how does Evolve handle states? Does it even *have* states? For example...

!ignite overv

BLAM! You're set on fire! YAY! Teehee... :D

But... what happens? Does the game just go "add fire to overv" and that's it? Does it go "overv is now on fire *ticks check box*, and add fire! *adds fire*"? How? (If it works the second way, I'm sure you can guess how to fix this, haha)
Feb 18, 2011
#8 jimvanko...@gmail.com
I'd like to see
!gag
!ungag
!mute
!unmute
!ignite
!unignite
!noclip
!unnoclip
etc.

Powered by Google Project Hosting