10-16-2010, 09:22 PM
(This post was last modified: 10-16-2010, 09:25 PM by Jacob__mybb_import1.)
Tools are now working; see the Insert Object menu. Place them in the StarterInventory and they will be given to all new players.
When a player is added, the tools are shown in a row along the top of the screen. Use the number keys to select a tool.
Tools have 4 events. When making a game with scripted tools, you should always use a script inside the tool to connect the events so they will work when the tool is copied from the StarterInventory to the player's inventory.
The events are: selected, deselected, mousedown(button, position), mouseup(button)
You will also see Drag, Copy, Delete, and Rotate tools; these are building tools that don't require any scripting to use.
New players will have a fancy new default game, others can download it here: http://buildism.net/default.buildism
![[Image: ippgtw.jpg]](http://i56.tinypic.com/ippgtw.jpg)
Other features in this update:
When a player is added, the tools are shown in a row along the top of the screen. Use the number keys to select a tool.
Tools have 4 events. When making a game with scripted tools, you should always use a script inside the tool to connect the events so they will work when the tool is copied from the StarterInventory to the player's inventory.
The events are: selected, deselected, mousedown(button, position), mouseup(button)
You will also see Drag, Copy, Delete, and Rotate tools; these are building tools that don't require any scripting to use.
New players will have a fancy new default game, others can download it here: http://buildism.net/default.buildism
Other features in this update:
- The camera is centered over the player's head rather than the middle of their body
- getChild(name) global member function. This is the same as using dot notation (game.World.Model.Part, etc.) except that when the child doesn't exist, it returns nil rather than causing an error. You should use this function when you're not sure if a certain child exists or not.
- game.World:getPartAt(Vec2D(x, y)) - gets the part at the specified world location; very useful for tools
- message() function for players (game.Players.PlayerName:message(text)). This makes a line of text appear at the bottom of their screen; use the function without any arguments to clear the message.
- Fixed registration error (why didn't anyone tell me?)
- Fixed an odd bug related to dragging parts