Forum
TFTrue 2.8
Created 30th December 2008 @ 10:15
Add A Reply Pages: « Previous 1 ... 21 22 23 ... 41 Next »
Wlv, what you have just said can’t be related to TFTrue. We are not changing anything related to particles/effects, etc, and after a lot of testing, nobody ever noticed/reported anything similar. It was just a problem from your server..
@dunc : Yes ofc, there is an aimbot/wallhack/speedhack in it. -_-
As I said, the source code will not be given publicly. If anything needs to be checked it’ll be done with leagues admins, and I won’t say anything more about the source code now. I think this is the league admins problem, not players.
About scouts 2 shotting people, you are forgetting to put random spread into the equation. A scout can be at mid distance, and all of the hits from the scattergun _could_ hit or 3/4 of them could miss.
I’m trying now to stay out of this thread anyway because I really couldn’t care less if it gets added or not. While I would vote against it, it will only be another month before someone claims something else is wrong with the game and tries to fix it. Then a TF2 update will come out that will significantly change gameplay, and the balance issues would have to be totally reworked. Have fun doing that ;) I’ll just sit back and enjoy TF2 however it is being played.
Most intelligent post and one i aggree with the most by arx there.
Its nice to think we can make the game better but theres too many variables, opinions, conditions and obviously what valve will do next to consider.
And yep i shall be firmly in the section thats interested in what your doing but very much just playing tf2 and seeing what happens.
Anakin this discussion is essentially about the usage of TFTrue in ETF2L. The admins won’t make the decision to use it if the players aren’t happy. I’ve already said on numerous occasions that making the code open source would be a bad idea, but that doesn’t mean it couldn’t be reviewed by competent coders within ETF2L. I really can’t see what the problem is with giving the code out, unless there’s something to hide. You joke about the cheats but it would be easy to do, no? How do we have any proof that something isn’t amiss if we can’t access the source code?
The coincidental bugs are going to make the community restless unless other coders can analyse the code themselves. Thus far the testing of the plugin has been fairly poor – it needs to be done on more servers in more rigid test environments. It’s not always easy to do but it’s not impossible and it’s exactly what the community needs if it is to advocate the use of the plugin in official competitive play.
It should *at least* be allowed to be used in Season 4 if both teams playing agree to do so.
then it should also be allowed to play with 2 Medics if both teams agree no?
we need fixed rules mate.
Er yeah…fix a rule saying it’s allowed if both teams agree.
Like you can use a merc if both teams agree.
Duh.
Givin the community the code means aswell anyone can code cheats. But i’m sure the code shouldn’t stay secret and admins should have the right to take a look on it.
wouldnt that be a good time to start implementing a etf2l anticheat aswell? ;)
@dunc, you didn’t understand what I meant. I didn’t say the admins have to force people to use the plugin. I said that if the code needs to look at, it’ll be done by league admins, and not by anyone else. That’s all.
It is you that misunderstood me, Sir :)
Release the code to the admins. Have them check it over. In the meantime, it needs to be tested rigorously so that the ETF2L players themselves can be happy about its usage.
Only then will you get the percentage support required to allow its use in ETF2L.
With all due respect, but I think some of you guys are weak on understanding statistics.
You are trying to implement an averaging system without even knowing the characteristics of the value you want to average. You do not know its range (50/60-130/150??), you do not know its type of spread (linear or gaussian) or its standard-deviation, you do not know how often a nade inflicts damage in a normal game.
All these points and especially the last one are tremendously important in guessing the pay-off of all the hassle some of you want to put us through (stuttering, linux probs).
Do you really think, that a match gets decided by one or two lucky demo-nades?
In the course of a match a demo sure scores some 50 hits with his nade (directly and indirectly), possibly more. Over such a big number of hits, the random factor gets eliminated.
If even a luck-driven game like Poker shows that luck does not account for a big difference over the course of a season and if even in football, the outcome of a season is mostly determined by the salary payed to the players, how can you think that TF2 with its low luck-factor is luck-determined?
Do you think luck can make me play better than Ryb for even then minutes? Do you think that the worse team wins because it gets lucky three times in a row (which would be necessary to win three cap-battles and cap all five points) and that for enough rounds to beat the stronger team?
What is the pay-off, compared to the costs (instability, maintenance, computing power, hacking potential, bitching potential)? Is it worth all the trouble just to introduce a hidden demo-nerf and please some scout-players?
Every class now has the mean value of the range, how can this be a demo nerf? If you say its a demo nerf because you cant do as much damage sometimes then that stands for every class, whether it be demo, scout, heavy, spy, sniper, soldier, pyro, engineer or medic. It goes both ways, you need two nades to kill a scout, spy, engy, sniper, you can no longer one-shot these classes, but then you’ll never need three nades.
@notger: You could use the same statistics with crits, and you could also say that in the final it doesn’t change anything. What people want is to remove the random factors of the game, that’s all.
@dunc: That’s exactly what I understood. And I already talk to Mole (ETF2L Admin) since TFTrue was released about every change which is done, and it’ll be checked by admins, as I said earlier. Now no need to continue talking about the source code here, it is between me and the admins, not here.
Add A Reply Pages: « Previous 1 ... 21 22 23 ... 41 Next »