Re: We may have a problem...
 

Extensions can be decompiled also.
Anyways, you've been able to override itemdef index for ages.. Hell you can do it with tf2itms if you want, or there are other ways. It's not that big of a deal. You guys shouldn't worry so much about things.

It would however, be very nice if valve would implement a way for sever ops to allow for the use of custom models/attachables/weapons. Also, vpks would be greatly appreciated. It's hard to mod when you can't make custom content or send it to clients easily, which is the main goal here.

Honestly, who really cares about turning gibuses into howars?
Hell, I'd just like razorbacks and targes to show up when I regenerate them on players in hale.
Probly could just rendermode the and do something to nuke the charge cool-down or something, but creating the item should work too.

Re: We may have a problem...
 

https://wiki.alliedmods.net/Finding_...inding_Offsets

It's easy to get information from binaries, that is, compiled extensions, there's even a tutorial on the alliedmodders wiki. Just making an extension out of it isn't enough. You have to be really, really good at hiding things. And even then isn't enough, because people are going to be after what you wrote fairly quickly. I'd say about three days after you choose to give out any compiled code, it will be figured out and all over the place.

Edit 1: This user is asking $150 for it but I don't believe it is worth that much. He is going to sell it to everyone he asks, he already sold it to someone else and promised not to sell it, but he is still trying to sell it to others. Don't buy it, eventually the code will be free, with how many people hes trying to give it to

Edit 2: MasterXykon released it! http://facepunch.com/showthread.php?t=1341335 Say farewell to SetParent everyone!

Re: We may have a problem...
 

I'd also like to point out that this guy has been using always the same method (double parenting), even the same he used in a plugin he released here some time ago that got trashed (I still have the decompiled source of that I think).
Anyway, he should probably have credited Mecha The Slag for it: http://pastebin.com/629Z21sF
This is only really good for attachables that aren't hats/weapons since they can't be inspected so if I was Valve I wouldn't really bother fixing it.

Re: We may have a problem...
 

What a dumb-fuck. You think he would've learned after the last time something like this happened.

Quickly, someone figure out how to contact Mediafire and have them remove the file! Tell them it's child porn or evidence of terrorism.

EDIT: Just checked it out...how can a plugin be 27MB? Something don't seem right.....downloading to see what exactly he's uploaded. Ok so it's a bunch of models and materials to be used in the plugin, alongside the source code.

Re: We may have a problem...
 

Calm down. All Valve is going to do is fix double parenting on the client (quoting Zephyrus, "No idea why they un-fixed it in the first place"), which will not affect TF2Items.
-2ninja-

Re: We may have a problem...
 

Wasn't the last guy that made something like this public banned from AlliedModders?

This guy (the guy who released it today) knew that Valve would probably break a lot of other people's plugins due to that post.

He has said he didn't care.

Re: We may have a problem...
 

Indeed. This is nothing new at all and has been being used in public plugins for well over a year, maybe two.

http://code.google.com/p/rtdgaming/s...ttachments.inc

Re: We may have a problem...
 

Really? :shock: I don't think I've ever seen a public plugin using that...I have known about that link for quite some time, though, and thought that it was uploaded accidentally, or something.

Re: We may have a problem...
 

He did base it on that code, but it does function differently.

This is capable of full bonemerges with the player and any model, and visible to all clients.

To my knowledge, that linked env_sprite version can't

Re: We may have a problem...
 

Okay.
Let's move along then.