HotThoth
|
  |
 |
| Joined: 24 Aug 2010 |
| Total Posts: 1176 |
|
|
| 20 Jun 2012 02:21 PM |
Heyo all-- it's been bugging me for a while that we seem to have some API calls which just don't do anything. I want to fix this now for once and for all, so I'm making an exhaustive list. If you know of any other calls/properties/menus which legitimately have no effect or which generally don't do what they're supposed to do, please add to the list!
Note: this is not a request for *new* features, but rather just issues with the current API, as is visible to most users (so ManualSurfaceJoint is not on the list, because it's not really part of our visible API).
---------------RBX.Lua----------------- - Half of the MouseButton events - Character Loading API - HumanoidNameOcclusion doesn't always work - InsertService::insert is broken [weld references can get invalidated]
----------Objects and Properties------ - SpecialMesh .Offset - TouchTriggers [should not be used/visible] - BodyForce [should be used/visible]
-----------ROBLOX Studio------------- - Insert-->Service doesn't work (and can't undo) - Most of the Camera Formatting Menu - Camera TiltUp/TiltDown are reversed? - Undo doesn't work with Terrain - Play/Reset has issues
Again, let me know if there is anything I'm missing from the list!
- HotThoth
|
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 02:26 PM |
| _G Doesn't work anymore. You Should fix that *wink**wink* |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 02:28 PM |
Are you fixing or deleting these?
Not sure if it's fixed by now but there's a mass of problems with Humanoids. Falling through bricks, randomly dying, health bar doesn't always update (I think?), it's, if I remember, a _HUGE_ pain to move them from lighting and such into workspace without them dying, etc. |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
|
| 20 Jun 2012 02:30 PM |
| Oh and can camera in roblox studio be like in old times? So it moves around it self, not around one point in front of it. Like it would be in first person... That's so annoying that camera moves around one point.. |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
|
| 20 Jun 2012 02:31 PM |
| @trapping. But you don't have to place them in lighting now. You could change InGame property thingy, but i guess it will have to die to get back in game.. :/ |
|
|
| Report Abuse |
|
|
MrNicNac
|
  |
| Joined: 29 Aug 2008 |
| Total Posts: 26567 |
|
|
| 20 Jun 2012 02:31 PM |
"- Play/Reset has issues"
Does that include the problems with the Changed event and the Humanoid events (such as Walking or Seated) not registering after a reset? |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 02:34 PM |
"You could change InGame property thingy, but i guess it will have to die to get back in game.. :/"
daf- wait... dahell?
since when did that exist? what does it do? why was I not informed? |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
|
| 20 Jun 2012 02:39 PM |
| http://wiki.roblox.com/index.php/CharacterAutoLoads |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
|
| 20 Jun 2012 02:40 PM |
| Idk since when it's there, but i noticed that once when i was checking LoadCharacter method. |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 02:42 PM |
^
what about npcs and dah zombies? |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
|
| 20 Jun 2012 02:44 PM |
| Roblox is discriminating themz, because they think that they don't have soulz! |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
|
| 20 Jun 2012 02:45 PM |
| I wonder if "EquipTool" method acctualy works... |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 02:46 PM |
Uhh, HotThoth, you do realise undo only works on basic operations and in most cases craps your place up? The save button is MUCH more useful.
Right, once when I was building a massive house I accidently moved one model into another and then moved it to Lighting. I then used the undo button. It seemed to rendomly dump things into Workspace or game and leave empty models lying around that used to be filled with bricks. For the 2.0 release of Studio, fix it. |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 02:47 PM |
| uh.. yeah.. I just wanted to say that.. uh.. it really irritates me that ROBLOX would imply that zombies and NPCs don't have souls.. ok.. well, they do have souls.. ok.. and lately they've been called NPCs and zombies.. by everyone in their school. and it really hurts their feelings... NPCS AND ZOMBIES HAVE SOULS! |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 02:48 PM |
| Let's be honest. The undo button is terrible. |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 02:50 PM |
I just remembered...
Since when did ClickDetectors work with right click? It really annoys me and I'm surprised nobody else has complained (since that is what the Scripters forum is for...)
If ClickDetectors are doing to work with right click, give it its own event and make right or left click optional (right click false by default). |
|
|
| Report Abuse |
|
|
zars15
|
  |
