Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/27/13 in all areas

  1. Poring Slots << Any Upper Headgear random enchanter NpC >> << PvP with board message and number of users inside room >> << Item with Endower Function >> << @cashpoint command >> << Make Every MvP Monster drop a Specific Item >> headchant.txt playervsplayer.txt Cashpoint Command Guide.patch gcoin.txt catalyzer.rar
    1 point
  2. Hi guys! Check out my Free Thor Patcher skin here! http://rathena.org/board/files/file/3048-chiaki-thor-patcher-skin-1/ It's free! with the config file and PSD file
    1 point
  3. LOL In Indonesia, wkwkwkwkwk means hahahaha
    1 point
  4. you must add it inside the grf with the right path.try my skin at my signature to make one.just pack it inside a grf
    1 point
  5. Refer to Basic_Scripting - <TAB> script <TAB> Sample <TAB> -1,{ OnPCKillEvent: if ( strcharinfo(3) == "your map" ) { if ( attachrid( getcharid( 3, strcharinfo( 0 ) ) ) ) { if ( Hp && ( Hp != MaxHp ) ) percentheal 100,100; } } }
    1 point
  6. Try : - script Sample -1,{ OnPCKillEvent: if ( strcharinfo(3) == "your map" ) { if (attachrid(getcharid(3, strcharinfo(0)))) { if ( Hp && ( Hp != MaxHp ) ) percentheal 100,100; } } }
    1 point
  7. no, about items in your server are not depend on the KRO, its depend on your version of your server emulator, but without the latest KRO, the latest items wont show, and maybe will caused GE. I think data v4.0 is the latest, so maybe the latest items are available.
    1 point
  8. Well, from my understanding the "MAIN" reason would actually be the way each engine handles DML sessions. I honestly can't say InnoDB lacks in the performance department in regards to large amounts of data. However, it does allow for multiple/parallel DML sessions, of which would be a negative effect on rA. MyISAM will currently limit those DML sessions to run 1 by 1, meaning that the rA system, only has to process one of those at a time to bring forth an update, thus reducing the strain on the server and lag in total. Then when you compare how scripters use SQL to store information, you'll see most of it is called when player performs action X. And since we can have anywhere from 1 - 1000+ players at any given time, you have to take into consideration that each of those players could trigger action X at once. Or in the instance where action X is killing any monster and updating the data to log how many kills... Well, what happens when a 10 wizards in 10 different parties kill 100 monsters each with SG? The answer is you'll have 1,000 indivisual queries to run, now if all 1,000 of those run at once, then rA systems will suffer until they are done and you'll experience lag on your server. But if we were to use MyISAM it'd run all 1,000 1 by 1, meaning the lag experienced should only be that of Internet connection / cpu stats. Again, this is all from my understanding. So I should say that, certain DBs should allow for InnoDB while most that perform at a more frequent rate, like that in my example or saving all the characters, should be handled by MyISAM.
    1 point
  9. MylSAM engine provides simplicity, use less system resources and is much more faster with huge amounts of data. MylSAM doesn't allow to perform more than one operation at same time (Table Transaction Global Mutex), poor data integrity and security. InnoDB is the best choice where all data is correlated (PK/FK and FN) ,indexed and where have chance to perform one more operation at the same time. This provides data integrity and security. InnoDB use more system resources and have performance penalty with large amounts of data. Sry for bad english
    1 point
×
×
  • Create New...