[hlcoders] HUD element with .res files
--
[ Picked text/plain from multipart/alternative ]
Hi,
I'm trying to work on a HUD element that catches different events and displays
a message for each event. My inspiration on how to accomplish this nicely came
from taking a look at the notification res files for TF2. I have my HUD
element inheriting from EditablePanel instead of Panel so I can load the
control settings. I have also created a base_message.res and then some
message_blah.res files. One example is:
#base "base_message.res"
"Resource/UI/messages/message_scientist_captured.res"
{
"Message_Label"
{
"labelText""#SI2_Scientist_Captured"
}
}
However, when I try to load the files that aren't the base file, I always get
the error in the console:
KeyValues Error: LoadFromBuffer: missing { in file
Resource/UI/messages/message_scientist_captured.res
or similar depending on the file. I'm not really sure what's wrong because as
far as I can see, I'm not missing any {.
Any help would be appreciated.
Thanks,
Garrett
Got a little couch potato?
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
--
___
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] SDK Update heads up?
-- [ Picked text/plain from multipart/alternative ] Good to see you didn't get worked up about his response like a few other people here :) On 9/21/07, Keeper <[EMAIL PROTECTED]> wrote: > > Wow, don't check the mailing list for a day and look what > happens. ::sigh:: > > > Nick, man, you misunderstood my post. > > I was responding directly to Mike's post. Therefore my line about "I can > e-mail you offline." was directed at HIM ONLY. Sorry for the confusion. > > > 1. Has exploits. > "The reason I ask is there are several exploits that have never been > fixed, > as well as some netcode issues that I've seen." > I see players doing things all the time that they aren't supposed to be > able > to do. I have examples and descriptions. The netcode in HL2DM at least > has > been completely shotty at best lately. Plus Valve has put in time to fix > exploits both announced an unannounced since the last SDK release. Since > they are moving to a new engine with new interfaces I wanted to be sure > those were put into the new SDK package. If not, I was going to make sure > I > tried to tackle those that I knew about in our mod. > > As far as engine exploits, I wanted to make sure Valve knew about the ones > I've come across. Obviously I have no control over fixing these. > > 2. Knows how to use them. > Mostly, no. Know how to spot them ... yes. > > 3. Is willing to give them out via email. > Only to Valve. I have several e-mail contacts there, but with the orange > box work they are doing, I didn't want to send it to the wrong person and > hope that it got to the right place. > > 4. Refuses to help others to fix them. > Nope. I have constantly e-mailed valve about other problems and some have > been passed along and fixed. Unfortunately you can't just post about them > here or they probably would be used as you can google any message from > this > list at any time and usually get a link somewhere that has the > archive. Not > to mention those who only watch these lists for specific things they can > try. > > 5. Refuses to make fixes available to others. > See 4 > > 6 & 7. Dunno where those came from. > > Again from your response "I am guessing he is trying to sell the exploits > to > others on the list via email" I think you misunderstood my response to > Mike > as a general announcement. Again, sorry for the confusion. > > Keeper > > > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > -- Matt Stafford (Wraiyth) http://www.wraiyth.com NightFall HL2 Mod - http://www.nightfallmod.com -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
RE: [hlcoders] SDK Update heads up?
Wow, don't check the mailing list for a day and look what happens. ::sigh:: Nick, man, you misunderstood my post. I was responding directly to Mike's post. Therefore my line about "I can e-mail you offline." was directed at HIM ONLY. Sorry for the confusion. 1. Has exploits. "The reason I ask is there are several exploits that have never been fixed, as well as some netcode issues that I've seen." I see players doing things all the time that they aren't supposed to be able to do. I have examples and descriptions. The netcode in HL2DM at least has been completely shotty at best lately. Plus Valve has put in time to fix exploits both announced an unannounced since the last SDK release. Since they are moving to a new engine with new interfaces I wanted to be sure those were put into the new SDK package. If not, I was going to make sure I tried to tackle those that I knew about in our mod. As far as engine exploits, I wanted to make sure Valve knew about the ones I've come across. Obviously I have no control over fixing these. 2. Knows how to use them. Mostly, no. Know how to spot them ... yes. 3. Is willing to give them out via email. Only to Valve. I have several e-mail contacts there, but with the orange box work they are doing, I didn't want to send it to the wrong person and hope that it got to the right place. 4. Refuses to help others to fix them. Nope. I have constantly e-mailed valve about other problems and some have been passed along and fixed. Unfortunately you can't just post about them here or they probably would be used as you can google any message from this list at any time and usually get a link somewhere that has the archive. Not to mention those who only watch these lists for specific things they can try. 5. Refuses to make fixes available to others. See 4 6 & 7. Dunno where those came from. Again from your response "I am guessing he is trying to sell the exploits to others on the list via email" I think you misunderstood my response to Mike as a general announcement. Again, sorry for the confusion. Keeper ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] SDK Update heads up?
This is really getting on my fucking nerves. I know no good deed goes unpunished but damn, this is insane. Keeper, exploit all you want, I do not care any more. Have fun. On 9/20/07, Greg Scott <[EMAIL PROTECTED]> wrote: > -- > [ Picked text/plain from multipart/alternative ] > Guys, as was said, Please keep the arguing about exploits/who is an > exploiter/what have you off the email list. We don't need our inboxes > filled with a 40 email long argument. Email each other personally or take > it to a forum somewhere please. > > - Khaim - Lunar Wind - > > On 9/20/07, Skyler York <[EMAIL PROTECTED]> wrote: > > > > This is getting quite ridiculous. > > > > 1) Finding an exploit does not make you an exploiter (i.e. someone who > > *actively* uses the exploit to achieve an unfair advantage over other > > players). Where did that logic come from? And if anything, as a > > developer I would be *overjoyed* if people spent time finding exploits > > and telling me about them. > > > > 2) Keeper said he was going to help out any way he could. Just because > > he didn't explicitly say that he's sending a full report to Valve right > > at this moment does not mean that he hasn't or won't. Now if he didn't > > or won't (and that's an *if*), then it would be shame on him. But we > > don't know that do we? > > > > 3) He definitely should not post any information about the exploits > > here. This Utopian notion that everyone reading the list has only the > > best of intentions at heart is utterly naive. If I was a hacker this > > would be the first mailing list I joined since specifics of inner > > workings of the game and engine are discussed on a regular basis. Any > > details should be kept confidential and sent directly to Valve. > > > > 4) I'm not a huge fan of people calling each other morons or other > > names even when they do behave a little out of line > > (*cough*botman*cough*) since that's just asking for things to spiral > > into a flame battle and doesn't help the situation at all. However with > > you (Nick) posting such blatant misinformation and slander I can't say I > > didn't see it coming. > > > > Fin. > > > > - Zipster > > > > Nick wrote: > > > > >I don't know what you have to gain from defending an exploiter, but it > > >really isn't my place to judge. I don't know if you and Keeper are > > >friends or working together, but please don't turn this around and > > >start attacking me for no reason. Exploits should be given to Valve, > > >so Valve can fix them and help everyone out. > > > > > >On 9/20/07, Jeremy <[EMAIL PROTECTED]> wrote: > > > > > > > > >>-- > > >>[ Picked text/plain from multipart/alternative ] > > >>How do you know he hasn't already sent the information to Valve? Those > > sort > > >>of exchanges wouldn't be advertised to the mailing list. Your statements > > >>were out of line and just plain wrong. It's poor taste to spout blatant > > BS > > >>too, which is why you got called on it. > > >> > > >>J > > >> > > >>On 9/20/07, Nick <[EMAIL PROTECTED]> wrote: > > >> > > >> > > To Valve. He's willing to email them privately to Valve, which is > > what > > everyone SHOULD do if they are aware of exploits > > > > > > >>>I don't know why he hasn't done this yet. > > >>> > > >>> > > >>> > > You, sir, are a moron and really aren't worth the time it took me to > > compose this email. > > > > > > >>>If I had exploits, the first thing I would do would be to email Valve > > >>>and give them all of the help I could in reproducing and fixing them. > > >>>I wouldn't post on this mailing list about the numerous exploits I > > >>>found, and refuse to offer assistance in fixing them(like keeper did). > > >>>Personally, I find it very poor taste to call others names, especially > > >>>when you are the one mistaken here, not me. I could say that your IQ > > >>>is similar to your age, but I am not rude like that, and it would > > >>>probably take you a few minutes to fully understand anyway. > > >>> > > >>>___ > > >>>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] SDK Update heads up?
-- [ Picked text/plain from multipart/alternative ] Guys, as was said, Please keep the arguing about exploits/who is an exploiter/what have you off the email list. We don't need our inboxes filled with a 40 email long argument. Email each other personally or take it to a forum somewhere please. - Khaim - Lunar Wind - On 9/20/07, Skyler York <[EMAIL PROTECTED]> wrote: > > This is getting quite ridiculous. > > 1) Finding an exploit does not make you an exploiter (i.e. someone who > *actively* uses the exploit to achieve an unfair advantage over other > players). Where did that logic come from? And if anything, as a > developer I would be *overjoyed* if people spent time finding exploits > and telling me about them. > > 2) Keeper said he was going to help out any way he could. Just because > he didn't explicitly say that he's sending a full report to Valve right > at this moment does not mean that he hasn't or won't. Now if he didn't > or won't (and that's an *if*), then it would be shame on him. But we > don't know that do we? > > 3) He definitely should not post any information about the exploits > here. This Utopian notion that everyone reading the list has only the > best of intentions at heart is utterly naive. If I was a hacker this > would be the first mailing list I joined since specifics of inner > workings of the game and engine are discussed on a regular basis. Any > details should be kept confidential and sent directly to Valve. > > 4) I'm not a huge fan of people calling each other morons or other > names even when they do behave a little out of line > (*cough*botman*cough*) since that's just asking for things to spiral > into a flame battle and doesn't help the situation at all. However with > you (Nick) posting such blatant misinformation and slander I can't say I > didn't see it coming. > > Fin. > > - Zipster > > Nick wrote: > > >I don't know what you have to gain from defending an exploiter, but it > >really isn't my place to judge. I don't know if you and Keeper are > >friends or working together, but please don't turn this around and > >start attacking me for no reason. Exploits should be given to Valve, > >so Valve can fix them and help everyone out. > > > >On 9/20/07, Jeremy <[EMAIL PROTECTED]> wrote: > > > > > >>-- > >>[ Picked text/plain from multipart/alternative ] > >>How do you know he hasn't already sent the information to Valve? Those > sort > >>of exchanges wouldn't be advertised to the mailing list. Your statements > >>were out of line and just plain wrong. It's poor taste to spout blatant > BS > >>too, which is why you got called on it. > >> > >>J > >> > >>On 9/20/07, Nick <[EMAIL PROTECTED]> wrote: > >> > >> > To Valve. He's willing to email them privately to Valve, which is > what > everyone SHOULD do if they are aware of exploits > > > >>>I don't know why he hasn't done this yet. > >>> > >>> > >>> > You, sir, are a moron and really aren't worth the time it took me to > compose this email. > > > >>>If I had exploits, the first thing I would do would be to email Valve > >>>and give them all of the help I could in reproducing and fixing them. > >>>I wouldn't post on this mailing list about the numerous exploits I > >>>found, and refuse to offer assistance in fixing them(like keeper did). > >>>Personally, I find it very poor taste to call others names, especially > >>>when you are the one mistaken here, not me. I could say that your IQ > >>>is similar to your age, but I am not rude like that, and it would > >>>probably take you a few minutes to fully understand anyway. > >>> > >>>___ > >>>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://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] SDK Update heads up?
This is getting quite ridiculous. 1) Finding an exploit does not make you an exploiter (i.e. someone who *actively* uses the exploit to achieve an unfair advantage over other players). Where did that logic come from? And if anything, as a developer I would be *overjoyed* if people spent time finding exploits and telling me about them. 2) Keeper said he was going to help out any way he could. Just because he didn't explicitly say that he's sending a full report to Valve right at this moment does not mean that he hasn't or won't. Now if he didn't or won't (and that's an *if*), then it would be shame on him. But we don't know that do we? 3) He definitely should not post any information about the exploits here. This Utopian notion that everyone reading the list has only the best of intentions at heart is utterly naive. If I was a hacker this would be the first mailing list I joined since specifics of inner workings of the game and engine are discussed on a regular basis. Any details should be kept confidential and sent directly to Valve. 4) I'm not a huge fan of people calling each other morons or other names even when they do behave a little out of line (*cough*botman*cough*) since that's just asking for things to spiral into a flame battle and doesn't help the situation at all. However with you (Nick) posting such blatant misinformation and slander I can't say I didn't see it coming. Fin. - Zipster Nick wrote: I don't know what you have to gain from defending an exploiter, but it really isn't my place to judge. I don't know if you and Keeper are friends or working together, but please don't turn this around and start attacking me for no reason. Exploits should be given to Valve, so Valve can fix them and help everyone out. On 9/20/07, Jeremy <[EMAIL PROTECTED]> wrote: -- [ Picked text/plain from multipart/alternative ] How do you know he hasn't already sent the information to Valve? Those sort of exchanges wouldn't be advertised to the mailing list. Your statements were out of line and just plain wrong. It's poor taste to spout blatant BS too, which is why you got called on it. J On 9/20/07, Nick <[EMAIL PROTECTED]> wrote: To Valve. He's willing to email them privately to Valve, which is what everyone SHOULD do if they are aware of exploits I don't know why he hasn't done this yet. You, sir, are a moron and really aren't worth the time it took me to compose this email. If I had exploits, the first thing I would do would be to email Valve and give them all of the help I could in reproducing and fixing them. I wouldn't post on this mailing list about the numerous exploits I found, and refuse to offer assistance in fixing them(like keeper did). Personally, I find it very poor taste to call others names, especially when you are the one mistaken here, not me. I could say that your IQ is similar to your age, but I am not rude like that, and it would probably take you a few minutes to fully understand anyway. ___ 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] SDK Update heads up?
-- [ Picked text/plain from multipart/alternative ] Seriously, how do you know that he is an exploiter, and NOT contacting them? Please, just give it a rest. On 9/20/07, Nick <[EMAIL PROTECTED]> wrote: > > I don't know what you have to gain from defending an exploiter, but it > really isn't my place to judge. I don't know if you and Keeper are > friends or working together, but please don't turn this around and > start attacking me for no reason. Exploits should be given to Valve, > so Valve can fix them and help everyone out. > > -- ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] SDK Update heads up?
Sh! Guys, if you want to bash each other the head with email nurf, do it off list. Adam --- Nick <[EMAIL PROTECTED]> wrote: > I don't know what you have to gain from defending an > exploiter, but it > really isn't my place to judge. I don't know if you > and Keeper are > friends or working together, but please don't turn > this around and > start attacking me for no reason. Exploits should be > given to Valve, > so Valve can fix them and help everyone out. > > On 9/20/07, Jeremy <[EMAIL PROTECTED]> wrote: > > -- > > [ Picked text/plain from multipart/alternative ] > > How do you know he hasn't already sent the > information to Valve? Those sort > > of exchanges wouldn't be advertised to the mailing > list. Your statements > > were out of line and just plain wrong. It's poor > taste to spout blatant BS > > too, which is why you got called on it. > > > > J > > > > On 9/20/07, Nick <[EMAIL PROTECTED]> wrote: > > > > > > > To Valve. He's willing to email them > privately to Valve, which is what > > > > everyone SHOULD do if they are aware of > exploits > > > > > > I don't know why he hasn't done this yet. > > > > > > >You, sir, are a moron and really aren't worth > the time it took me to > > > >compose this email. > > > > > > If I had exploits, the first thing I would do > would be to email Valve > > > and give them all of the help I could in > reproducing and fixing them. > > > I wouldn't post on this mailing list about the > numerous exploits I > > > found, and refuse to offer assistance in fixing > them(like keeper did). > > > Personally, I find it very poor taste to call > others names, especially > > > when you are the one mistaken here, not me. I > could say that your IQ > > > is similar to your age, but I am not rude like > that, and it would > > > probably take you a few minutes to fully > understand anyway. > > > > > > ___ > > > 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 > > Owner Nigredo Studios http://www.nigredostudios.com Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, and more! http://tv.yahoo.com/collections/3658 ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] SDK Update heads up?
I don't know what you have to gain from defending an exploiter, but it really isn't my place to judge. I don't know if you and Keeper are friends or working together, but please don't turn this around and start attacking me for no reason. Exploits should be given to Valve, so Valve can fix them and help everyone out. On 9/20/07, Jeremy <[EMAIL PROTECTED]> wrote: > -- > [ Picked text/plain from multipart/alternative ] > How do you know he hasn't already sent the information to Valve? Those sort > of exchanges wouldn't be advertised to the mailing list. Your statements > were out of line and just plain wrong. It's poor taste to spout blatant BS > too, which is why you got called on it. > > J > > On 9/20/07, Nick <[EMAIL PROTECTED]> wrote: > > > > > To Valve. He's willing to email them privately to Valve, which is what > > > everyone SHOULD do if they are aware of exploits > > > > I don't know why he hasn't done this yet. > > > > >You, sir, are a moron and really aren't worth the time it took me to > > >compose this email. > > > > If I had exploits, the first thing I would do would be to email Valve > > and give them all of the help I could in reproducing and fixing them. > > I wouldn't post on this mailing list about the numerous exploits I > > found, and refuse to offer assistance in fixing them(like keeper did). > > Personally, I find it very poor taste to call others names, especially > > when you are the one mistaken here, not me. I could say that your IQ > > is similar to your age, but I am not rude like that, and it would > > probably take you a few minutes to fully understand anyway. > > > > ___ > > 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] SDK Update heads up?
-- [ Picked text/plain from multipart/alternative ] How do you know he hasn't already sent the information to Valve? Those sort of exchanges wouldn't be advertised to the mailing list. Your statements were out of line and just plain wrong. It's poor taste to spout blatant BS too, which is why you got called on it. J On 9/20/07, Nick <[EMAIL PROTECTED]> wrote: > > > To Valve. He's willing to email them privately to Valve, which is what > > everyone SHOULD do if they are aware of exploits > > I don't know why he hasn't done this yet. > > >You, sir, are a moron and really aren't worth the time it took me to > >compose this email. > > If I had exploits, the first thing I would do would be to email Valve > and give them all of the help I could in reproducing and fixing them. > I wouldn't post on this mailing list about the numerous exploits I > found, and refuse to offer assistance in fixing them(like keeper did). > Personally, I find it very poor taste to call others names, especially > when you are the one mistaken here, not me. I could say that your IQ > is similar to your age, but I am not rude like that, and it would > probably take you a few minutes to fully understand anyway. > > ___ > 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] SDK Update heads up?
> To Valve. He's willing to email them privately to Valve, which is what > everyone SHOULD do if they are aware of exploits I don't know why he hasn't done this yet. >You, sir, are a moron and really aren't worth the time it took me to >compose this email. If I had exploits, the first thing I would do would be to email Valve and give them all of the help I could in reproducing and fixing them. I wouldn't post on this mailing list about the numerous exploits I found, and refuse to offer assistance in fixing them(like keeper did). Personally, I find it very poor taste to call others names, especially when you are the one mistaken here, not me. I could say that your IQ is similar to your age, but I am not rude like that, and it would probably take you a few minutes to fully understand anyway. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] SDK Update heads up?
On Thursday 20 September 2007, Nick wrote: > The only things I have seen is that Keeper: > > 1. Has exploits. > 2. Knows how to use them. > 3. Is willing to give them out via email. > 4. Refuses to help others to fix them. > 5. Refuses to make fixes available to others. > 6. Refuses to give them to Valve. > 7. Refuses to let others try fixing them. > > All I can say, is wow. I am guessing he is trying to sell the exploits > to others on the list via email, because from what I have seen he > wants nothing to do with fixing them, or even letting others fix them. > Very bad. The only things I have seen is that Keeper: 1. Has exploits. 2. Knows how to use them 3. Is willing to give them out via email. He's trying to keep these from general circulation. That's good. Now, I have no clue where you are pulling items 4-7 from. He cannot help others or fix them himself, because they are *engine issues* (or so he says). And where the fuck does the "refuses to give them to Valve" line come in? -John Sheu ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] SDK Update heads up?
Nick wrote: The only things I have seen is that Keeper: 1. Has exploits. 2. Knows how to use them. Knowing about them doesn't necessarily mean that you know how to reproduce them. 3. Is willing to give them out via email. To Valve. He's willing to email them privately to Valve, which is what everyone SHOULD do if they are aware of exploits and don't wish to spread that knowledge around so that anyone lurking on an email list can take advantage of them. 4. Refuses to help others to fix them. 5. Refuses to make fixes available to others. If he can't fix them, how can he make those fixes available to others? 6. Refuses to give them to Valve. That's completely the opposite of what the email said... "If you need examples of exploits, I can e-mail you offline." 7. Refuses to let others try fixing them. All I can say, is wow. I am guessing he is trying to sell the exploits to others on the list via email, because from what I have seen he wants nothing to do with fixing them, or even letting others fix them. Very bad. You, sir, are a moron and really aren't worth the time it took me to compose this email. -- Jeffrey "botman" Broome ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] SDK Update heads up?
The only things I have seen is that Keeper: 1. Has exploits. 2. Knows how to use them. 3. Is willing to give them out via email. 4. Refuses to help others to fix them. 5. Refuses to make fixes available to others. 6. Refuses to give them to Valve. 7. Refuses to let others try fixing them. All I can say, is wow. I am guessing he is trying to sell the exploits to others on the list via email, because from what I have seen he wants nothing to do with fixing them, or even letting others fix them. Very bad. On 9/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Keeper apparently refers to exploits in the *engine*. He is a modder > himself, so let's not insult his intelligence or good will and assume > that, had it been possible to fix these exploits in the SDK code, he would > have shared the fixes with us. Hence, it is not, and since we cannot fix > them anyway he's right not to publish them. > > > Well, I though we are all mature here and in the end we are the coders who > > should be fixing, not breaking, right?:P > > > >> Agreed; please don't post details--it only encourages abuse. > >> > >> -Original Message- > >> From: [EMAIL PROTECTED] > >> [mailto:[EMAIL PROTECTED] On Behalf Of Keeper > >> Sent: Wednesday, September 19, 2007 7:29 PM > >> To: hlcoders@list.valvesoftware.com > >> Subject: RE: [hlcoders] SDK Update heads up? > >> > >> Because I don't ever publicly post exploits. Pure and simple. > >> > >> Keeper > >> > >> -Original Message- > >> From: Nick > >> Sent: Wednesday, September 19, 2007 6:40 PM > >> Subject: Re: [hlcoders] SDK Update heads up? > >> > >> It might be helpful to share some of the things here, maybe people > >> already made fixes for them. Or they might not be problems after all. > >> What is the point of having a mailing list if you don't want to share > >> problems on it? > >>> > >>> If the orange box engine means a fix to some of these exploits, then an > >>> overhaul to some of our mod coding to fit the new SDK release might > >>> just > >> be > >>> worth it. If you need examples of exploits, I can e-mail you offline. > >>> > >>> Keeper > > > > ___ > > 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] RE: RE: AI in multiplayer
It looks like the combine soldier is trying to run TASK_GET_PATH_TO_ENEMY_LKP, which generates a path to the enemy's last known position. This task is failing, however, because it cant build a route to that position, which sets the COND_ENEMY_UNREACHABLE condition, causing the TASK_GET_PATH_TO_ENEMY_LKP to fail. Assuming that, in the game, it looks like the soldier should be able to find a path to the enemy's LKP, then you probably want to debug why that path generation is failing. A good starting point on the wiki is http://developer.valvesoftware.com/wiki/Ai_show_connect Robin. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Donovan Sent: Thursday, September 20, 2007 3:23 AM To: hlcoders@list.valvesoftware.com Subject: [hlcoders] RE: RE: AI in multiplayer -- [ Picked text/plain from multipart/alternative ] Im sorry to keep hounding about this question..you all probably know what its like to stare into a pile of code and get a bit lost...thats where I am and Im desperately trying to find out the bits I am missing. I am thinking it has something to do with the the way the AI is setting up its Schedule or Task state and not that its an animation problem directly. Below is a snippet of condump that lists whats happening in the process. I am now trying to figure out why it is that the AI for combine_s is having problems with the way this is defining the Schedule state... I cant seem to pick where its going wrong..Any help welcome. Look @ the condum below operator_handleanimevent --This is the Animation state of the combine_s while I am hidden behind a breakable model. Also I have a few of the following errors and was wondering if any you coders out there might have dealt with these in setting up AI? Its a condition of some sort that not been met? maybe its my own player model? Maybe the activity is not set up right? I cant really see which area it might be. TaskFail -> Don't have a route (npc_combine_s: 47/soldier_1_1) [152683] Break condition -> COND_ENEMY_UNREACHABLE (npc_combine_s: 47/soldier_1_1) [152690](failed) (npc_combine_s: 47/soldier_1_1) [152690] Task: TASK_SET_FAIL_SCHEDULE (npc_combine_s: 47/soldier_1_1) [152683] * Schedule: SCHED_COMBINE_ESTABLISH_LINE_OF_FIRE (time: 2285.63) (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_SET_FAIL_SHEDULE (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_SET_TOLERANCE_DISTANCE (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_GET_PATH_TO_ENEMY_LKP_LOS (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_COMBINE_SET_STANDING (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_SPEAK_SENTENCE (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_RUN_PATH (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_WAIT_FOR_MOVEMENT (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_COMBINE_IGNOREATTACKS (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_SET_SCHEDULE (npc_combine_s: 47/soldier_1_1) [152452] Schedule: SCHED_COMBAT_FACE (time: 2286.78) (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_STOP_MOVING (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_SET_ACTIVITY (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_FACE_ENEMY (npc_combine_s: 47/soldier_1_1) [152452] Schedule: SCHED_SHOOT_ENEMY_COVER (time: 2286.78) (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_STOP_MOVNG (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_FACE_ENEMY (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_WAIT (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_RANGE_ATTACK1 (npc_combine_s: 47/soldier_1_1) [152487] operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1Schedule: SCHED_SHOOT_ENEMY_COVER (time: 2287.51) (npc_combine_s: 47/soldier_1_1) [152501] Task: TASK_STOP_MOVING (npc_combine_s: 47/soldier_1_1) [152501] Task: TASK_FACE_ENEMY (nc_combine_s: 47/soldier_1_1) [152501] Task: TASK_WAIT (npc_combine_s: 47/soldier_1_1) [152501] Task: TASK_RANGE_ATTACK1 (npc_combine_s: 47/soldier_1_1) [152536] operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1Schedule: SCHED_SHOOT_ENEMY_COVER (time: 2289.20) (npc_combine_s: 47/soldier_1_1) [152613] Task: TASK_STOP_MOVING (npc_combine_s: 47/soldier_1_1) [152613] Task: TASK_FACE_ENEMY (npc_combine_s: 47/soldier_1_1) [152613] Task: TAS_WAIT (npc_combine_s: 47/soldier_1_1) [152613] Task: TASK_RANGE_ATTACK1 (npc_combine_s: 47/soldier_1_1) [152648] operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1Schedule: SCHED_COMBINE_ASSAULT (time: 2290.24) (npc_combine_s: 47/soldier_1_1) [152683] Task: TASK_SET_FAIL_SCHEDULE (npc_combi
Re: [hlcoders] World shader override
-- [ Picked text/plain from multipart/alternative ] Doing a custom lightmappedgeneric shader could probably give you the effect you wanted. Not too sure though :)! /ProZak On 20/09/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hey list, > > I'm wondering if there is an equivalent of the ForceMaterialOverride for > the world. Say I wanted to render eg. the entire world ( without the > entities, just the brushwork ) in just one color, or better yet shaded but > untextured, is there a feasible way to do this? [ I'm not talking > post-process, I do mean the world rendering itself ]. > ForceMaterialOverride itself works for all entities except the world. > > Thanks for any info, > > -- Maarten > > > ___ > 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
[hlcoders] RE: RE: AI in multiplayer
-- [ Picked text/plain from multipart/alternative ] Im sorry to keep hounding about this question..you all probably know what its like to stare into a pile of code and get a bit lost...thats where I am and Im desperately trying to find out the bits I am missing. I am thinking it has something to do with the the way the AI is setting up its Schedule or Task state and not that its an animation problem directly. Below is a snippet of condump that lists whats happening in the process. I am now trying to figure out why it is that the AI for combine_s is having problems with the way this is defining the Schedule state... I cant seem to pick where its going wrong..Any help welcome. Look @ the condum below operator_handleanimevent --This is the Animation state of the combine_s while I am hidden behind a breakable model. Also I have a few of the following errors and was wondering if any you coders out there might have dealt with these in setting up AI? Its a condition of some sort that not been met? maybe its my own player model? Maybe the activity is not set up right? I cant really see which area it might be. TaskFail -> Don't have a route (npc_combine_s: 47/soldier_1_1) [152683] Break condition -> COND_ENEMY_UNREACHABLE (npc_combine_s: 47/soldier_1_1) [152690](failed) (npc_combine_s: 47/soldier_1_1) [152690] Task: TASK_SET_FAIL_SCHEDULE (npc_combine_s: 47/soldier_1_1) [152683] * Schedule: SCHED_COMBINE_ESTABLISH_LINE_OF_FIRE (time: 2285.63) (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_SET_FAIL_SHEDULE (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_SET_TOLERANCE_DISTANCE (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_GET_PATH_TO_ENEMY_LKP_LOS (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_COMBINE_SET_STANDING (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_SPEAK_SENTENCE (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_RUN_PATH (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_WAIT_FOR_MOVEMENT (npc_combine_s: 47/soldier_1_1) [152375] Task: TASK_COMBINE_IGNOREATTACKS (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_SET_SCHEDULE (npc_combine_s: 47/soldier_1_1) [152452] Schedule: SCHED_COMBAT_FACE (time: 2286.78) (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_STOP_MOVING (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_SET_ACTIVITY (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_FACE_ENEMY (npc_combine_s: 47/soldier_1_1) [152452] Schedule: SCHED_SHOOT_ENEMY_COVER (time: 2286.78) (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_STOP_MOVNG (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_FACE_ENEMY (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_WAIT (npc_combine_s: 47/soldier_1_1) [152452] Task: TASK_RANGE_ATTACK1 (npc_combine_s: 47/soldier_1_1) [152487] operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1Schedule: SCHED_SHOOT_ENEMY_COVER (time: 2287.51) (npc_combine_s: 47/soldier_1_1) [152501] Task: TASK_STOP_MOVING (npc_combine_s: 47/soldier_1_1) [152501] Task: TASK_FACE_ENEMY (nc_combine_s: 47/soldier_1_1) [152501] Task: TASK_WAIT (npc_combine_s: 47/soldier_1_1) [152501] Task: TASK_RANGE_ATTACK1 (npc_combine_s: 47/soldier_1_1) [152536] operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1Schedule: SCHED_SHOOT_ENEMY_COVER (time: 2289.20) (npc_combine_s: 47/soldier_1_1) [152613] Task: TASK_STOP_MOVING (npc_combine_s: 47/soldier_1_1) [152613] Task: TASK_FACE_ENEMY (npc_combine_s: 47/soldier_1_1) [152613] Task: TAS_WAIT (npc_combine_s: 47/soldier_1_1) [152613] Task: TASK_RANGE_ATTACK1 (npc_combine_s: 47/soldier_1_1) [152648] operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1operator_handleanimevent smg1event weapon smg1Schedule: SCHED_COMBINE_ASSAULT (time: 2290.24) (npc_combine_s: 47/soldier_1_1) [152683] Task: TASK_SET_FAIL_SCHEDULE (npc_combine_s: 47/soldier_1_1) [152683] Tas: TASK_SET_TOLERANCE_DISTANCE (npc_combine_s: 47/soldier_1_1) [152683] Task: TASK_GET_PATH_TO_ENEMY_LKP (npc_combine_s: 47/soldier_1_1) [152683] TaskFail -> Don't have a route (npc_combine_s: 47/soldier_1_1) [152683] TaskFail -> Don't have a route (npc_combine_s: 47/soldier_1_1) [152683] Break condition -> COND_ENEMY_UNREACHABLE (npc_combine_s: 47/soldier_1_1) [152690] (failed) (npc_combine_s: 47/soldier_1_1) [152690] _ SEEK Salary Centre: What are you really worth? Find out. http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseeklearning%2Ecom%2Eau%2F%3Ftracking%3Dsk%3Acon%3Askl%3Anine%3A0%3Ahot%3Acoursetafe&_t=764565661&_r=Seek_learning_AUG07_TAG
Re: [hlcoders] SDK Update heads up?
Frankly it is so. BTW, me and Keeper are in the same mod team ;) EmielRegis a.k.a. Millz www.invision-games.com Keeper apparently refers to exploits in the *engine*. He is a modder himself, so let's not insult his intelligence or good will and assume that, had it been possible to fix these exploits in the SDK code, he would have shared the fixes with us. Hence, it is not, and since we cannot fix them anyway he's right not to publish them. Well, I though we are all mature here and in the end we are the coders who should be fixing, not breaking, right?:P Agreed; please don't post details--it only encourages abuse. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keeper Sent: Wednesday, September 19, 2007 7:29 PM To: hlcoders@list.valvesoftware.com Subject: RE: [hlcoders] SDK Update heads up? Because I don't ever publicly post exploits. Pure and simple. Keeper -Original Message- From: Nick Sent: Wednesday, September 19, 2007 6:40 PM Subject: Re: [hlcoders] SDK Update heads up? It might be helpful to share some of the things here, maybe people already made fixes for them. Or they might not be problems after all. What is the point of having a mailing list if you don't want to share problems on it? If the orange box engine means a fix to some of these exploits, then an overhaul to some of our mod coding to fit the new SDK release might just be worth it. If you need examples of exploits, I can e-mail you offline. Keeper ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
Re: [hlcoders] SDK Update heads up?
Keeper apparently refers to exploits in the *engine*. He is a modder himself, so let's not insult his intelligence or good will and assume that, had it been possible to fix these exploits in the SDK code, he would have shared the fixes with us. Hence, it is not, and since we cannot fix them anyway he's right not to publish them. > Well, I though we are all mature here and in the end we are the coders who > should be fixing, not breaking, right?:P > >> Agreed; please don't post details--it only encourages abuse. >> >> -Original Message- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Keeper >> Sent: Wednesday, September 19, 2007 7:29 PM >> To: hlcoders@list.valvesoftware.com >> Subject: RE: [hlcoders] SDK Update heads up? >> >> Because I don't ever publicly post exploits. Pure and simple. >> >> Keeper >> >> -Original Message- >> From: Nick >> Sent: Wednesday, September 19, 2007 6:40 PM >> Subject: Re: [hlcoders] SDK Update heads up? >> >> It might be helpful to share some of the things here, maybe people >> already made fixes for them. Or they might not be problems after all. >> What is the point of having a mailing list if you don't want to share >> problems on it? >>> >>> If the orange box engine means a fix to some of these exploits, then an >>> overhaul to some of our mod coding to fit the new SDK release might >>> just >> be >>> worth it. If you need examples of exploits, I can e-mail you offline. >>> >>> Keeper > > ___ > 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] SDK Update heads up?
Well, I though we are all mature here and in the end we are the coders who should be fixing, not breaking, right?:P Agreed; please don't post details--it only encourages abuse. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keeper Sent: Wednesday, September 19, 2007 7:29 PM To: hlcoders@list.valvesoftware.com Subject: RE: [hlcoders] SDK Update heads up? Because I don't ever publicly post exploits. Pure and simple. Keeper -Original Message- From: Nick Sent: Wednesday, September 19, 2007 6:40 PM Subject: Re: [hlcoders] SDK Update heads up? It might be helpful to share some of the things here, maybe people already made fixes for them. Or they might not be problems after all. What is the point of having a mailing list if you don't want to share problems on it? If the orange box engine means a fix to some of these exploits, then an overhaul to some of our mod coding to fit the new SDK release might just be worth it. If you need examples of exploits, I can e-mail you offline. Keeper ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
[hlcoders] World shader override
Hey list, I'm wondering if there is an equivalent of the ForceMaterialOverride for the world. Say I wanted to render eg. the entire world ( without the entities, just the brushwork ) in just one color, or better yet shaded but untextured, is there a feasible way to do this? [ I'm not talking post-process, I do mean the world rendering itself ]. ForceMaterialOverride itself works for all entities except the world. Thanks for any info, -- Maarten ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
