nanakiwurtz Posted January 1, 2015 Group: Members Topic Count: 81 Topics Per Day: 0.02 Content Count: 1654 Reputation: 583 Joined: 08/09/12 Last Seen: January 14, 2020 Share Posted January 1, 2015 December Digest 2014The following digest covers the month of December, 2014. Staffs Changes None Development Highlights Major updates: Renewal Cast updated (45fdf32) Update libconfig to 1.4.9 (78bcd82) Added new tool 'update.pl', a small perl script to auto git update and apply db update in sql (af0da61) Doubled the hostname length (3f912f4) Item DB updated up to kRO 2014-10-29, along with some View IDs addition and fixes (fe56ff0) Bug Fixes: Corrected `guid` Implementation of Item Package (5ce8055) Fixed Item Recovery Rate (071cb76) Fixed minor bug on THQS_ChatingNPC.txt script (01baeec, 9302969) Gravitational Field will now work as official servers (861112b) Fixed range of Ganbantein and Gravitational Field (bugreport:4897) Fixed that in renewal, weapons with a range of 2 and 3 did depend on DEX instead of STR (Issue:#129) Fixed Sura Job Quest event trigger bug (Issue:#151) Fixed Spiritual Bestowment skill bug (bugreport:4340) Fixed fast movement animation when disguised and Devotion skill behaviour (14f6654) Fixed GCC 4.9 plugin needed to handle lto object (629af3b) Fixed Prestige skill bug (Issue:#164) Fixed issue related with libconfig 1.4.9 by removing yacc and bison file (3625aaa) Added an error message for movenpc to report which NPC was not found (4e3a940) Fixed some item's "English Name" (ba817e8) Fixed small typo in 'npc/events/christmas_2005.txt' (d49f21a) Fixed some hardcoded script values to MAX_LEVEL (Issue:#161) Statistics 4 authors have pushed 10 commits during this period. On master, 10 files have changed. There have been 437 additions and 381 deletions. There are 7 merged Pull Requests and 1 Proposed Pull Requests. There are 9 created Issues and 2 Closed Issues. Show your support to rAthena by submitting your Issue or Pull Requests! The rAthena community would like to say "Happy New Year 2015!!" 3 Quote Link to comment Share on other sites More sharing options...
Cydh Posted January 1, 2015 Group: Developer Topic Count: 153 Topics Per Day: 0.04 Content Count: 2285 Reputation: 745 Joined: 06/16/12 Last Seen: June 30, 2023 Share Posted January 1, 2015 Happy year end 2014 Digest! pertamax diamankan, turun dari 10500 jd 9900, premium 8500 jd 7600 Quote Link to comment Share on other sites More sharing options...
Patskie Posted January 2, 2015 Group: Members Topic Count: 50 Topics Per Day: 0.01 Content Count: 1702 Reputation: 238 Joined: 09/05/12 Last Seen: Sunday at 07:46 PM Share Posted January 2, 2015 Great year-end updates! Keep up the good work rAthena !! Quote Link to comment Share on other sites More sharing options...
Cydh Posted January 3, 2015 Group: Developer Topic Count: 153 Topics Per Day: 0.04 Content Count: 2285 Reputation: 745 Joined: 06/16/12 Last Seen: June 30, 2023 Share Posted January 3, 2015 I just hope people read this off-topic post! Please don't use "latest" when reporting something, please give us the commit ID - thank you - 2 Quote Link to comment Share on other sites More sharing options...
nanakiwurtz Posted January 4, 2015 Group: Members Topic Count: 81 Topics Per Day: 0.02 Content Count: 1654 Reputation: 583 Joined: 08/09/12 Last Seen: January 14, 2020 Author Share Posted January 4, 2015 Please don't use "latest" when reporting something, please give us the commit ID - thank you - I thought I have posted exactly the same thing like yours, but it looks like my post has failed to reach the board because of the CF check, ah well.. I was thinking the same, for example if there's a user named 'A' posted on the GitHub Issue and wrote "I have an error on latest hash", but then a dev pushed another commit(s), it means that A's latest hash won't be the latest anymore, isn't it? Quote Link to comment Share on other sites More sharing options...
Cydh Posted January 5, 2015 Group: Developer Topic Count: 153 Topics Per Day: 0.04 Content Count: 2285 Reputation: 745 Joined: 06/16/12 Last Seen: June 30, 2023 Share Posted January 5, 2015 Please don't use "latest" when reporting something, please give us the commit ID - thank you - I thought I have posted exactly the same thing like yours, but it looks like my post has failed to reach the board because of the CF check, ah well.. I was thinking the same, for example if there's a user named 'A' posted on the GitHub Issue and wrote "I have an error on latest hash", but then a dev pushed another commit(s), it means that A's latest hash won't be the latest anymore, isn't it? exactly Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.