| Joined: 10 Nov 2008 |
| Total Posts: 9999 |
|
|
| 20 Jun 2012 02:56 PM |
| Yeah about right click.. I noticed it once, but it didin't realy bug me, but it would be good idea to serpeat themmz. |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 03:05 PM |
I think the Teams:RebalanceTeams method or something like that doesn't work.
I never managed to get it to work.
Sadly, I can't test because I'm stuck on Fedora.
--
The Guest property of the Player object should either be removed, either be unlocked.
The only reason to not unlock it would be if it is useless, in which case it might as well be removed.
If it isn't useless, then you might as well unlock it, because we can already know if a player is a Guest anyway.
---
I'd also suggest to do something about the Players.NumPlayers property. We don't have a Teams.NumTeams property and a Instance.NumChildren property, now, do we? Therefore, why would we want Players.NumPlayers? I know it's kept for script compatibility, but, still...
---
Terrain:Reset takes A LOT of time to complete. Way too much time. Terrain:SetCells(Terrain.MaxExtents, 0, 0, 0) completes 50 times faster. I'm not exaggerating, it really completes 50 times faster.
---
The Humanoid has lots of members that are broken, useless, glitchy and everything. |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 03:13 PM |
Player:GetFriendStatus should be unlocked.
Why? Because it gives us information we can already get from the IsFriendsWith method.
It also tells us whether the user has sent or received a friend request to the other/from the other. Nothing bad could happen here, but this information could however be useful.
---
Player:RemoveCharacter should be unlocked. No, actually, it should be removed.
All it does is set the player's character to nil. Not very harmful, neither very useful, is it?
---
Player.MouseDownOnPlayer should be unlocked.
We can already know if a player's character was hovered on, by filling that player's character with ClickDetectors or by using a tool or whatever. However, this would be a lot more practical. And it wouldn't be harmful, BECAUSE WE CAN ALREADY DO IT.
---
Seriously, you developers should stop locking stuff that is completely unharmful and should stop making members that do things that can already be done easily. |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 03:21 PM |
Players:GetPlayerByID should be unlocked and renamed to GetPlayerById.
It should be renamed to GetPlayerById because that's how every other method that contains 'ID' is named (the alternatives with 'ID' instead of 'Id' are deprecated).
It should be unlocked for convenience, because it allows us to get a player by his ID, something we can already do anyway.
---
DataModel:SetCreatorID should be removed.
It was replaced by SetCreatorId and is currently deprecated and locked.
Is is completely useless because it isn't meant to be used by normal users (duh) and has been replaced by another.
Removing it won't break any script, because, again, IT ISN'T MEANT TO BE USED BY NORMAL USERS.
The same applies to DataModel:SetPlaceID.
---
Assuming you also consider the different data types as being a part of the API...
You should make the various members of CFrames, Vector3s and all other data types that are currently only available camelCased available CamelCased, to make it consistent with the rest of the API. |
|
|
| Report Abuse |
|
|
Legend26
|
  |
| Joined: 08 Sep 2008 |
| Total Posts: 10586 |
|
|
| 20 Jun 2012 03:23 PM |
Kinda went overboard with this.
--Studio/Game * Characters can get flinged away by terrain * Have to DebugDisableInterpolation to get characters to render where they're supposed to be. * Log file spam. (AppData\Local\Temp and AppData\LocalLow\RbxLogs) * Switching to OpenGL causes the cursor to get HUGE and the shadowing between DX and OpenGL implementions appear strange. * Object Browser shows random deprecated stuff even when settings().Authoring.ShowDeprecatedObjects is false * Block and Cylinder mesh do not support materials though SpecialMesh does * [*]Mesh.VertexColor doesn't seem to have effect. * About 50% of the time, instead of removing something, the devs just hide the class member from the object browser completely. (events Player.Kill and BasePart.LocalSimulationTouched for example) If it's a really old or unknown thing, you aren't going to break ANYTHING by removing it. Leads to an API bloat of unknown stuff.
--Studio buttons * File>Print stuff is useless and doesn't really work. * View > Game Layout murders studio b/c of attempts to fix bugs * Insert > Clear Tools* - no one uses these. * Format > Set Model Front - What is this supposed to even do? Doesn't work? * Format > Replace glue/welds - useless? * Tools > Join selected bricks and engine stats do nothing * Tools > Insert Model Raw - does it do anything different than Insert > Model? If not, kill it. * Changing settings are generally really obscure * Right clicking on ClickDetectors fires the event. It shouldn't and is annoying. * ForceField doesn't scale with the model's size. * ...why is the force of gravity 196.3...
--API * Object "LocalWorkspace" exists but isn't usable * Why is DataCost locked? Just make it read-only if it isn't already. * ParallelRampPart can't be created * Team.Score doesn't do anything visible * Wasn't StoppedTouching locked until after it was deprecated? As such, no one is using it. It shows it in italics in the object browser, not striked through. * Decal.Specular and Decal.Shiny do_nothing_at_all. * A lot of Body objects have camelCased members still. * JointsService isn't an actual service. Can't be gotten via GetService. Make it so it is. * Humanoid:MoveTo doesn't work as expected. No alternatives. If you fix it, "zombie" scripts are doomed though. * y Humanoid.SetClickToWalkEnabled b locked? * A lot of events in the humanoid make no sense. Humanoid.RagDoll? How would I get that to pass true in the first place? * Teams.BalanceTeams doesn't seem to work
--Requests :P (Just had to do this section) * Allow us to shut down a server without having to crash it. * Make object browser more transparent. Show us everything. |
|
|
| Report Abuse |
|
|
nightname
|
  |
| Joined: 10 Jun 2008 |
| Total Posts: 8960 |
|
|
| 20 Jun 2012 03:26 PM |
The humanoid's MoveTo method is quite peculiar. It has an extra argument with no significant use at all.
[Humanoid]:MoveTo(loc, part)
As far as I remember, the loc argument is where the humanoid will move to, and the second argument does not effect the method at all. Is this a joke or something?
|
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 03:30 PM |
| @nightname; I believe that the part argument was for when there used to be a green circle that hovered where your mouse was..I don't remember what it was used for though. |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 03:31 PM |
To summarize it all...
- Stop locking harmless stuff. (like the Players:GetPlayerByID method) - Stop creating members for things that shouldn't require one. (like the Player:RemoveCharacter method) - Remove useless members. (like the deprecated and locked DataModel:SetCreatorID method which was only intended for the devs
Also, take a look at Legend26's post. Even though he went a little overboard with it (he put stuff not relating to the API), he mentioned lots of things that should totally go on your list-of-things-do-fix. :) |
|
|
| Report Abuse |
|
|
|
| 20 Jun 2012 03:34 PM |
Oh yeah, something that _ABSOLUTELY_ NEEDS TO BE INSTANTLY AND URGENTLY REMOVED:
Team.Score
The most useless property that was ever created in ROBLOX's history.
It has absolutely no purpose. |
|
|
| Report Abuse |
|
|