Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Playlist saving and export/import

Open
#31 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
api, backend

Research direction

Start by locating the KatApi implementation and command tree mentioned in the issue, then review how guild data and file attachments are currently handled. Done means supporting save, load, list, delete, import, and export commands with serialized playlists and safe handling of received attachments.

Written by the indexing model from the issue text.

Description

enhancement

Command to save current loaded playlist with a custom name, and then load playlists back in. Should also be able to export/import through JSON or other serialization.

Possible command syntax:

  • !playlist save <custom_name> : Save a playlist
  • !playlist load <saved_name> : Load a playlist by name
  • !playlist import <file_attachment> : Import playlist to the guild via attachment
  • !playlist export [saved_name] : Export a saved playlist to file attachment
  • !playlist : Show list of all guild playlists
  • !playlist delete <saved_name> : Delete a saved playlist

Infrastructure needed:

  • KatApi implementation for loading/saving playlists (low cache lifetime)
  • Command tree for above commands
  • Sterilization of received file attachments!
Dominant language
Java
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ReignBit/java-discord-kat

All issues in ReignBit/java-discord-kat

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.