Skip to content
This repository has been archived by the owner on Jul 28, 2022. It is now read-only.

Releases: Sleitnick/AeroGameFramework

AeroGameFramework v1.7.3

15 Mar 14:17
Compare
Choose a tag to compare
  • Fix Maid:GivePromise to actually work as expected
  • Fix memory leak when Signal:Fire is called without any connections

AeroGameFramework v1.7.2

23 Nov 15:43
d5ceb37
Compare
Choose a tag to compare
  • Fix ProfileService so that it will work properly within the AGF environment
  • Replace tick() with appropriate replacements (e.g. time() and os.time())
  • Fix linter

AeroGameFramework v1.7.1

27 Aug 18:14
Compare
Choose a tag to compare
  • Remove StoreService
  • Remove old Event module
  • Add new Signal module (replaces Event module)
  • Add new raycasting methods
  • Add ProfileService module
  • Upgrade Promise to 3.0.1
  • Implement new .settings file for configuring module behavior within the framework
  • Updated VS Code extension to allow for creating settings files (v0.0.23)
  • New PID module implementation

AeroGameFramework v1.6.1

21 May 21:19
Compare
Choose a tag to compare

Added support for Selene. All pull requests are now required to pass through the Selene check before being merged into master.

Implemented less verbose method names for firing events and deprecated the old versions.

Modules are no longer wrapped with the Aero metatable if they already have a metatable and a __call metamethod. This adds easier support of third-party modules such as DataStore2.

The mouse is no longer enabled/disabled by default based on user input. If developers wish to hide the mouse automatically when a gamepad is used, UserInput.HideMouse must be set to true.

There were also various bug fixes and performance enhancements thanks to the implementation of Selene.

AeroGameFramework v1.6.0

23 Apr 16:10
Compare
Choose a tag to compare

Added NumberUtil and VectorUtil libraries.

AeroGameFramework v1.5.2

14 Apr 19:19
76cb3a3
Compare
Choose a tag to compare

Fix a breaking issue regarding back-to-back invocations of RemoteFunctions within the internal client script. This issue was caused by an incorrect design decision that subsequent calls to a pending RemoteFunction should return the result of the first pending invocation. In other words, if a RemoteFunction was invoked 5 times at the exact same time, each invocation would return the result of the first invocation.

This faulty design has been reverted to the old behavior from before v1.5.1, which guarantees that each invocation of a RemoteFunction is unique.

AeroGameFramework v1.5.1

06 Apr 15:25
Compare
Choose a tag to compare
Add python requirements

AeroGameFramework v1.5.0

06 Jan 05:12
Compare
Choose a tag to compare
Update filelist

AeroGameFramework v1.4.1

15 Dec 22:55
Compare
Choose a tag to compare
Update version

AeroGameFramework v1.3.0

13 Feb 04:07
Compare
Choose a tag to compare

Restructured source directory and installer to be compatible with Rojo.