Max New Monsters
Re: Max New Monsters
I'll teach you Reck... listen to me. I rule. :)
Re: Max New Monsters
Originally posted by Dark
hehehe I was on a board that changed the rats to Bin Ladins
and other stuff to dirty Afgans etc
I played there for a while. Can't remember the name tho.
hehehe I was on a board that changed the rats to Bin Ladins
and other stuff to dirty Afgans etc
I played there for a while. Can't remember the name tho.
Re: Max New Monsters
Port Orchard, where is that?
Re: Max New Monsters
Originally posted by Ray Dillyo
Port Orchard, where is that?
About 45 minutes form seattle
Port Orchard, where is that?
About 45 minutes form seattle
Re: Max New Monsters
Originally posted by BlackHaze
I played there for a while. Can't remember the name tho.
Me too. From what I gather, there's more than one board like that. The edits were done by a lowlife named Jade. She can't keep a board up worth a damn, so her and a few of her friends keep bringing up new ones with the same edits. Word of warning... The reason I say she's a lowlife is that she's the reason Sinister Urge got hacked a while back. Dxpac had an account on one of those boards and her assclown friend looked up his password on there and used it to log onto his op account on Sinister... Planted a trojan in his system and everything. So the wannabe hacker and Jade the wannabe best hexer ever tried to take over. Nasty little troll. So word of warning to everybody that's ever been on one of those boards... whatever password you used there, retire it and retire it now.
I played there for a while. Can't remember the name tho.
Me too. From what I gather, there's more than one board like that. The edits were done by a lowlife named Jade. She can't keep a board up worth a damn, so her and a few of her friends keep bringing up new ones with the same edits. Word of warning... The reason I say she's a lowlife is that she's the reason Sinister Urge got hacked a while back. Dxpac had an account on one of those boards and her assclown friend looked up his password on there and used it to log onto his op account on Sinister... Planted a trojan in his system and everything. So the wannabe hacker and Jade the wannabe best hexer ever tried to take over. Nasty little troll. So word of warning to everybody that's ever been on one of those boards... whatever password you used there, retire it and retire it now.
Re: Max New Monsters
You can't make more than 1010 monsters because they don't regen? Or is there some kinda file size check I don't know about? Or why? ;)
Re: Max New Monsters
Originally posted by Tsunami
You can't make more than 1010 monsters because they don't regen? Or is there some kinda file size check I don't know about? Or why? ;)
the dll is limiting the number of monsters that it checks to regen to the first 1010 monsters.
You can't make more than 1010 monsters because they don't regen? Or is there some kinda file size check I don't know about? Or why? ;)
the dll is limiting the number of monsters that it checks to regen to the first 1010 monsters.
Re: Max New Monsters
That sounds like it would be easy enoguh to fix, but I am assuming it's not since that its not fixed. Couldn't one just edit the dll check that deals with the lim?? I dunno alot about it, so i might be talking crazy;).
Re: Max New Monsters
Originally posted by Durin
That sounds like it would be easy enoguh to fix, but I am assuming it's not since that its not fixed. Couldn't one just edit the dll check that deals with the lim?? I dunno alot about it, so i might be talking crazy;).
no, it's not that easy at all. below is what assembly code looks like. this is just a small snippet of the tens-of-thousands of lines of code. this is also NOT the mud dll, it's actually NMR (for legal reasons). but this gives you a sense on what it looks like. people are trying to learn and get it fixed though.
:004198A0 1E push ds
:004198A1 3C28 cmp al, 28
:004198A3 17 pop ss
:004198A4 44 inc esp
:004198A5 301F xor byte ptr [edi], bl
:004198A7 47 inc edi
:004198A8 3524412F1E xor eax, 1E2F4124
:004198AD 3B29 cmp ebp, dword ptr [ecx]
:004198AF 183D29186245 sbb byte ptr [45621829], bh
:004198B5 3663443562 arpl dword ptr ss:[ebp+esi+62], eax
:004198BA 43 inc ebx
:004198BB 3460 xor al, 60
:004198BD 41 inc ecx
:004198BE 325E3F xor bl, byte ptr [esi+3F]
:004198C1 305C3D2E xor byte ptr [ebp+edi+2E], bl
:004198C5 5B pop ebx
:004198C6 3C2D cmp al, 2D
:004198C8 5A pop edx
:004198C9 3B2C58 cmp ebp, dword ptr [eax+2*ebx]
:004198CC 392A cmp dword ptr [edx], ebp
:004198CE 59 pop ecx
:004198CF 3A2B cmp ch, byte ptr [ebx]
:004198D1 5B pop ebx
:004198D2 3C2D cmp al, 2D
:004198D4 5C pop esp
:004198D5 3D2E5C3D2E cmp eax, 2E3D5C2E
:004198DA 5B pop ebx
:004198DB 3C2D cmp al, 2D
:004198DD 59 pop ecx
:004198DE 3A2B cmp ch, byte ptr [ebx]
:004198E0 56 push esi
:004198E1 392A cmp dword ptr [edx], ebp
:004198E3 57 push edi
:004198E4 40 inc eax
:004198E5 31543F30 xor dword ptr [edi+edi+30], edx
:004198E9 5E pop esi
:004198EA 47 inc edi
:004198EB 37 aaa
:004198EC 6B514168 imul edx, dword ptr [ecx+41], 00000068
:004198F0 4A dec edx
:004198F1 395C3A2A cmp dword ptr [edx+edi+2A], ebx
:004198F5 5D pop ebp
:004198F6 37 aaa
:004198F7 256B402F8B and eax, 8B2F406B
:004198FC 5B pop ebx
:004198FD 49 dec ecx
:004198FE A26E5DA971 mov byte ptr [71A95D6E], al
:00419903 5E pop esi
:00419904 A5 movsd
:00419905 6A57 push 00000057
:00419907 BC7F6BDB9C mov esp, 9CDB6B7F
:0041990C 88CE mov dh, cl
:0041990E 8D78A1 lea edi, dword ptr [eax-5F]
:00419911 64 BYTE 064h
That sounds like it would be easy enoguh to fix, but I am assuming it's not since that its not fixed. Couldn't one just edit the dll check that deals with the lim?? I dunno alot about it, so i might be talking crazy;).
no, it's not that easy at all. below is what assembly code looks like. this is just a small snippet of the tens-of-thousands of lines of code. this is also NOT the mud dll, it's actually NMR (for legal reasons). but this gives you a sense on what it looks like. people are trying to learn and get it fixed though.
:004198A0 1E push ds
:004198A1 3C28 cmp al, 28
:004198A3 17 pop ss
:004198A4 44 inc esp
:004198A5 301F xor byte ptr [edi], bl
:004198A7 47 inc edi
:004198A8 3524412F1E xor eax, 1E2F4124
:004198AD 3B29 cmp ebp, dword ptr [ecx]
:004198AF 183D29186245 sbb byte ptr [45621829], bh
:004198B5 3663443562 arpl dword ptr ss:[ebp+esi+62], eax
:004198BA 43 inc ebx
:004198BB 3460 xor al, 60
:004198BD 41 inc ecx
:004198BE 325E3F xor bl, byte ptr [esi+3F]
:004198C1 305C3D2E xor byte ptr [ebp+edi+2E], bl
:004198C5 5B pop ebx
:004198C6 3C2D cmp al, 2D
:004198C8 5A pop edx
:004198C9 3B2C58 cmp ebp, dword ptr [eax+2*ebx]
:004198CC 392A cmp dword ptr [edx], ebp
:004198CE 59 pop ecx
:004198CF 3A2B cmp ch, byte ptr [ebx]
:004198D1 5B pop ebx
:004198D2 3C2D cmp al, 2D
:004198D4 5C pop esp
:004198D5 3D2E5C3D2E cmp eax, 2E3D5C2E
:004198DA 5B pop ebx
:004198DB 3C2D cmp al, 2D
:004198DD 59 pop ecx
:004198DE 3A2B cmp ch, byte ptr [ebx]
:004198E0 56 push esi
:004198E1 392A cmp dword ptr [edx], ebp
:004198E3 57 push edi
:004198E4 40 inc eax
:004198E5 31543F30 xor dword ptr [edi+edi+30], edx
:004198E9 5E pop esi
:004198EA 47 inc edi
:004198EB 37 aaa
:004198EC 6B514168 imul edx, dword ptr [ecx+41], 00000068
:004198F0 4A dec edx
:004198F1 395C3A2A cmp dword ptr [edx+edi+2A], ebx
:004198F5 5D pop ebp
:004198F6 37 aaa
:004198F7 256B402F8B and eax, 8B2F406B
:004198FC 5B pop ebx
:004198FD 49 dec ecx
:004198FE A26E5DA971 mov byte ptr [71A95D6E], al
:00419903 5E pop esi
:00419904 A5 movsd
:00419905 6A57 push 00000057
:00419907 BC7F6BDB9C mov esp, 9CDB6B7F
:0041990C 88CE mov dh, cl
:0041990E 8D78A1 lea edi, dword ptr [eax-5F]
:00419911 64 BYTE 064h