id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type 1378697554,PR_kwDOBLalGM4_PPLN,3902,Fix: Attributes able to be augmented above 100 innate,7436154,closed,0,,,0,2022-09-20T01:28:00Z,2022-09-24T00:54:27Z,2022-09-24T00:54:27Z,CONTRIBUTOR,,0,ACEmulator/ACE/pulls/3902,"This is an attempt to amicably resolve an issue in which players are able to augment innate attributes above 100 innate. In an attempt to respect the ambiguous nature of this functionality, it was written such that server operators must opt-in to this functionality. **To reproduce**: Create a character with 99 innate coordination, purchase the Oswald's Enhancement augmentation once = 104 innate coordination. **Resolution** This adds a new server side setting (""attribute_augmentation_safety_cap"") which, when enabled, will prevent players with >= 96 in an innate attribute from purchasing augmentations for said attributes. Furthermore, the 'verify-attributes' command will retroactively fix characters who have taken advantage of this by redistributing 5 points of an attribute in which this was exploited to the lowest available attribute (so that the points are not lost), while resetting the player's attribute reset timer so that they may legitimately redistribute the points at they please.","{""url"": ""https://api.github.com/repos/ACEmulator/ACE/issues/3902/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,79078680,pull 1596166916,PR_kwDOBLalGM5Kkdek,3955,Cloak proc configuration,7436154,closed,0,,,0,2023-02-23T03:45:51Z,2023-03-19T15:58:38Z,2023-03-19T15:58:38Z,CONTRIBUTOR,,0,ACEmulator/ACE/pulls/3955,"This is intended to allow server operators to scale cloaks to proc less or more frequently with a few configuration options. It's not intended to deviate much from the derived formula. Sadly, I wasn't able to track down any leads on the retail formula.","{""url"": ""https://api.github.com/repos/ACEmulator/ACE/issues/3955/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,79078680,pull 1708670657,PR_kwDOBLalGM5QcRFK,4003,Mysqlconnector3919: Fix auto update issues that arise in newer versions of MariaDb,7436154,closed,0,,,4,2023-05-13T16:12:31Z,2023-07-01T07:58:57Z,2023-07-01T07:58:56Z,CONTRIBUTOR,,0,ACEmulator/ACE/pulls/4003,"When setting up a new dev environment recently I encountered the same issue described in #3919 Some cursory research lead me to a discussion about this on [Stack Overflow](https://stackoverflow.com/questions/74060289/mysqlconnection-open-system-invalidcastexception-object-cannot-be-cast-from-d) I decided to implement MySqlConnector as an alternative to MySql.Data, but it wasn't a drop-in replacement as it lacks support for the MySqlScript methods (including the StatementExecuted event) so some light refactoring had to be done.","{""url"": ""https://api.github.com/repos/ACEmulator/ACE/issues/4003/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,79078680,pull