[DiscordArchive] Anyone know of a go-to place to add additional races to my clean 3.3.5a build?
[DiscordArchive] Anyone know of a go-to place to add additional races to my clean 3.3.5a build?
Original source
Anyone know of a go-to place to add additional races to my clean 3.3.5a build?
rektbyfaith
10-25-2023, 04:58 PM #1Archived author: Rubycomputer • Posted: 2023-10-25T16:58:24.916000+00:00
Original source
Anyone know of a go-to place to add additional races to my clean 3.3.5a build?
Original source
It's not as easy as just to add them, like a really quick way of doing it. It requires a lot of core, dbc and client changes. I would suggest Googling for some information on adding custom races to the client and move from there. I'm sure there are guides for adding it to TrinityCore and with that you could adapt it for AzerothCore. Another thing to look at is https://github.com/heyitsbench/mod-worgoblin and https://github.com/heyitsbench/mod-arac for ideas.
rektbyfaith
10-25-2023, 06:37 PM #2Archived author: Revision • Posted: 2023-10-25T18:37:32.774000+00:00
Original source
It's not as easy as just to add them, like a really quick way of doing it. It requires a lot of core, dbc and client changes. I would suggest Googling for some information on adding custom races to the client and move from there. I'm sure there are guides for adding it to TrinityCore and with that you could adapt it for AzerothCore. Another thing to look at is https://github.com/heyitsbench/mod-worgoblin and https://github.com/heyitsbench/mod-arac for ideas.
Original source
thank you
rektbyfaith
10-25-2023, 07:45 PM #3Archived author: Rubycomputer • Posted: 2023-10-25T19:45:28.033000+00:00
Original source
thank you
Original source
i found the issue finally,
for some reason the server doesnt like the localhost in the realmlist table, i changed it to the actual adress within the network which fixed it
it works as long as im connecting from within the network with the localhost adress tho but it doesnt when connect from outside of it
rektbyfaith
10-25-2023, 08:56 PM #4Archived author: DukeSmile • Posted: 2023-10-25T20:56:13.438000+00:00
Original source
i found the issue finally,
for some reason the server doesnt like the localhost in the realmlist table, i changed it to the actual adress within the network which fixed it
it works as long as im connecting from within the network with the localhost adress tho but it doesnt when connect from outside of it
Original source
Copy pasta from the past:
> `localAddress` is the local LAN IP. the way the auth server knows whether to hand the client this IP or not is by checking the `localSubnetMask`. If you know anything about networking, it's using this mask to determine how big the "LAN" is, so it knows which client IPs it should provide the LAN IP to.
>
> So if I had a `localAddress` of `192.168.0.25` and a `localSubnetMask` of `255.255.0.0`, any client coming from an IP in the range `192.168.0.0 - 192.168.255.255` woud be given the `localAddress` to connect to.
>
> As you may have guessed, anything OUTSIDE that range will get the `address` IP instead.
>
> Side note: you may use DNS names for the `localAddress` and `address` fields, but they will be resolved by the server and not by the client. I personally use `whoami.akamai.net` for my `address` field, which will resolve to whatever public IP is being used to reach the Akamai DNS server.
rektbyfaith
10-25-2023, 09:10 PM #5Archived author: KJack • Posted: 2023-10-25T21:10:45.828000+00:00
Original source
Copy pasta from the past:
> `localAddress` is the local LAN IP. the way the auth server knows whether to hand the client this IP or not is by checking the `localSubnetMask`. If you know anything about networking, it's using this mask to determine how big the "LAN" is, so it knows which client IPs it should provide the LAN IP to.
>
> So if I had a `localAddress` of `192.168.0.25` and a `localSubnetMask` of `255.255.0.0`, any client coming from an IP in the range `192.168.0.0 - 192.168.255.255` woud be given the `localAddress` to connect to.
>
> As you may have guessed, anything OUTSIDE that range will get the `address` IP instead.
>
> Side note: you may use DNS names for the `localAddress` and `address` fields, but they will be resolved by the server and not by the client. I personally use `whoami.akamai.net` for my `address` field, which will resolve to whatever public IP is being used to reach the Akamai DNS server.