Skip to content

feat(media): add more life and diversity in alternative media coverage #195

Description

@Vincent-LAMBERT

Problem or opportunity

The current system makes the difference between traditional media coverage with news report from Sheep Esport and other sources but only includes spanish-speaking alternative media coverage, namely EsportManiacos, Al Lio Podcast and el_yuste. Furthermore, messages from Al Lio podcasts can pop any day of the week whereas they broadcast on specific days of the week.

This makes the game experience feel detached from the player language and chosen nationality

NB: This is a first for me. I never contributed before in a project but I am particularly interested in helping the OLM team. I am a french computer science PhD and engineer and I have been following league esports for 5 years. I can help with the french translation too as I saw issues here and there but this is not the focus of this feature request. Do not hesitate to tell me if I should change something in this feature request.

Proposed solution

Add more diversity to include alternative media coverage for each language currently supported in OLM.
Modify the mod.rs, the message_builder.rs and the languages .json files to add daily random events called from process_day().
These events would retain a low probability each day so they don't spam the player.

UX impact

No UX impact

Acceptance criteria

  • Alternative media (podcast and streamer) messages added for every language in OLM
  • Functional translation for every other language in OLM (with DeepL from english and manual check for french and spanish as I speak these languages)
  • Messages received should come in priority from the chosen language and english alternative medias
  • Messages should come the day after an alternative media broadcasted. For podcasts, it depends on the podcast. For streamers, it can be any day.

Scope

Other

Approval pre-flight

  • I searched existing issues and did not find a duplicate.
  • I understand maintainers must add status:approved before implementation starts.
  • I will branch from development using type/lowercase-slug if this is approved.
  • I identified whether this changes docs, release behavior, licensing, or data provenance.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:needs-reviewIssue is waiting for maintainer reviewtype:featureNew feature or capability

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions