Peonso
Godly Member
- Joined
- Jan 14, 2008
- Messages
- 1,748
- Solutions
- 30
- Reaction score
- 1,529
I already removed it from client and also set the player event to return false. But still, player can open a container in the floor and through the parent container arrow that appears in container window reach the "browse field container".
I thought about 2 possible solutions (without the need to rewrite everything to totally remove it). First, don't ever create the browse field container, so there will be no parent container to another container in the floor. Or second, if the parent container is a browse field container, don't send to the client information to add the parent container arrow to give access to the browse field container.
I tried to search stuff in game.cpp and container.cpp but couldn't identify the code that handle the stuff I pointed out. Any ideas?
otland/forgottenserver
otland/forgottenserver
otland/forgottenserver
otland/forgottenserver
I thought about 2 possible solutions (without the need to rewrite everything to totally remove it). First, don't ever create the browse field container, so there will be no parent container to another container in the floor. Or second, if the parent container is a browse field container, don't send to the client information to add the parent container arrow to give access to the browse field container.
I tried to search stuff in game.cpp and container.cpp but couldn't identify the code that handle the stuff I pointed out. Any ideas?
otland/forgottenserver
otland/forgottenserver
otland/forgottenserver
otland/forgottenserver