Jump to content

mcbigmac

Members
  • Posts

    1,245
  • Credits

  • Joined

  • Last visited

  • Feedback

    0%

About mcbigmac

Profile Information

  • Current Mood
    Angry
  • Gender
    Not Telling
  • Country
    Afghanistan

Recent Profile Visitors

2,037 profile views

mcbigmac's Achievements

Newbie

Newbie (1/16)

1

Reputation

14

Community Answers

  1. DB errors if i remember correctly - that makes cached go hicky hicky once sending packets to l2server upon startup. Verify ALL fields have correct data in the value-types their declared for said pledges in ALL pledge tables. Nothing to do with internal network\memory. ...but i can only check over a week from now so.
  2. Can't check now but sounds right ish. out and not able to check source until 8th of august. Fishing stacking should also be fixed.
  3. For you because your unable to quickly build it or build it within meaningful timeframe. Doesn't mean your everyone. And you can't build a daemon out of scripts, base was always GF with HF until the private HFs started popping up. It's known HF exists, freya never existed outside NCSoft. And rumours state Freya-scripts leaked by human error in NC West. By pure public servers we know HF,GOD, Tauti, Lindvior,Glory, Ertheia is in the "private circle" hands. That should tell you someone has had long term and almost permanent access to NC or a partner with NCSoft contracts (Take a wild geuss which). Which perhaps still exists today perhaps still not (slowdown lately of "new chronicle servers") - but since HF someone more or less had access to build this concession of leaks per chronicle with almost clockwise swiss perfection to run public servers in N-1 fashion against retail updates. The ONLY reason GF leaked is because those same people physically let go of the files - since it was probably a one-off sale at that given time. Yet here we are years later and nothing new has leaked since then. Geuss all you want - but all logic dictates the ship that started GF has been severely tightened and is very well managed up until now. One can assume that means their revenue ambitions\demands still follow suit - and until that changes public will see nothing.
  4. No, it will not. Because you have not understood how it leaks in the first place - nor that "eventually" is a very ambigious and pointless term to use here. (And funny how you skip H5, when will it leak mister?). It does matter when something publicly leaks or when something gets in hand privately to people. A GOD++ leak now is worth alot to the right people - but of course not as much as when you were solo'ing the market with 3-4 live servers globally with the files. Scripts are worthless alone to anyone except l2j people - it's too much work to do GF>up (hell even H5>Up - if your one of the few people with the physical files) for what will most likely be chum change compared to invested time. ...GOD++> up however sets a base that's entirely workable in a decent timeframe.
  5. ...when you have the bins of any god++ let the right people know ;)
  6. 1. Yes. And L2npc can pause-stop execution of active instances if no player near. In c4 its a switch in menu - whereas its more automated in GF. 2. Yes 3. Yes - although coNfirmed that iN last post last answer.
  7. 1. No. Go see 1. of previous post - and research l2npc for true definitions. Anything in native handlers can be considered fairplay - rest should be tested. 2. Is frintezza native ? - no it's custom-made. 3. Yes. 4. GG is a namespace, not a variable, event or similar. call_super does exactly what it says, calls the superceeding class, no more no less. 5. All living used objects need to be declared in the handler. How logic specificly works\requires - you can find in l2npc. I do not recall the side-effects of not declaring - but there are some- While the code may technicly execute to your desired effect. (probably memory leaks and wastage for cleanup when handler is done). 6. Oh look, r8\r9 is not used anywhere - where are they? Dumb question. .text:000000000082CEB0 sub_82CEB0 proc near .text:000000000082CEB0 push rbp .text:000000000082CEB2 sub rsp, 20h .text:000000000082CEB6 mov rbp, rdx .text:000000000082CEB9 lea rcx, [rbp+48h] .text:000000000082CEBD call sub_402930 .text:000000000082CEC2 add rsp, 20h .text:000000000082CEC6 pop rbp .text:000000000082CEC7 retn .text:000000000082CEC7 sub_82CEB0 endp
  8. If you actually viewed AI you'd see it make sense. i0 to i9 are empty integer storage registers for integer vars c is the same for creatures. _list are list variables of creatures\members used to store run thru checks for quests when a party is the last attacker. code_info is related as well. The actual logic for why things are coded this way i forget - but going thru AI should reveal why the need for temporary storage vars are needed. I believe but i can't remember for sure - it's used for proper threading\handling due to l2npc lag being a very real thing when badly coded handlers are executed 100 times per second. This is especially true for itemgiving \ dropping commands that go back to l2server with interpacket communication. If no logic is found - then l2npc is always there to research why specificly. Either way following their syntax\logic for new quests is advised.
  9. 1. No, leaked files generally do not contain guides on how to optimally abuse their intellectual propety. 2. You have the programs that use them, go research. ...but should be a list of a function events and handlers in this forum somewhere for both GF & C4, most are self explanatory. 3. See above. 4. myself is the AI instance\class where code is executed, which doesn't always mean a NPC instance but could be a Makerinstance also. 5. A CSharedCreatureData struct within AI class, for npc instances. 6. Yes, see 2. 7. Load time, not run time. 8. If declared properly, yes. 9. See above. 10. A watch list, most likely used with l2logd. Fairly pointless for most private servers. Probably monitoring measures if large quantity or rare items suddenly explode within the game world. 11. Same as skill_pch - just with different data. 12. Same as above, with quest.
  10. I'm amazed some of you still fall into the same trap he lays out all time - and then he manages to do what you claim he has not done for his own server. When someone preys on your logical attention to achieve his objective - just don't give "it" the satisfaction ;) DopeAgent: Consider the statement "People don't want to play the same anymore". The ask yourself what has been given the last few years - since nothing new is offered... and are you offering anything else? If we look at what's given it's predominantly the following: C6, GF, Freya,H5. So lets ask the question - why do people play L2 still? Is it because they like the game, the nostalgia - or is it because they want to play L2 but completely re-designed? That's why your plan will fail. People still want to play - but no-one is just offering the right version because quite frankly no one has the time or ability to deliver it. Deliver what they want, build that - not a crazy mutant of what's already offered in the name of "freshness". You saw a shortcoming that's been in the market for years - but instead of listening to the market...you created your own fix\cure that YOU think will "rock". People want to play L2 - not Lineage Legends 2 Dota Version X or similar ;)
  11. Yea that doesn't look suspiciously alot like a reseller - using GoD as bait...AT ALL. Nope, all smooth legit here.
  12. Several editors do this, including HFs + Petre's. If one can find them still.
×
×
  • Create New...