Talendrys
getMaNGOS Staff-
Posts
706 -
Joined
-
Last visited
-
Days Won
30 -
Donations
0.00 GBP
Content Type
Profiles
Bug Tracker
Wiki
Release Notes
Forums
Downloads
Blogs
Events
Everything posted by Talendrys
-
That's fun
-
It would be nice to have the getmangos.sh script detecting the server repo into the source-path given by the end-user rather than assuming that the directory name is 'server'.
-
Experimental support added in https://github.com/mangoszero/server/pull/179
-
Fedora let the codename go, the source code cannot deal with this easily. As well, there is no such package manager as on some other distro using apt-get or aptitude. This support is currently blocked until some users running Fedora could give further support.
-
RHEL is a proprietary system, only an experimental support will be added.
-
Added in PR https://github.com/mangoszero/server/pull/175
-
Changed Status to Completed
-
Tracker issue to add Redhat support into the getmangos.sh installer.
-
@antz, these are the libraries that we do install if you check the pre-requisites box: build-essential linux-headers-<core version> autoconf automake cmake libbz2-dev libace-dev libace-<distribution dependant> libssl-dev libmysqlclient-dev zlib1g-dev Therefore, libtool must be added. Will do it shortly.
-
Tracker issue to add support of the debian distribution into the getmangos.sh installer.
-
Tracker issue to add support for Fedora releases in the getmangos.sh script.
-
Refactor linux tools to use a single installer accross all cores
Talendrys commented on Talendrys's bug in Archived Reports
Changed Status to Completed -
Refactor linux tools to use a single installer accross all cores
Talendrys commented on Talendrys's bug in Archived Reports
Fixed by https://github.com/mangoszero/server/pull/174 -
Actually, linux tooling are a set of 2 tools which are a bit incomplete: - lazymangos.sh which is dealing with user, third party tools and building. - getmangos.sh which is dealing with third party tools, building, installing and cloning. The idea is to get the best of bread by: - Removing lazymangos.sh from all the cores (starting by zero) and use only getmangos.sh as the main installer. Other features will be added in separate tracked-activities.
-
lazylinux.sh is not setting the proper database values
Talendrys commented on Talendrys's bug in Archived Reports
Changed Status to Completed -
lazylinux.sh is not setting the proper database values
Talendrys commented on Talendrys's bug in Archived Reports
Solved by this commit -
The lazylinux.sh script is not setting up proper values of the database connection causing improper startup of Mangos daemons.
-
Why not put it as invalid for the client or even hide it ? Offline seems using a flag for a non-foreseen usage.
-
Realm flag 40 for a classic realm throws a red warning
Talendrys commented on madmax's bug in Realm Daemon
[quote=madmax]Oh really? We should really make these things give an error that tells you what to use instead of 0x40 which i have no idea lol.[/quote] By the way, 0x40 is 64 (recommended, green). While 40 is the combination of 32 + 8 (New players + Unknown flag) but I think that new players flag is a blue recommended. And I would not say that the core needs to tell you to put something it doesn't know... however, you could read the documentation : [url]https://getmangos.eu/wiki/Reference%20Information/DB/realm/realmlist.md#realmflags[/url] ;-) -
Realm flag 40 for a classic realm throws a red warning
Talendrys commented on madmax's bug in Realm Daemon
I would suggest to implement JaNGOS Database structure for the realmlist table. In JaNGOS, you set 0 or 1 to flags instead of an integer which is then interpreted as an hexadecimal value for the game. Several other fields have exactly the same issue in the MaNGOS database: playerBytes, item_data, ... According to myself (and maybe others), it is actually a stupid idea to store an integer which has several flag meaning into the database (Especially whenever you can combine them). Database: `id` int(11) NOT NULL AUTO_INCREMENT COMMENT 'ID of the realm.', `name` varchar(32) NOT NULL DEFAULT '' COMMENT 'Name of the realm.', `address` varchar(32) NOT NULL DEFAULT '127.0.0.1' COMMENT 'Address of the realm, may be a name of an ip.', `port` int(11) NOT NULL DEFAULT '8085' COMMENT 'Listen port of the realm.', `fk_realmtype` int(11) NOT NULL COMMENT 'Foreign key to the Realm Type.', `fk_timezone` int(11) NOT NULL COMMENT 'Foreign key to the timezone.', `population` float NOT NULL DEFAULT '0' COMMENT 'Population calculated from (playerCount / maxPlayerCount * 2)', `maxPlayers` int(11) NOT NULL DEFAULT '1000' COMMENT 'The maximum number of players allowed on this realm.', `countPlayers` int(11) NOT NULL DEFAULT '0' COMMENT 'The number of players actually created on this realm.', [COLOR="#FF0000"][B] `invalid` tinyint(1) NOT NULL DEFAULT '0' COMMENT 'Means that this realm is invalid and must not be shown to the client.', `offline` tinyint(1) NOT NULL DEFAULT '0' COMMENT 'Means that this realm is offline.', `showversion` tinyint(1) NOT NULL DEFAULT '0' COMMENT 'Means that the version of this realm must be shown to the client.', `newplayers` tinyint(1) NOT NULL DEFAULT '0' COMMENT 'Means that only the new players may join this realm.', `recommended` tinyint(1) NOT NULL DEFAULT '0' COMMENT 'Display the recommended option in the client.',[/B][/COLOR] PRIMARY KEY (`id`), KEY `fk_realm_type_idx` (`fk_realmtype`), KEY `fk_realm_timezone_idx` (`fk_timezone`), CONSTRAINT `fk_realm_timezone` FOREIGN KEY (`fk_timezone`) REFERENCES `realmtimezone` (`id`) ON DELETE NO ACTION ON UPDATE NO ACTION, CONSTRAINT `fk_realm_type` FOREIGN KEY (`fk_realmtype`) REFERENCES `realmtype` (`id`) ON DELETE NO ACTION ON UPDATE NO ACTION Software code: /** * This method is converting the realm flags into a single integer. * @param r The realm for which the flags needs to be converted. * @return The integer value corresponding to the flags. */ private int convertFlagsToInt(Realm r) { int flags = 0; flags+=(r.isInvalid() ? 1 : 0); flags+=(r.isOffline() ? 2 : 0); flags+=(r.isShowversion() ? 4 : 0); // flags+=(0*8); // Unknown flag // flags+=(0*16); // Unknown flag flags+=(r.isNewplayers() ? 32 : 0); flags+=(r.isRecommended() ? 64 : 0); // flags+=(0*128); // unknown flag return flags; } -
Well, for me, the discussion is rather: do we allow it ? This is not like it is blizzlike... So is it Worth to do that effort ?
-
The command .announce SayHello does not work Hello, as reported in this post ([url]https://www.getmangos.eu/french-francais/10563-server-mangosone-develop21-announce-bug.html[/url]), the command .announce does not seem to work properly. I think it may come from the fact that announce uses SendWorldText which does not look like it is received by the client. ChatHandler: [url]https://github.com/mangosone/server/blob/fc04066c0444b43c4f14289cf59461da4b39ddbc/src/game/ChatCommands/Level1.cpp[/url] World: [url]https://github.com/mangosone/server/blob/fc04066c0444b43c4f14289cf59461da4b39ddbc/src/game/WorldHandlers/World.cpp[/url] Tal'.
-
Instance entry level not correct...
Talendrys commented on Xenithar's bug in Archived Reports (Zero)(Resolved issues)
Which part of SM did you try ?
Contact Us
To contact us
click here
You can also email us at [email protected]
Privacy Policy | Terms & Conditions
You can also email us at [email protected]
Privacy Policy | Terms & Conditions
Copyright © getMaNGOS. All rights Reserved.
This website is in no way associated with or endorsed by Blizzard Entertainment®
This website is in no way associated with or endorsed by Blizzard Entertainment®