 |  |
 |  | Home |  | Add-On Repo | |
| Implementing v21 fixes by Badspot. | | |
| Adding changes by Badspot to make it work with Blockland r1395. | | |
[list=][*]Thoroughly revised the codebase, resulting in a massive performance boost. Loading times for both regular and content bricks are now 3+ times as fast as previous versions of the add-on.
[*]Added console notifications for when restrictions are added and for when they are toggled by RTB.
[*]Fixed an issue that caused JVS preferences in RTB to not be re-added to Server Control after the initial server hosted in a Blockland session is closed.[/list] | | |
1. Removed all internal pref saving / execution. All pref management is now done with RTB.
2. RTB prefs are now dynamically created for each restriction type, allowing super admins to toggle individual restrictions via RTB server control.
3. Fixed some formatting issues with certain server commands to bring them in-line with Blockland's own server commands (clearcontent, clearallcontent, clearcontentbyname, clearcontentbyblid).
4. Changed all references to "interactive" brick / bricks to "content" brick / bricks in messages.
5. Organizational changes. | | |
1. Altered stuck player / stuck vehicle detection routine to stagger input event calls for multiple players / vehicles by 33ms. This delay allows for some fairly useful event structures.
2. Client for onContentStuckVehicle is now the last driver of the vehicle (if it exists) or the owner of the vehicle spawn. | | |
1. The client object of players stuck in content bricks is now sent to the onContentStuckPlayer event. This is much better for several reasons, one of which is that you can now make it so that doors only reopen for stuck players if the player is allowed to open the door.
2. Because of the change in client object being sent to onContentStuckPlayer, the StuckClients and StuckPlayers targets are no longer needed. They have been removed. You can now use the Client and Player targets instead. | | |
1. Added OwnerPlayer and OwnerClient targets to the Content Add-On's input events. These targets are not valid for LAN play. They allow you to call output events on the client or player object of the person who owns the content brick.
2. Registering a custom content restriction now requires a unique ID. The format of the ID to be used should be 1XXYYYYY where XX is the number of the restriction out of the set you have made and YYYYY is your BLID. For example, 10100205 would be the ID for the first restriction Trader made. Requiring unique IDs provides save compatibility regardless of which restrictions you have enabled.
3. Miscellaneous organization changes. | | |
1. Fixed a an issue that affected proper loading of bricks owned by players who aren't in the server.
2. Added several server commands:
A. contentCount - Messages you with the number of interactive bricks you own.
B. contentCountAll - Messages you with the total number of interactive bricks in the server. Admin only.
C. contentCountByName / contentCountByBLID - Messages you with the number of interactive bricks owned by a particular player. Admin only.
D. clearContentByBLID - Clears the interactive bricks owned by a particular player. | | |
1. Added /contentCreate server command to replace content brick events with their default set.
2. Improved handling of content bricks in regards to whether or not they should receive their default events when planted, loaded, restored from fake death, etc.
3. Improved handling of calls to onContentCreated, resulting in much more consistent performance (especially when loading bricks that use the event to restore a particular state). | | |
| |
| |
