-
2026 staff recruitment is open! Check it out and consider applying!
Search results
-
C++ Healing Mana/Health appear very separate
I'm no expert, but I'm pretty sure that's a client-side issue. Idk what client you're using, but judging by the sprites it's higher than 8.0, which is when what you are looking for changed, specifically this part: Correct me if I'm wrong, but from my knowledge this can only be done in later... -
Solved Storage Issue (Max HP) [OTX3]
Thanks @Xeraphus I will try it. EDIT seems to work perfectly, thanks a million. -
Solved Storage Issue (Max HP) [OTX3]
I need to reopen this, as there is a new issue i encountered. All characters on my account are fine, but when I use a different account the character instantly dies when it logs in. I guess I don't enough about storages to see what the problem is I thought it was working for all players -
10+ player in screen = spells exhaust
Read the rules before you post man please we can't help you if we don't know what version/distribution you are using. Thank you. -
C++ Enable Monster Friendly Fire [OTX3]
Thank you for your reply. I will check it now. Edit: that was it. Thank you. Removing the following lines solved the issue: } else if (attacker->getMonster()) { const Creature* targetMaster = target->getMaster(); if (!targetMaster ||... -
C++ Enable Monster Friendly Fire [OTX3]
I'm working with OTX3, 7.72 distribution. Normally in version 7.72 monster's spells should hurt each other. However, this distribution is a downgrade and that aspect was not changed. I checked "bool Game::combatChangeHealth" in game.cpp and it seems that nothing is blocking creature vs... -
Solved Monster Attack Minimum Interval (Source Editing) [OTX3]
Solved. int32_t EVENT_CREATURECOUNT needed to be changed as well (from 10 to 1). Recompiled and tested. -
Solved Xampp problem with port 80 being used
This. I have had WAY less problems with Uniserver. -
Solved Monster Attack Minimum Interval (Source Editing) [OTX3]
Bump and update, it is not that line of code. Changed it and recompiled, no effect. Still not sure where to change this. -
help with this script please!
Please read the rules for the support board before you post so we know how to help you. Rules for the Support board -
-
Complete 8.0 map etc, but missing the exe file.
You need to recompile the sources to make a new .exe file. -
Complete 8.0 map etc, but missing the exe file.
Do you still have the source files? Because you definitely can not run any random .exe file. -
Solved Monster Attack Minimum Interval (Source Editing) [OTX3]
I'm looking for the file in the sources where the minimum monster attack interval is determined. In newer versions of Tibia, there is a forced cooldown on all of their (monster) spells. In older versions of Tibia, there was no minimum cooldown between spells. A Minotaur Mage could stand there... -
Solved Corpse Ownership [OTX3] (Compiling)
Solved by blocking out the following line of code in actions.cpp /* uint32_t corpseOwner = container->getCorpseOwner(); if (container->isRewardCorpse()) { //only players who participated in the fight can open the corpse if... -
Solved Corpse Ownership [OTX3] (Compiling)
Yes I reported it. I have been instructed how to fix it but my visual studio is not working so I can not test it yet. -
Solved Corpse Ownership [OTX3] (Compiling)
Been 24, giving this a bump, still can't solve it. -
Solved Corpse Ownership [OTX3] (Compiling)
I've discovered an issue in this distro I'm using (OTX Server 3 - Based on TFS 1.2 (7.6/7.72 - 8.6 - 8.70/71 - 10.96)) with corpse ownership and I can't seem to solve it. First of all, I don't want to have "corpse ownership" be in the game at all (I'm working with version 7.72). But the problem... -
Solved Lifesteal Melee Weapon [TFS 1.2]
I'm getting the same issues as OP, healing is inconsistent even though I set chance to 100% or remove the chance function altogether. -
Solved Storage Issue (Max HP) [OTX3]
Sorry man I had a hard time explaining the problem the way I worded it made it kind of confusing. But question though, if I just addHealth to maximum like in the way you just posted, won't that mean that anytime someone relogs they will just get max HP?