@wavezfm/api 0.7.18 → 0.7.20

package/README.md

@@ -342,6 +342,24 @@ bot.on<RoomBotRealtimeEventPayloads['queue_removed']>('queue_removed', packet =>
 
 `queue_left` remains a general queue notification; explicit departure adds `reason: 'voluntary'`. Forced removals emit `queue_removed` with the resulting `queue`, a cause (`moderator`, `kick`, `ban`, `clearqueue`, `removeghost`, or `queue_restriction`), and preserve the corresponding legacy queue notifications. `queue_restriction` means a queue access block removed an actually queued user. Kicks and bans still emit `user_left` when presence is removed. `message_deleted` and `chat_cleared` identify the action's actor. Explicit role changes enrich `user_updated` with `actor`, `previousRole`, and, when available, `previousCustomRoomRoleId`; other profile updates need not carry these fields.
 
+`client.roomBot.clearChat(roomId)` retains its existing HTTP request and
+`{ success: true }` response. On the updated server, a general bot clear removes
+unprotected messages from public and staff chat while preserving messages from
+platform admins, developers, and ambassadors. A bot cannot bypass that protection
+through its owner's admin role or `delete_protected_messages`; that permission
+allows individual message deletion only. Direct actions against protected users
+can still fail with `ROOM_MODERATION_PLATFORM_ROLE_FORBIDDEN`.
+
+When a `chat_cleared` event contains `messageIds`, remove only the listed IDs
+from local history. An empty array means no removal. WebSocket `messageCount`
+can be absent or retain the requested deletion limit; the IDs are authoritative.
+HTTP clears emit a separate event for each channel with the actual deleted IDs
+and count, including `[]` and `0`, with normal staff-event access rules.
+Full-clear events without `messageIds` retain their existing channel or
+`clearAllChannels` scope. These fields are already supported by
+`RoomBotChatClearedPayload`; the behavior change requires a server deployment,
+not a new SDK method.
+
 `track_skipped` and `queue_reordered` also include `roomId` and `actor`, with typed payloads `RoomBotTrackSkippedPayload` and `RoomBotQueueReorderedPayload`. Legacy `actorUserId` continues to identify the authorizing account, while `actor` distinguishes a bot from its owner. Queue reorders preserve their move/swap positions or bulk-removal details. Assigning the same built-in and custom room roles again does not emit a role-change event.
 
 `room_settings_updated` carries `{ roomId, actor, changedFields }`, with changed field names only. `public_room_updated` continues to refresh the public room directory for settings, presence, and playback changes; it does not guarantee an actor or a settings delta.

package/dist/types.d.ts

@@ -198,6 +198,8 @@ export interface BadgeAssignment {
     [key: string]: unknown;
 }
 export interface RoomActiveUser {
+    /** Approximate country detected from the current connection IP, never the profile flag. */
+    connectionCountryCode?: string | null;
     id: string;
     username: string;
     displayUsername?: string | null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wavezfm/api",
-  "version": "0.7.18",
+  "version": "0.7.20",
   "description": "Official JavaScript/TypeScript API client for WavezFM.",
   "homepage": "https://docs.wavez.fm/docs",
   "repository": {