Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!
I understand what you mean but I need an example or a guide on how to do it ... I do it myself without any problems ... I would need a "base" and an explanation
I understand what you mean but I need an example or a guide on how to do it ... I do it myself without any problems ... I would need a "base" and an explanation
2. Spamming / Double post:
You may not repeat the same message multiple times. It is seen as spamming, and will be deleted. If you accidentally post the same content twice, report one of the duplicate posts so a moderator can delete or merge that post.
This also applies if you for example "bump" a thread.
I won't solve your question, that would requiere a lot of test and work, but I can guide you how to start building a solution.
First, I see you're requesting addons for an old client. You need to check for this void in protocolgame.cpp on your server sources
Code:
void ProtocolGame::sendOutfitWindow() <--- this void is related to the outfit window
You will see there's a clear difference between this two C++ codes. From this line AddOutfit(msg, currentOutfit); the code start changing. You will have to figure out how does the rest of the code from 8.60 repository works and which difference it has with Nostalrius. You will see this line
Code:
uint8_t addons;
if (!player->getOutfitAddons(outfit, addons)) {
continue;
Is related to player addons. This is a hint of what you should start searching and which posts have relation to this line. For example, search on google "if (!player->getOutfitAddons(outfit, addons)) otland" and you will see that the results start appearing. Try to descompose the source code and start searching for results. That will help you finding solutions instead of just bumping the thread.
I can tell you that protocolgame.cpp isn't the only file you will need to change from the sources, there's some editions you have to do, for example, on bool Player::getOutfitAddons at outfit.h and outfit.cpp. You will have to do a lot of search and see if you get a good result. Another example could be player.cpp in bool Player::canWear that refers if a player can wear an addon or not.
I won't solve your question, that would requiere a lot of test and work, but I can guide you how to start building a solution.
First, I see you're requesting addons for an old client. You need to check for this void in protocolgame.cpp on your server sources
Code:
void ProtocolGame::sendOutfitWindow() <--- this void is related to the outfit window
You will see there's a clear difference between this two C++ codes. From this line AddOutfit(msg, currentOutfit); the code start changing. You will have to figure out how does the rest of the code from 8.60 repository works and which difference it has with Nostalrius. You will see this line
Code:
uint8_t addons;
if (!player->getOutfitAddons(outfit, addons)) {
continue;
Is related to player addons. This is a hint of what you should start searching and which posts have relation to this line. For example, search on google "if (!player->getOutfitAddons(outfit, addons)) otland" and you will see that the results start appearing. Try to descompose the source code and start searching for results. That will help you finding solutions instead of just bumping the thread.
I can tell you that protocolgame.cpp isn't the only file you will need to change from the sources, there's some editions you have to do, for example, on bool Player::getOutfitAddons at outfit.h and outfit.cpp. You will have to do a lot of search and see if you get a good result. Another example could be player.cpp in bool Player::canWear that refers if a player can wear an addon or not.
thank you very much @ralke and I'm sorry for my mistake ... I was almost giving up ... your explanation motivated me to continue, thank you very much for taking the time to create this explanation!