[Accepted] Ultimate Prop Suggestions 2.0

Please, Please, Please, i really beg you stop. all these commands needs an encyclopedia so convert to GUI man, we can add cool stuff like managing properties options by checkboxes and another cool stuff... JUST DO IT
Any way until the GUI is done, there is some suggestion

Another note, My dream is to completely make props as servers(game modes).

1- /SetPropChat <1/0> [Difficulity: Easy]
This command used to set whether you want to make people in your prop able to communicate with oher people in another worlds, what i mean ability to make prop players able to see/write another worlds/main world chat.
Why?
because sometimes its hard to set events/doing CDs/another reasons that because of the flood of the main chat make communicating in same prop hard.
1- /PropBan <playername> [Difficulity: Medium]
Ability to ban peoples from a specific prop
Why?
Because some people are annoying/or another special reasons, that can help in controling the property as i mentioned above  for good control.
2- /OnPlayerInArea <x> <y> <then>[Difficulity: Extreamly hard] (*1*)
the events in "then" affects on players or some property info, suggested events: {death for player, showing a message, showing a prop ann, playing a sound?, checkpoint?, whatever>
3- /AddSpectate <savedloc> <angle in radian> <time in seconds>[Difficulity: Easy]

For: when player get in that pickup it make his able to spectate a special location  the prob.
Why?: as example i want when the player won a race as example his camera spectate the end of the race to see who or any place else
4- /PropAnn <style> <message>[Difficulity: Extreamly hard]
For sending ann for the property by Level 4, the game
Why? because of better attenntion
Note: for the tildes(~) although they are useful it can crash the players, you can add something that checks if the ~ is used good because its really usefull for coloring its really up to you.
5- Adding another argument for the command /AddMessageMickup <style(message/ann> <message>[Difficulity: Easy]
Why? because its usefull for races or if chat is flooded.
6- /PropBring <name> [Difficulity: Easy]
For: Bringing a player to the bringer by level4.
Why? usefull for setting non-event-staff based events
Note: Please dont add that gay "accept to bring"

------------------------------------------------------------
*1*: Im trying to make sort of transpiler in squriel that make people able to make their scripts in my lang that affects on props, my planned example if i got time:

Code:


OnPlayerDeath = AddMessage __PLAYERNAME__ "Died"


this for when player dies event it will send a property message as example with his name that he died. if i got time i may implement that in squrriel.

yea these all suggestions were in my mind but I thought they can't be added by Angel .

Why no add /propmute, /proptempban, /propslap and /propdown.
-1 for 1st one completely useless.
-1 for /propban there is always /propkick cmd
-1 for 3rd one dont really want any one to spec anyone while there spawn except admins.
-1 for 4th one bad idea ever.
-1 for 6th bad idea what if some one jump in water and use /bring signal or max.
Just give prop administration commands, no offense.

+1

Zurix wrote:Please, Please, Please, i really beg you stop. all these commands needs an encyclopedia so convert to GUI man, we can add cool stuff like managing properties options by checkboxes and another cool stuff... JUST DO IT
Any way until the GUI is done, there is some suggestion

Another note, My dream is to completely make props as servers(game modes).

1- /SetPropChat <1/0> [Difficulity: Easy]
This command used to set whether you want to make people in your prop able to communicate with oher people in another worlds, what i mean ability to make prop players able to see/write another worlds/main world chat.
Why?
because sometimes its hard to set events/doing CDs/another reasons that because of the flood of the main chat make communicating in same prop hard.
1- /PropBan <playername> [Difficulity: Medium]
Ability to ban peoples from a specific prop
Why?
Because some people are annoying/or another special reasons, that can help in controling the property as i mentioned above  for good control.
2- /OnPlayerInArea <x> <y> <then>[Difficulity: Extreamly hard] (*1*)
the events in "then" affects on players or some property info, suggested events: {death for player, showing a message, showing a prop ann, playing a sound?, checkpoint?, whatever>
3- /AddSpectate <savedloc> <angle in radian> <time in seconds>[Difficulity: Easy]

For: when player get in that pickup it make his able to spectate a special location  the prob.
Why?: as example i want when the player won a race as example his camera spectate the end of the race to see who or any place else
4- /PropAnn <style> <message>[Difficulity: Extreamly hard]
For sending ann for the property by Level 4, the game
Why? because of better attenntion
Note: for the tildes(~) although they are useful it can crash the players, you can add something that checks if the ~ is used good because its really usefull for coloring its really up to you.
5- Adding another argument for the command /AddMessageMickup <style(message/ann> <message>[Difficulity: Easy]
Why? because its usefull for races or if chat is flooded.
6- /PropBring <name> [Difficulity: Easy]
For: Bringing a player to the bringer by level4.
Why? usefull for setting non-event-staff based events
Note: Please dont add that gay "accept to bring"

------------------------------------------------------------
*1*: Im trying to make sort of transpiler in squriel that make people able to make their scripts in my lang that affects on props, my planned example if i got time:

Code:


OnPlayerDeath = AddMessage __PLAYERNAME__ "Died"


this for when player dies event it will send a property message as example with his name that he died. if i got time i may implement that in squrriel.

I like how you define the difficulty.

I've already pretty much made it like the properties are their own game mode with the property stats system. Not much more I can do, I think you guys can pretty much do anything.

Right now I've focused a lot on properties so I am not going to make that many more features for the next patch at all. As I've mentioned in the past we have 6-8 different huge systems and I can't focus on them all at the same time. This last patch I added some minigames (after not adding any for several patches), I made a huge update to the property system and more. So don't expect too many more property scripts for a while except small commands.

1. Don't really understand the logic here. You want to prevent people in your property from talking? There are still other people in other worlds that will be able to talk. I am not sure about if I like this suggestion.


1.2. propban. You numbered them wrong btw. Definitely something that I want to add. It won't be database based though, it will probably be an array stored on the normal server until the server closes.

2. I don't understand this one.

3. The camera is something I've been thinking of for a very long time. It's on my suggestion list from before. The only minor problem I have right now, how to exit the camera mode and not trigger the pickup again? Any ideas would be great. Kinda hard to say.

4. I am pretty sure that symbol doesn't crash people anymore, I've tried it and can't seem to trigger it no more.
Propanns? Maybe, but I feel like the people who needs anns are people hosting events = event staff members mainly. There is an eventann for that

5. Explain more please?

6. Same as 4, these commands are useful for events and that's why you should join the event staff if you want access to them.


Overall I'll probably add the camera and propban command at some point. Maybe soon.

About the GUI, eventually I'll probably do that if we last long enough. Got the 500 VK token (secret of VKs), another job coming up hopefully next patch. I'll also finish my final version of the rel006 script hopefully. I've been kinda holding off on the rel006 version due to mostly bugs that the developers don't fix. I've reported a few in PMs and in topics, but nothing seemed to have happened.

Chuck norris wrote:
3. The camera is something I've been thinking of for a very long time. It's on my suggestion list from before. The only minor problem I have right now, how to exit the camera mode and not trigger the pickup again? Any ideas would be great. Kinda hard to say.

player.Pos.x -= 2
Then function.

Or on camera picked player.iD].camerapick = 1
And then
Onpickuppicked
If ( player.ID].camerapick == 1) return 0
And then
On the function where exited camera mode
NewTimer("decrease pick", 2000,1,playe4.ID)
Funcyion decreasepick(player)
Player.ID].camerapick = 0

Nah.

Chuck Norris wrote:

Zurix wrote:Please, Please, Please, i really beg you stop. all these commands needs an encyclopedia so convert to GUI man, we can add cool stuff like managing properties options by checkboxes and another cool stuff... JUST DO IT
Any way until the GUI is done, there is some suggestion

Another note, My dream is to completely make props as servers(game modes).

1- /SetPropChat <1/0> [Difficulity: Easy]
This command used to set whether you want to make people in your prop able to communicate with oher people in another worlds, what i mean ability to make prop players able to see/write another worlds/main world chat.
Why?
because sometimes its hard to set events/doing CDs/another reasons that because of the flood of the main chat make communicating in same prop hard.
1- /PropBan <playername> [Difficulity: Medium]
Ability to ban peoples from a specific prop
Why?
Because some people are annoying/or another special reasons, that can help in controling the property as i mentioned above  for good control.
2- /OnPlayerInArea <x> <y> <then>[Difficulity: Extreamly hard] (*1*)
the events in "then" affects on players or some property info, suggested events: {death for player, showing a message, showing a prop ann, playing a sound?, checkpoint?, whatever>
3- /AddSpectate <savedloc> <angle in radian> <time in seconds>[Difficulity: Easy]

For: when player get in that pickup it make his able to spectate a special location  the prob.
Why?: as example i want when the player won a race as example his camera spectate the end of the race to see who or any place else
4- /PropAnn <style> <message>[Difficulity: Extreamly hard]
For sending ann for the property by Level 4, the game
Why? because of better attenntion
Note: for the tildes(~) although they are useful it can crash the players, you can add something that checks if the ~ is used good because its really usefull for coloring its really up to you.
5- Adding another argument for the command /AddMessageMickup <style(message/ann> <message>[Difficulity: Easy]
Why? because its usefull for races or if chat is flooded.
6- /PropBring <name> [Difficulity: Easy]
For: Bringing a player to the bringer by level4.
Why? usefull for setting non-event-staff based events
Note: Please dont add that gay "accept to bring"

------------------------------------------------------------
*1*: Im trying to make sort of transpiler in squriel that make people able to make their scripts in my lang that affects on props, my planned example if i got time:

Code:


OnPlayerDeath = AddMessage __PLAYERNAME__ "Died"


this for when player dies event it will send a property message as example with his name that he died. if i got time i may implement that in squrriel.

I like how you define the difficulty.

I've already pretty much made it like the properties are their own game mode with the property stats system. Not much more I can do, I think you guys can pretty much do anything.

Right now I've focused a lot on properties so I am not going to make that many more features for the next patch at all. As I've mentioned in the past we have 6-8 different huge systems and I can't focus on them all at the same time. This last patch I added some minigames (after not adding any for several patches), I made a huge update to the property system and more. So don't expect too many more property scripts for a while except small commands.

1. Don't really understand the logic here. You want to prevent people in your property from talking? There are still other people in other worlds that will be able to talk. I am not sure about if I like this suggestion.


1.2. propban. You numbered them wrong btw. Definitely something that I want to add. It won't be database based though, it will probably be an array stored on the normal server until the server closes.

2. I don't understand this one.

3. The camera is something I've been thinking of for a very long time. It's on my suggestion list from before. The only minor problem I have right now, how to exit the camera mode and not trigger the pickup again? Any ideas would be great. Kinda hard to say.

4. I am pretty sure that symbol doesn't crash people anymore, I've tried it and can't seem to trigger it no more.
Propanns? Maybe, but I feel like the people who needs anns are people hosting events = event staff members mainly. There is an eventann for that

5. Explain more please?

6. Same as 4, these commands are useful for events and that's why you should join the event staff if you want access to them.


Overall I'll probably add the camera and propban command at some point. Maybe soon.

About the GUI, eventually I'll probably do that if we last long enough. Got the 500 VK token (secret of VKs), another job coming up hopefully next patch. I'll also finish my final version of the rel006 script hopefully. I've been kinda holding off on the rel006 version due to mostly bugs that the developers don't fix. I've reported a few in PMs and in topics, but nothing seemed to have happened.

You better like forget about those things and focus on rel006.

Roycewicz wrote:Nah.

Chuck Norris wrote:

Zurix wrote:Please, Please, Please, i really beg you stop. all these commands needs an encyclopedia so convert to GUI man, we can add cool stuff like managing properties options by checkboxes and another cool stuff... JUST DO IT
Any way until the GUI is done, there is some suggestion

Another note, My dream is to completely make props as servers(game modes).

1- /SetPropChat <1/0> [Difficulity: Easy]
This command used to set whether you want to make people in your prop able to communicate with oher people in another worlds, what i mean ability to make prop players able to see/write another worlds/main world chat.
Why?
because sometimes its hard to set events/doing CDs/another reasons that because of the flood of the main chat make communicating in same prop hard.
1- /PropBan <playername> [Difficulity: Medium]
Ability to ban peoples from a specific prop
Why?
Because some people are annoying/or another special reasons, that can help in controling the property as i mentioned above  for good control.
2- /OnPlayerInArea <x> <y> <then>[Difficulity: Extreamly hard] (*1*)
the events in "then" affects on players or some property info, suggested events: {death for player, showing a message, showing a prop ann, playing a sound?, checkpoint?, whatever>
3- /AddSpectate <savedloc> <angle in radian> <time in seconds>[Difficulity: Easy]

For: when player get in that pickup it make his able to spectate a special location  the prob.
Why?: as example i want when the player won a race as example his camera spectate the end of the race to see who or any place else
4- /PropAnn <style> <message>[Difficulity: Extreamly hard]
For sending ann for the property by Level 4, the game
Why? because of better attenntion
Note: for the tildes(~) although they are useful it can crash the players, you can add something that checks if the ~ is used good because its really usefull for coloring its really up to you.
5- Adding another argument for the command /AddMessageMickup <style(message/ann> <message>[Difficulity: Easy]
Why? because its usefull for races or if chat is flooded.
6- /PropBring <name> [Difficulity: Easy]
For: Bringing a player to the bringer by level4.
Why? usefull for setting non-event-staff based events
Note: Please dont add that gay "accept to bring"

------------------------------------------------------------
*1*: Im trying to make sort of transpiler in squriel that make people able to make their scripts in my lang that affects on props, my planned example if i got time:

Code:


OnPlayerDeath = AddMessage __PLAYERNAME__ "Died"


this for when player dies event it will send a property message as example with his name that he died. if i got time i may implement that in squrriel.

I like how you define the difficulty.

I've already pretty much made it like the properties are their own game mode with the property stats system. Not much more I can do, I think you guys can pretty much do anything.

Right now I've focused a lot on properties so I am not going to make that many more features for the next patch at all. As I've mentioned in the past we have 6-8 different huge systems and I can't focus on them all at the same time. This last patch I added some minigames (after not adding any for several patches), I made a huge update to the property system and more. So don't expect too many more property scripts for a while except small commands.

1. Don't really understand the logic here. You want to prevent people in your property from talking? There are still other people in other worlds that will be able to talk. I am not sure about if I like this suggestion.


1.2. propban. You numbered them wrong btw. Definitely something that I want to add. It won't be database based though, it will probably be an array stored on the normal server until the server closes.

2. I don't understand this one.

3. The camera is something I've been thinking of for a very long time. It's on my suggestion list from before. The only minor problem I have right now, how to exit the camera mode and not trigger the pickup again? Any ideas would be great. Kinda hard to say.

4. I am pretty sure that symbol doesn't crash people anymore, I've tried it and can't seem to trigger it no more.
Propanns? Maybe, but I feel like the people who needs anns are people hosting events = event staff members mainly. There is an eventann for that

5. Explain more please?

6. Same as 4, these commands are useful for events and that's why you should join the event staff if you want access to them.


Overall I'll probably add the camera and propban command at some point. Maybe soon.

About the GUI, eventually I'll probably do that if we last long enough. Got the 500 VK token (secret of VKs), another job coming up hopefully next patch. I'll also finish my final version of the rel006 script hopefully. I've been kinda holding off on the rel006 version due to mostly bugs that the developers don't fix. I've reported a few in PMs and in topics, but nothing seemed to have happened.

You better like forget about those things and focus on rel006.

He will only going to release rel006 after patch 5.0.

гомосексуалиста
or in other words
гей
You still can't translate it ?
Well good luck trying to solve it.
The best part is the the meaning of those words.

#narkotik_kal

Chuck Norris wrote:

Zurix wrote:Please, Please, Please, i really beg you stop. all these commands needs an encyclopedia so convert to GUI man, we can add cool stuff like managing properties options by checkboxes and another cool stuff... JUST DO IT
Any way until the GUI is done, there is some suggestion

Another note, My dream is to completely make props as servers(game modes).

1- /SetPropChat <1/0> [Difficulity: Easy]
This command used to set whether you want to make people in your prop able to communicate with oher people in another worlds, what i mean ability to make prop players able to see/write another worlds/main world chat.
Why?
because sometimes its hard to set events/doing CDs/another reasons that because of the flood of the main chat make communicating in same prop hard.
1- /PropBan <playername> [Difficulity: Medium]
Ability to ban peoples from a specific prop
Why?
Because some people are annoying/or another special reasons, that can help in controling the property as i mentioned above  for good control.
2- /OnPlayerInArea <x> <y> <then>[Difficulity: Extreamly hard] (*1*)
the events in "then" affects on players or some property info, suggested events: {death for player, showing a message, showing a prop ann, playing a sound?, checkpoint?, whatever>
3- /AddSpectate <savedloc> <angle in radian> <time in seconds>[Difficulity: Easy]

For: when player get in that pickup it make his able to spectate a special location  the prob.
Why?: as example i want when the player won a race as example his camera spectate the end of the race to see who or any place else
4- /PropAnn <style> <message>[Difficulity: Extreamly hard]
For sending ann for the property by Level 4, the game
Why? because of better attenntion
Note: for the tildes(~) although they are useful it can crash the players, you can add something that checks if the ~ is used good because its really usefull for coloring its really up to you.
5- Adding another argument for the command /AddMessageMickup <style(message/ann> <message>[Difficulity: Easy]
Why? because its usefull for races or if chat is flooded.
6- /PropBring <name> [Difficulity: Easy]
For: Bringing a player to the bringer by level4.
Why? usefull for setting non-event-staff based events
Note: Please dont add that gay "accept to bring"

------------------------------------------------------------
*1*: Im trying to make sort of transpiler in squriel that make people able to make their scripts in my lang that affects on props, my planned example if i got time:

Code:


OnPlayerDeath = AddMessage __PLAYERNAME__ "Died"


this for when player dies event it will send a property message as example with his name that he died. if i got time i may implement that in squrriel.

I like how you define the difficulty.

I've already pretty much made it like the properties are their own game mode with the property stats system. Not much more I can do, I think you guys can pretty much do anything.

Right now I've focused a lot on properties so I am not going to make that many more features for the next patch at all. As I've mentioned in the past we have 6-8 different huge systems and I can't focus on them all at the same time. This last patch I added some minigames (after not adding any for several patches), I made a huge update to the property system and more. So don't expect too many more property scripts for a while except small commands.

1. Don't really understand the logic here. You want to prevent people in your property from talking? There are still other people in other worlds that will be able to talk. I am not sure about if I like this suggestion.


1.2. propban. You numbered them wrong btw. Definitely something that I want to add. It won't be database based though, it will probably be an array stored on the normal server until the server closes.

2. I don't understand this one.

3. The camera is something I've been thinking of for a very long time. It's on my suggestion list from before. The only minor problem I have right now, how to exit the camera mode and not trigger the pickup again? Any ideas would be great. Kinda hard to say.

4. I am pretty sure that symbol doesn't crash people anymore, I've tried it and can't seem to trigger it no more.
Propanns? Maybe, but I feel like the people who needs anns are people hosting events = event staff members mainly. There is an eventann for that

5. Explain more please?

6. Same as 4, these commands are useful for events and that's why you should join the event staff if you want access to them.


Overall I'll probably add the camera and propban command at some point. Maybe soon.

About the GUI, eventually I'll probably do that if we last long enough. Got the 500 VK token (secret of VKs), another job coming up hopefully next patch. I'll also finish my final version of the rel006 script hopefully. I've been kinda holding off on the rel006 version due to mostly bugs that the developers don't fix. I've reported a few in PMs and in topics, but nothing seemed to have happened.

i listed the diffculty according to you as being a vcmp scripter.

1- not talking i mean they can as example send a pm or something else but i dont want any another world messages to be sent to the prop its up to the prop owner, as example when giving some instructions in race that you need to read it fast but someone is sending a CD in another world will mak ehim have to TAB to check messages and that is annoying
1/2- that is cool no need for a database indexing.
2- you InPoly vcmp's function?, something like this bujt for props but in squares because as you know we are neeps in math xd, but it have some events i mean when someone goes in this poly something happens.
3- thats why i suggested "time"
4- forget admins and eventstaff, look at me as being a neither of them. i feel limited its for poperty settings, and who doesnt like that he can leave my prop.
5- another argument(parameter) that prop editor can use to make wheather of this pickup gonna print a message or announce it.
6- i dont want to be an event staff, im busy as F*ck lol, but i may do some events in my prop/gamemodes also as i mentioned in 4 please, try to give more stuff for property owners it doesnt really effect on any one.
About GUIs: i never made a gui in vcmp but although its looks shit because of MGUI(no offense Juppi) to support DirectX8 it gonna help us in properties setting so put that in mind.

Roycewicz wrote:You better like forget about those things and focus on rel006.

According to Angel rel006 is finished the gui stuff and others, release? idk

+1.

#SPAMZ0R

its nice +1 for all