summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHello=) <hello@themanaworld.org>2024-07-14 14:49:39 +0300
committerHello=) <hello@themanaworld.org>2024-07-14 14:49:39 +0300
commit43bf4d6d3b9252017a34e197ceea6f647a30c3de (patch)
treee260fdf4ba3dc7342be27004edaa914a052195f1
parent02aa5d0821a6d98f4192e78429dfd2ab302fb5fc (diff)
downloadserverdata-43bf4d6d3b9252017a34e197ceea6f647a30c3de.tar.gz
serverdata-43bf4d6d3b9252017a34e197ceea6f647a30c3de.tar.bz2
serverdata-43bf4d6d3b9252017a34e197ceea6f647a30c3de.tar.xz
serverdata-43bf4d6d3b9252017a34e197ceea6f647a30c3de.zip
This commit lands workaround on MM weight problem.
Naive approach using stats failed. But even more direct way works. This sets MaxWeight on MM login to 10 000 000 aka 10 000 kg aka 10 tons. I think 10 tons "should be enough for everyone". I've actually tested it works by heavily loading ManaMarket replica on local server with itens.
-rw-r--r--world/map/npc/functions/global_event_handler.txt1
1 files changed, 1 insertions, 0 deletions
diff --git a/world/map/npc/functions/global_event_handler.txt b/world/map/npc/functions/global_event_handler.txt
index 5274fa05..6664da36 100644
--- a/world/map/npc/functions/global_event_handler.txt
+++ b/world/map/npc/functions/global_event_handler.txt
@@ -20,6 +20,7 @@ OnPCLoginEvent:
callfunc "VaultLogin"; // Mirror Lake Protocol biddings
callfunc "VaultLogout"; // Clean some stuff, to be safe
// add more here
+ if (strcharinfo(0, BL_ID) == "ManaMarket") set MaxWeight, 10000000; // Let ManaMarket bot to carry 10 tons
set @login_event, 2;
end;