Jump to content

AGUZZTYN

Inactive Member
  • Posts

    17
  • Joined

  • Last visited

  • Feedback

    0%

Posts posted by AGUZZTYN

  1. There must be something wrong (or missing), either within the file you were editing or other resources. The error says there is a problem with a string, but many times these errors are a byproduct of a much larger problem.

    I feel like I'm always suggesting the same here on the forums, but I digress. If you can't fix them, go back to the files you edited, restore them to a previous working state and start working from there.

    Perhaps you could give us more detail on what you were working (or even share a fragment of code)? We need more information...

  2. Could you please tell us what was the last thing you changed?

    Could be many things: protos, a python script.

    Can you show us your client syserr?

     

    Edit: nevermind, just read the whole post lol. There must have been some change in your client files then. I'd suggest recompiling client binary and replacing root, locale and uiscript from your latest working backup

  3. On 8/4/2017 at 9:28 PM, enzi said:
      Reveal hidden contents

    SYSERR: Aug  5 09:30:05 :: Process: SEQUENCE 29bb3c00 mismatch 0xaf != 0x64 header 254
    SYSERR: Aug  5 09:30:05 :: Process: SEQUENCE_LOG [UNKNOWN]-------------
        [254 : 0xaf]

    This is one annoying error, right here.

    In my case there was a problem with my mob_proto.

    I'd suggest revising your mob_names.txt also, as they are inconsistent and contain many bugs when it comes to GOTO and WARP names...

  4. I know it's a rather old topic, but I'll leave a reply anyways, for the future.

    This problem is related to mob_proto and how your client/server handles mob types. Did you add/delete mob types in ProtoReader.cpp?

    Also, latest mob_protos changed horses' type from NPC to HORSE. If you have updated your mob_proto recently you could try reverting those changes, if present..

  5. Hi guys!

    Let me explain you. I've been dealing with this problem for months and have not found yet a glimpse of where this problem comes from, so thats why I'm asking you guys :)

    My intention is to run a 40k server from my laptop, which has freebsd installed on it. The main problem is that, when I run 34k or 40k server files on it I'm able to connect to the server but it freezes after a couple of seconds of play. I can enter the game, past the character select screen, but if I move ingame a few metres or hit a few dogs the connection just... dies. What confuses me is that if I use the same server configuration on 2089 files it works flawlessly :wacko:

    Also, the same setup on VirtualBox with these 34k and 40k files work without further problems. That being said, it looks like it is something specific to those server files or a hardware issue. But from what I tested its more likely to be the former since, even while my laptop only has 1GB of RAM, I've been able to run these 40k files on VirtualBox with 256MB.

    Technical information:

    Laptop: Intel Atom, 2 cores @ 1.56GHz / 1GB DDR3 RAM / FreeBSD 10.3 with 18GB of free space and 2GB swap. Default gateway: 192.168.2.1. Ipv4 address: 192.168.2.6. External IP: 181.197.XXX.XX. No need to add BIND_IP on CONFIG files under 2089 files (and it just works), neither in 34k and 40k (and server runs) but the problem arises. I tried several times adding my Ipv4 address, but had no success. If I try to add my external IP I get the infamous "socket_tcp_bind: tcp_socket: Can't assign requested address". All ports have been properly forwarded via router configuration. I don't have to use PortMap so as to connect to the servers. DMZ available.

    Ask me anything and I will post the information you need in order to solve this issue. I would love to see this problem solved :wub: help guys!

    example1.jpg

    example2.jpg

×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.