diff --git a/FreePackages/Handlers/PackageQueue.cs b/FreePackages/Handlers/PackageQueue.cs
index d3f2a24..3a4c4c0 100644
--- a/FreePackages/Handlers/PackageQueue.cs
+++ b/FreePackages/Handlers/PackageQueue.cs
@@ -16,8 +16,8 @@ internal sealed class PackageQueue : IDisposable {
 		private Timer Timer;
 		private readonly ConcurrentQueue<Package> Packages = new();
 		private const int DelayBetweenActivationsSeconds = 5;
-		private readonly uint ActivationsPerHour = 40;
-		private const uint MaxActivationsPerHour = 50; // Steam's imposed limit
+		private readonly uint ActivationsPerHour = 25;
+		private const uint MaxActivationsPerHour = 30; // Steam's imposed limit
 		private bool PauseWhilePlaying = false;
 
 		internal PackageQueue(Bot bot, BotCache botCache, uint? packageLimit, bool pauseWhilePlaying) {
diff --git a/README.md b/README.md
index 879c344..2b98660 100644
--- a/README.md
+++ b/README.md
@@ -44,10 +44,10 @@ Under certain conditions, activating a free package while playing a game on Stea
 
 ### Changing the hourly package limit
 
-A maximum of 50 packages can be activated per hour.  By default, this plugin will use at most 40 of those hourly activations and will resume where it left off if it's ever interrupted.  You can control this limit by adding `FreePackagesPerHour` to your individual bot's config files of `uint` type.
+A maximum of 30 packages can be activated per hour.  By default, this plugin will use at most 25 of those hourly activations and will resume where it left off if it's ever interrupted.  You can control this limit by adding `FreePackagesPerHour` to your individual bot's config files of `uint` type.
 
 > [!NOTE]
-> I don't recommend raising this value.  The default is 40 to let you manually redeem packages without having to fight with the plugin.  It's also not always possible for the plugin to tell when it's being rate-limited, and so it's best to avoid ever getting rate-limited.
+> I don't recommend raising this value.  The default is 25 to let you manually redeem packages without having to fight with the plugin.  It's also not always possible for the plugin to tell when it's being rate-limited, and so it's best to avoid ever getting rate-limited.
 
 ---