|
When you have a tool, and click and hold the mouse, the target point doesn't change. This might not be a big deal for some, however for those who create/use automatic weapons, this is a BIG DEAL.
The gun scripts that use Humanoid.TargetPoint are constantly firing in one spot because of this issue. Changing the TargetPoint to make it change positions while shooting is needed, since then guns won't shoot in the same spot constantly. |
|
|
|
These scripts have been fixed with workarounds many a times.
Non-issue. |
|
|
|
I think it's something about modifying Cframe values. I forget. you might be able to find it if you look hard enough |
|
|
I agree I have the same problem two and I have to move on to single fire weapons. |
|
cobalt10Join Date: 2008-07-21
Post Count: 7371 |
Support.. |
|
|
THANK YOU FOR AGREEING! I'm not digging into 400 pages of free models to find one solution.
Anyone else support? |
|
|
Welp, now that i think of it, a workaround for a supposed-to-work script is a flaw in itself.
Support. |
|
|
OR
The makers of those guns can stop being stupid and start using the Mouse.Hit property. Seriously, Humanoid.TargetPoint is not at all needed for guns. It's just something stupid that you can use if you don't have the time/energy/brains to simply use a freaking LocalScript, which you must already be using, since you need the Mouse to get the Button1Down event to see when a person clicked.
In case you can't script very well, here's a non-scripters version:
Humanoid.Target point is stupid hax. Using it is pointless, there is already a much better alternative. |
|
|
Mouse.Hit is likely to change, especially since I heard they killed it in the gametest, as well as Button1Down. TargetPoint is used so much, and it is so unlikely to break/riddened that it is a reliable source of direction for targeting weapons.
Besides, are you going to whine to 80% of Roblox's population to use LocalScripts, only because you can't simply join along and help us fix a problem that most already are getting quite annoyed about? |
|
|
"I heard they killed it in the gametest, as well as Button1Down"
The admins/devs would NEVER do that. I believe that Telamon has decided to nuke the MouseObject instance, because it does absolutely nothing, but removing properties and events from the Mouse would be a terrible idea, as they are both working perfectly and very useful in scripting.
"it is so unlikely to break/riddened that it is a reliable source of direction for targeting weapons"
Kind of ironic that you would say that, seeing as this thread is specifically asking for TargetPoint to be fixed.
"are you going to whine to 80% of Roblox's population to use LocalScripts"
Yes, because that is the correct way to do it.
"most already are getting quite annoyed about"
If you are getting annoyed with it, then simply fix the problem on your own. It just takes a minor edit to fix guns like that. |
|
|
Why are you argueing over something that most people use? I could change the guns a little, but what about the others who don't know what is wrong? Other places other than mine will have the same problem you know. |
|
RedX8Join Date: 2010-06-02
Post Count: 839 |
Agree, and support myslef. They should also bring back custom animations so we can make reload, and firing animations. |
|
|
Good idea, hate that bug.
Support |
|
|
ArguiturJoin Date: 2011-06-04
Post Count: 40 |
Hello, I'm Arguitur.
~rationes son ardente ira populi~ |
|
|
@Arguitur, do you speak English? (parlez-vous anglais?)
Also, Hello to you also.
Anyone else support? |
|
|
|
Well at least its fixed on Gametest.roblox. I should be quiet now.
Let this die now, I have something else in mind to argue... |
|