Ind Posted November 9, 2012 Share Posted November 9, 2012 "MINICORE" as it is defined in over a dozen locations within the source, are there any reasons not to purge it? I'm asking because I myself have little clue why that thing was coded in the first place 1 Link to comment Share on other sites More sharing options...
GreenBox Posted November 9, 2012 Share Posted November 9, 2012 I never understood wtf is the minicore too O_O Link to comment Share on other sites More sharing options...
Maki Posted November 9, 2012 Share Posted November 9, 2012 Looks like ultramage removed it from eathena? https://trac.paradoxsystems.net/changeset/15203/ Link to comment Share on other sites More sharing options...
Brian Posted November 9, 2012 Share Posted November 9, 2012 r15204/eathena/ looks like a pain to merge too. Link to comment Share on other sites More sharing options...
Ind Posted November 10, 2012 Author Share Posted November 10, 2012 aah o-o minicore ifndef is used by the mapcache (and previously the converter stuff), i think there is little point on keeping it Link to comment Share on other sites More sharing options...
Cookie Posted November 24, 2012 Share Posted November 24, 2012 As it is used by the mapcache (per Greenbox), I'm going to reject, and we'll keep it. More info: <GreenBox> minicore disables some uneed features like mysql db, threads, sockets etc etc etc <GreenBox> mapcaches uses it to load just the basic components Link to comment Share on other sites More sharing options...
