Skip to content

messing around version1

Java · active 2023-08-152026-05-21 (UTC)

Complete coverage26,616 / 26,616 hourly files (100%) · 2 absent upstream2023-08-152026-08-27 (UTC)
Events
438
Pushes
18
Pull requests
7
Issues
111
Stars
123
Forks
19

Activity over time

Daily event counts in the loaded window

Line chart, 1011 days from 2023-08-15 to 2026-05-21. Pushes: 18 total, peak 3 in a day. Pull requests: 7 total, peak 2 in a day. Issues: 111 total, peak 3 in a day. Comments: 143 total, peak 13 in a day. Stars: 123 total, peak 4 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue comment#230CommandGenius2026-04-14 21:51
    [26.1] Chunk corruption when used with Lithium 0.24.1
  • Issue comment#229Derpgamer222026-04-05 04:36
    Caverns and Chasms rainbow beacon beam becomes white when ferrite core is installed
  • Issue comment#229Derpgamer222026-04-05 02:26
    Caverns and Chasms rainbow beacon beam becomes white when ferrite core is installed
  • Issue#225Vancomb2026-02-19 17:16
    Forge 1.20.1 Clientside crash
  • Issue comment#223malte08112026-02-08 09:56
    ferritecore crash 1.19.2 forge 43.5.0
  • Issue#224ThakarisVder2026-02-07 05:30
    Can you confirm the status of Forge 1.20.1 support?
  • Issue#222irunatbullets2026-02-03 13:19
    Is ferrite-core 7.0.3 requirement of neoforge 21.1.218 on purpose?
  • Issue comment#222irunatbullets2026-02-03 13:19
    Is ferrite-core 7.0.3 requirement of neoforge 21.1.218 on purpose?
  • Issue comment#221malte08112026-01-30 09:37
    Wants me to update but then wants a version of neo forge not compatible with my version of minecraft.
  • Issue#220malte08112026-01-25 13:42
    missing curseforge tag for ferritecore-7.0.3-neoforge.jar
  • Issue comment#219malte08112026-01-19 07:14
    Client startup extremely slow (400+ seconds) when FerriteCore and Supplementaries are both installed (NeoForge 1.21.1)
  • Issue#216malte08112026-01-15 06:01
    Baghdad
  • Issue#215ThatCamel2026-01-09 13:29
    version 1.21.11 on modrinth still gets a out of date fabric errors
  • Issue#215ThatCamel2026-01-06 05:38
    version 1.21.11 on modrinth still gets a out of date fabric errors
  • Issue#214malte08112025-12-27 07:19
    Bmn
  • Issue#214mnbvcxzlll1243-rgb2025-12-27 01:23
    Bmn
  • Issue#211FortyTwoCn2025-12-13 08:03
    [Neoforge1.21.1]Conflict with industrialupgrade mod causing crash
  • Issue#210deaddiesel2025-12-10 22:37
    Game Crush
  • Issue comment#208malte08112025-11-02 09:52
    1.21.10 Update
  • Issue#209malte08112025-11-02 09:12
    FerriteCore causes network protocol errors when trying to join servers if Lithium is not installed/enabled
  • Issue#208malte08112025-11-02 08:52
    1.21.10 Update
  • Issue comment#208capyisslay2025-10-19 11:01
    1.21.10 Update
  • Issue comment#199malte08112025-10-05 12:19
    Mod 'ferritecore' attempted to override option 'mixin.alloc.blockstate', which doesn't exist, ignoring
  • Issue#206Dimarik102-cyber2025-08-22 15:04
    Ferritecore crush
  • Issue comment#205malte08112025-08-12 05:35
    [1.19.2] Minecraft instance can't be booted with Ferritecore and resourcefullib enabled together.

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 123 stars here means stars gained during the window, not the repo's star count.