lastalonJoin Date: 2008-05-02
Post Count: 1818 |
I have a few things I would like to suggest to allow scripters to use that I'm fairly sure wouldn't allow exploits if made properly.
1. Allow server communication, meaning allowing numbers, tables, strings, functions, userdata, etc., to be stored within something that all servers for that place can access continually. Not allowing html etc. to be added as a string or otherwise to prevent access of the website.
This would be good because it would allow scripts to share things such as a list of banned players so that when a player is banned by the owner or one of their personal game moderators all the servers will know when the table can be accessed from all the games servers.
This could be accessed through a global object something like _G.ServerCom which would be a table that you put values in and are added to the website in some way, or something similar, I'm not too picky about this part.
2. Allow editing of a low priority GUI (meaning shown underneath as well as not as important) allowing positioning and scaling using X and Y for on screen pictures that will NOT affect or allow access to the current GUI.
This would be nice to use for things such as huds for things like a strategy game where you have many options and need menu's for people to click on (could be checked using X and Y positions of the mouse in a tool (or a later idea that I haven't said yet)) allowing easy maneuvering through menu's unlike the current method of using key's and hint's, or even how xLEG0x did it using mouse cursors.
Instead of being accessed through a global value this could be accessed like an object in game using Instance.new("GuiObject") or selecting Insert - GuiObject. The properties of the object could be something like as follows: Xposition, Yposition, Xscale (The texture would be stretched to fit, much like a decal on a part), Yscale, Texture, Text (only texture OR text could be displayed on one), Measurements (Would be an Enum value of Pixels or Percent), Name, className, Archiviable, Parent. It could work much like a hint or a message along with a decal or texture where the rest would be handled by the game, it could be put in the workspace just like a hint or message, but would be able to display like a decal or texture with a picture.
3. Access to the mouse and keyboard through players, so that we can find out when they click and where they click, or when they type and where they type without a tool or hopperbin. This would work the exact same way as a hopperbin when it passes the Selected event, or a tool when it passes the Equipped event. It would be just as safe, just as a hidden property in the player object, or something similar.
This could help with things like GuiObjects mentioned above, for when they click. Or for clicking bricks to tell who clicked them instead of using a click detector. This could also be used to check when someone types something without typeing it (maybe a secret code for a door, or a quiz place) so that other players can't see. There are so may possabilities for this.
It would be very simple, it would pass the same way as the mouse in the Selected/Equipped events except through a property. It could be a property in the player object called Input or something like that, and would work the same way (game.Players.Player.Input.Button1Down:connect(function)). When a player looks at the properties of the player object, they could either see nothing listed for Input, or they could see the Input property, with the name of the Event being passed currently (Button1Down, Moved, nothing...).
4. Full access to the humanoid object instead of just the events like jumped, or the properties like jumping. It would be very useful in finding what a player is doing and would allow better control over characters (including human ones and AI ones lol).
This could be used for things such as a mind control tool that will give much better access to commands than jump, sit, walk, etc. and allow things like selecting tools and hopperbins, and removing hats/tools, and activating tools or clicking the mouse on hopperbins, and all kinds of other things. It would also allow people to not control certain things, like not being able to jump, but still being able to walk up stairs/ladders, or not being able to walk and only jump.
This would take a lot of work, and I'm not sure how to do it because I have no idea what causes these things to happen.
5. Much similar to number 4, but with vehicleseats. This would allow full access to vehicle seats through scripting. It could check for any hinges attached in any directions, etc. Again, I don't know how to do it because I don't know what causes them.
I would appreciate it if someone like Telamon, or MrDoomBringer would comment on these ideas. It is also much appreciated to get feedback that is constructive and not just saying that its bad or its good, I would like to know why you feel that way about it, and specifically how you feel about each idea.
Didn't read it? Too long? Then please don't post. |