Jump to content
TrinityCore

codeman3518

Members
  • Posts

    254
  • Joined

  • Last visited

  • Days Won

    39

Posts posted by codeman3518

  1. Well then tell me how they can be so fucked up if I redid everything from start, the only thing I didn't do was vmaps and mmaps but everything else is from the start and is fresh. The error sounds like it is coming from the dbc files but I did those fresh too so not sure if you say core from master is running great then there really is a problem somewhere not sure where. I am reinstalling the client too just to cover everything this time as well.

    I can ensure you I did everything properly this isn't my first time doing this. I agree though I cannot find anything code wise that this would be. I'm doing vmaps and mmaps now just to make sure everything is done from fresh build. I wonder is there a way to rebuild the gt folder in wow because it sounds like that is where the error is coming from since it is not from the dbc files, I am going to try and re-scan the client for changes or to force changes made to it.

    • Upvote 1
  2. 7 hours ago, whyamidead said:

    yes

    Wait you are using a different core, you are not using TC to make your own server that would be for one reason why you are not able to use vmaps correctly. You can't expect vmaps to work properly with a different core all the time with changes that are made. Not only that but you have to know there are so many updates and the core you are using is really really outdated.

  3. Okay then if that is the case then I can say for sure it is not seeing the server at all, which also tells me that it is not even seeing the login server or world server to even try to connect so now my questions lead me to have you even used the connection patcher to patch the client and if so are you sure you are running the right one, if you did patch the client are you running the patch client and not making the common mistake of running the normal client that is not patched because this is common when getting just the connected message and nothing else.

    If you are running the right client my next thing is are you sure you are able to connect to other things like MySQL to this VPS IP because something is not seeing the server at all because this is a common problem with the just connecting message. One thing for sure it is not seeing the server because normally if it sees the server you will either get the information you entered is either not correct, disconnected message, or the server is not secured for a connection.

  4. Wait are you saying when you hit connect after entering your information in all you get is connecting, you don't get any kind of error it just sits on connecting all the time it has to give something back after sitting there for a bit even on connecting. Are you even waiting long enough to get something back even after sitting on connecting for a bit because it has to timeout after 1 minute.

  5. 5 hours ago, CDawg said:

    Do eeet!! We need something to make sniffing easier.

    When I get time, Iv'e been piecing together the player map. I usually get about 10-15mins a day, due to real life.

    That is what worries me about starting projects is the time having to do it because of real life.

  6. On 5/30/2017 at 0:51 PM, labaouici said:

    So I tried to put in on a vps under linux to try, but even setting the portal with VPS IP it stay on connection, so I would like how to connect because I really don't see why it don't work (I open port 8087, 8088 for the world server).
    Thanks to read because I would really try what the TC Legion

    You said you open ports 8087, 8088 did you change your ports for some reason to a different number from what it was set to and why did you change them do you have more than one server is that why.  If you are running just one server then your ports should be 8085, 8086 for world server then for login you should have open ports 1119, and 8081 open for the login server.

    Now did you set your bnetserver.conf file where LoginRest has your external address and local address setup correctly because this is the most common problems when trying to connect to the server outside where the server is actually on.  Another common problem I have been seeing people doing is they are setting the external address to there localhost IP address and the localhost address being set to localhost when the realm is set to there local router address.

  7. 4 hours ago, CDawg said:

    Actually, it can get goofy and you do have to set the path manually for Linux users. (similar to Windows)

    I did have to export BOOST_ROOT=$HOME/boost_1_63_0. (idk, maybe it was me when I upgraded my boost :P )

    Fortunately for Linux users that CMake has a catch all process before compiling and finding out before you get half way into compiling your core and not spewing errors. I think there is a specific Boost version install that doesn't set within the registry correctly for Win users or If you install, reinstall, something gets goofy with Win users.

    Edit:

    Oh btw, when I remove the old boost directories, I get errors during the cmake process, even though it's looking at the newer version boost.

    An example: I have 3 directories boost_61/ boost_62/ and boost_63/, however when I remove 61 and 62 (old ones) cmake says it's using boost_63, but during the compile i still get 'cant find boost libraries'

    So I place them both back (61 and 62) and everything is fine. ¯\_(ツ)_/¯

    It's quite frustrating.

    Strange for me I did not have to set a thing when installing the server the paths were set, but I guess it is never the same.  That's a really strange problem you get when trying to remove the older versions of boost and yet it still sees the new version but yet again it still needs the older ones back before it lets you compile correctly.

    I guess each system has it's own problems when trying to set paths and compile correctly, the strange thing is I wasn't thinking I would have more problems with Linux then I did with windows but it was the other way around that got me.

  8. You need to set the IP in the config file bnetserver.conf this is the reason for the disconnects when using the master branch because of new settings for LoginRest not to mention the new port for master branch port 1119. The ports to be open are 8085, 8086, 1119, 8081. The things to change in the config file are, because I take it you are trying to connect outside where the server is, which even if you are not this should be set to the correct IP's. When you open the ports that I mention you will ensure that the ports are now open for 3.3.5 and for 7.2.0 this way you can connect to either one.

    LoginREST.ExternalAddress=xxx.xxx.xxx.xxx
    LoginREST.LocalAddress=xxx.xxx.xxx.xxx

    • Upvote 1
  9. You can tell it is compiled on windows because you said you had to specified it to do it, if you were doing it for Linux it does not need to be specified to the path it does it automatically. Still strange even for windows that you had to specified I did not have to it did it for me.  Are you sure you installed the correct ones in the right paths without changing anything

    • Upvote 1
×
×
  • Create New...