Re: [hlcoders] MenuSelect
Its so good to know that Valve cares so much about its customers.. Ive never seen any warning about using a documented SDK user message. From Alfred Reynolds: They are using an undocumented hack to display those menus, this update removes the hack and so they can no longer use it (because the last subsystem that was using it, radio menus, has finally been fixed to be client side). They have a plugin API to display messages to users and get feedback, they should use that. - Alfred They were warned multiple times to not use the hacks they were, so it is upon their own heads. - Alfred ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] MenuSelect
I'd have to agree that this was kind of dumb. We wouldn't be forced to use hacks to display a menu if we were provided with a proper ingame menu as opposed to the crap that Valve handed us. If Valve tried to make even one useful server plugin they would be unsuccessful in doing so without using any hacks. It is obvious to me that the server plugin interface is just to appease the coders so that they can't say Valve doesn't care about server-side plugins, which obviously they don't. - Original Message - From: Ray [EMAIL PROTECTED] To: hlcoders@list.valvesoftware.com Sent: Friday, May 20, 2005 3:24 AM Subject: Re: [hlcoders] MenuSelect Its so good to know that Valve cares so much about its customers.. Ive never seen any warning about using a documented SDK user message. From Alfred Reynolds: They are using an undocumented hack to display those menus, this update removes the hack and so they can no longer use it (because the last subsystem that was using it, radio menus, has finally been fixed to be client side). They have a plugin API to display messages to users and get feedback, they should use that. - Alfred They were warned multiple times to not use the hacks they were, so it is upon their own heads. - Alfred ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] MenuSelect
I have to agree that this is a really strange and frustrating approach to take on Valve's part. I'm more disappointed in Valve that there was zero forewarning before they wished to push such a big change onto everyone in the middle of the night. I'm going to start another thread on this topic. -Mattie - Original Message - From: Ray [EMAIL PROTECTED] To: hlcoders@list.valvesoftware.com Sent: Friday, May 20, 2005 6:24 AM Subject: Re: [hlcoders] MenuSelect Its so good to know that Valve cares so much about its customers.. Ive never seen any warning about using a documented SDK user message. From Alfred Reynolds: They are using an undocumented hack to display those menus, this update removes the hack and so they can no longer use it (because the last subsystem that was using it, radio menus, has finally been fixed to be client side). They have a plugin API to display messages to users and get feedback, they should use that. - Alfred They were warned multiple times to not use the hacks they were, so it is upon their own heads. - Alfred ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] MenuSelect
I too am highly disappointed in valve.. Ive spent months of time and many ,many hours trying to make admining our servers an easy thing to do, and making the menus were more for peoples requests to do so, than anything else. The provided api for everything is less than adequate on all accounts. Valve, Alfred, you would Like to know what things are needed? In game menus, not having to hit esq and block my view of the person im about to kick or ban. Leave the menus in ...and allow them to be selectable as to what the command they send on selection the way the esc menus do. The reason the menus are being taken out..is because of the Source TV proxy problem that sending the create menu messages to srctv caused.. Valve had to spend time troubleshooting that..and now the price for there time is to disable something they do not document..other than the 2 dozen source files in the sdk that shows there use. The correct solution is to have the srctv ignore user messages that it doesnt need. (as well as us developers taking the time to not send user messages to bots or hltv) Please provide the radio command menu as is or with programmer selectable commands the same way the esc menus use..Some times being able to hit the menu choices requires quick action... Shutting them down will break everyone's plugin and make it so that administering our servers is a difficult task again. The effects interface seems pretty much an afterthought. Ok for sparks and smoke ..useless for much more, how about bloodstreams and flames and who knows what else. Add Access to the users money via IPlayerInfo. Ray At 12:12 PM 05/20/2005, you wrote: I have to agree that this is a really strange and frustrating approach to take on Valve's part. I'm more disappointed in Valve that there was zero forewarning before they wished to push such a big change onto everyone in the middle of the night. I'm going to start another thread on this topic. -Mattie - Original Message - From: Ray [EMAIL PROTECTED] To: hlcoders@list.valvesoftware.com Sent: Friday, May 20, 2005 6:24 AM Subject: Re: [hlcoders] MenuSelect Its so good to know that Valve cares so much about its customers.. Ive never seen any warning about using a documented SDK user message. From Alfred Reynolds: They are using an undocumented hack to display those menus, this update removes the hack and so they can no longer use it (because the last subsystem that was using it, radio menus, has finally been fixed to be client side). They have a plugin API to display messages to users and get feedback, they should use that. - Alfred They were warned multiple times to not use the hacks they were, so it is upon their own heads. - Alfred ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] MenuSelect
Add Access to the users money via IPlayerInfo. It's a generic interface meant to be mod-independant. You would have to be able to derive a special CCSPlayerInfo from it. Same with CS 1.6, you couldn't just get money from the entvars, you had to find the offset from the CBaseEntity base in pvPrivateData (omg hax!)... this is reasonable, since Valve has no reason to abstract that sort of thing. ~dvander Ray wrote: I too am highly disappointed in valve.. Ive spent months of time and many ,many hours trying to make admining our servers an easy thing to do, and making the menus were more for peoples requests to do so, than anything else. The provided api for everything is less than adequate on all accounts. Valve, Alfred, you would Like to know what things are needed? In game menus, not having to hit esq and block my view of the person im about to kick or ban. Leave the menus in ...and allow them to be selectable as to what the command they send on selection the way the esc menus do. The reason the menus are being taken out..is because of the Source TV proxy problem that sending the create menu messages to srctv caused.. Valve had to spend time troubleshooting that..and now the price for there time is to disable something they do not document..other than the 2 dozen source files in the sdk that shows there use. The correct solution is to have the srctv ignore user messages that it doesnt need. (as well as us developers taking the time to not send user messages to bots or hltv) Please provide the radio command menu as is or with programmer selectable commands the same way the esc menus use..Some times being able to hit the menu choices requires quick action... Shutting them down will break everyone's plugin and make it so that administering our servers is a difficult task again. The effects interface seems pretty much an afterthought. Ok for sparks and smoke ..useless for much more, how about bloodstreams and flames and who knows what else. Add Access to the users money via IPlayerInfo. Ray At 12:12 PM 05/20/2005, you wrote: I have to agree that this is a really strange and frustrating approach to take on Valve's part. I'm more disappointed in Valve that there was zero forewarning before they wished to push such a big change onto everyone in the middle of the night. I'm going to start another thread on this topic. -Mattie - Original Message - From: Ray [EMAIL PROTECTED] To: hlcoders@list.valvesoftware.com Sent: Friday, May 20, 2005 6:24 AM Subject: Re: [hlcoders] MenuSelect Its so good to know that Valve cares so much about its customers.. Ive never seen any warning about using a documented SDK user message. From Alfred Reynolds: They are using an undocumented hack to display those menus, this update removes the hack and so they can no longer use it (because the last subsystem that was using it, radio menus, has finally been fixed to be client side). They have a plugin API to display messages to users and get feedback, they should use that. - Alfred They were warned multiple times to not use the hacks they were, so it is upon their own heads. - Alfred ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] MenuSelect
I agree wholeheartedly. Even though I'm against this whole update deprecating Menuselect code, I feel that it is a wholly different situation than something like adding access to money values, as the menuselect code is easily mod-independant. There would be no issues with such a proper menu from working in any of the Source mods, which is why I have a problem with the fact that a hack is even necessary for such a menu. If Valve wants us to stop using hacks in our code, why not give us something proper to use instead that suits our needs? - Original Message - From: David Anderson [EMAIL PROTECTED] To: hlcoders@list.valvesoftware.com Sent: Friday, May 20, 2005 5:12 PM Subject: Re: [hlcoders] MenuSelect Add Access to the users money via IPlayerInfo. It's a generic interface meant to be mod-independant. You would have to be able to derive a special CCSPlayerInfo from it. Same with CS 1.6, you couldn't just get money from the entvars, you had to find the offset from the CBaseEntity base in pvPrivateData (omg hax!)... this is reasonable, since Valve has no reason to abstract that sort of thing. ~dvander Ray wrote: I too am highly disappointed in valve.. Ive spent months of time and many ,many hours trying to make admining our servers an easy thing to do, and making the menus were more for peoples requests to do so, than anything else. The provided api for everything is less than adequate on all accounts. Valve, Alfred, you would Like to know what things are needed? In game menus, not having to hit esq and block my view of the person im about to kick or ban. Leave the menus in ...and allow them to be selectable as to what the command they send on selection the way the esc menus do. The reason the menus are being taken out..is because of the Source TV proxy problem that sending the create menu messages to srctv caused.. Valve had to spend time troubleshooting that..and now the price for there time is to disable something they do not document..other than the 2 dozen source files in the sdk that shows there use. The correct solution is to have the srctv ignore user messages that it doesnt need. (as well as us developers taking the time to not send user messages to bots or hltv) Please provide the radio command menu as is or with programmer selectable commands the same way the esc menus use..Some times being able to hit the menu choices requires quick action... Shutting them down will break everyone's plugin and make it so that administering our servers is a difficult task again. The effects interface seems pretty much an afterthought. Ok for sparks and smoke ..useless for much more, how about bloodstreams and flames and who knows what else. Add Access to the users money via IPlayerInfo. Ray At 12:12 PM 05/20/2005, you wrote: I have to agree that this is a really strange and frustrating approach to take on Valve's part. I'm more disappointed in Valve that there was zero forewarning before they wished to push such a big change onto everyone in the middle of the night. I'm going to start another thread on this topic. -Mattie - Original Message - From: Ray [EMAIL PROTECTED] To: hlcoders@list.valvesoftware.com Sent: Friday, May 20, 2005 6:24 AM Subject: Re: [hlcoders] MenuSelect Its so good to know that Valve cares so much about its customers.. Ive never seen any warning about using a documented SDK user message. From Alfred Reynolds: They are using an undocumented hack to display those menus, this update removes the hack and so they can no longer use it (because the last subsystem that was using it, radio menus, has finally been fixed to be client side). They have a plugin API to display messages to users and get feedback, they should use that. - Alfred They were warned multiple times to not use the hacks they were, so it is upon their own heads. - Alfred ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http
RE: [hlcoders] MenuSelect
There is an existing Menu interface as part of the plugin API, you should use that. - Alfred Original Message From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Jennings Sent: Friday, May 20, 2005 5:41 PM To: hlcoders@list.valvesoftware.com Subject: Re: [hlcoders] MenuSelect I agree wholeheartedly. Even though I'm against this whole update deprecating Menuselect code, I feel that it is a wholly different situation than something like adding access to money values, as the menuselect code is easily mod-independant. There would be no issues with such a proper menu from working in any of the Source mods, which is why I have a problem with the fact that a hack is even necessary for such a menu. If Valve wants us to stop using hacks in our code, why not give us something proper to use instead that suits our needs? - Original Message - From: David Anderson [EMAIL PROTECTED] To: hlcoders@list.valvesoftware.com Sent: Friday, May 20, 2005 5:12 PM Subject: Re: [hlcoders] MenuSelect Add Access to the users money via IPlayerInfo. It's a generic interface meant to be mod-independant. You would have to be able to derive a special CCSPlayerInfo from it. Same with CS 1.6, you couldn't just get money from the entvars, you had to find the offset from the CBaseEntity base in pvPrivateData (omg hax!)... this is reasonable, since Valve has no reason to abstract that sort of thing. ~dvander Ray wrote: I too am highly disappointed in valve.. Ive spent months of time and many ,many hours trying to make admining our servers an easy thing to do, and making the menus were more for peoples requests to do so, than anything else. The provided api for everything is less than adequate on all accounts. Valve, Alfred, you would Like to know what things are needed? In game menus, not having to hit esq and block my view of the person im about to kick or ban. Leave the menus in ...and allow them to be selectable as to what the command they send on selection the way the esc menus do. The reason the menus are being taken out..is because of the Source TV proxy problem that sending the create menu messages to srctv caused.. Valve had to spend time troubleshooting that..and now the price for there time is to disable something they do not document..other than the 2 dozen source files in the sdk that shows there use. The correct solution is to have the srctv ignore user messages that it doesnt need. (as well as us developers taking the time to not send user messages to bots or hltv) Please provide the radio command menu as is or with programmer selectable commands the same way the esc menus use..Some times being able to hit the menu choices requires quick action... Shutting them down will break everyone's plugin and make it so that administering our servers is a difficult task again. The effects interface seems pretty much an afterthought. Ok for sparks and smoke ..useless for much more, how about bloodstreams and flames and who knows what else. Add Access to the users money via IPlayerInfo. Ray At 12:12 PM 05/20/2005, you wrote: I have to agree that this is a really strange and frustrating approach to take on Valve's part. I'm more disappointed in Valve that there was zero forewarning before they wished to push such a big change onto everyone in the middle of the night. I'm going to start another thread on this topic. -Mattie - Original Message - From: Ray [EMAIL PROTECTED] To: hlcoders@list.valvesoftware.com Sent: Friday, May 20, 2005 6:24 AM Subject: Re: [hlcoders] MenuSelect Its so good to know that Valve cares so much about its customers.. Ive never seen any warning about using a documented SDK user message. From Alfred Reynolds: They are using an undocumented hack to display those menus, this update removes the hack and so they can no longer use it (because the last subsystem that was using it, radio menus, has finally been fixed to be client side). They have a plugin API to display messages to users and get feedback, they should use that. - Alfred They were warned multiple times to not use the hacks they were, so it is upon their own heads. - Alfred ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] MenuSelect
I don't think anyone would have any problem using a Valve provided meny if it were possible it popped up (i.e. it didn't require the players to hit ESC). Is there any chance that Valve would consider adding that funcionality to the menu for use in such things as map votes? Thanks, Duke On 5/20/05, Alfred Reynolds [EMAIL PROTECTED] wrote: There is an existing Menu interface as part of the plugin API, you should use that. - Alfred ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
[hlcoders] MenuSelect
Now that you have made the Radio Command all client side ..there is no menuselect command set to the server when we use the Radio Commands menu for plugin menus.. All menus in plugins are now non functional... the the hit esc to use menu's are worthless... Is there any way we can get a message sent from client back to the server when a menu item is selected when the menus are not used for Radio commands? 6 months of work down the drain ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
