* Use Guild shared_ptr
* Member rank level default to constexpr
* Use const when possible
* @ramon-bernardo
Use const when possible
* Use shared_ptr alias
* Fix
* Fix
* Fix
* Fix
* Fix delete
* Fix
* No need to reuse the variable
* Use const shared ptr
* Use const& ptr
* Inline rank check
* Run clang-format with updated Ubuntu image
* Run clang-format on workflow modification and dispatch
* Drop sudo from apt invocation
* Install clang-format from llvm repository
* Merge strings
- Use base Google style
- Drop column limit override
- Format all files
- Use tabs for indentation
- Move system headers after project headers
- Avoid breaking string literals
- Reflow usage text
- Match breaks before braces and colons to previous style
- Reduce spaces before trailing comments
- Reflow comments and fix macro usage in luascript.cpp
- Fix invalid code
- Don't align newline escapes
- Reflow comment to make more sense
Fixes these scenarios:
1. Still being able to remove or add items from a container that is placed inside of a house tile, if the container was already open prior to being uninvited from the house
2. Being able to use useable items, like runes out of a house door or from a container placed in a house door, if it was already open prior to being uninvited from the house
3. houseTile always being nullptr inside of Container::queryRemove, since the cast was not done properly, and even after fixing the cast, it had wrong behaviour afterwards
This change removes support for house access list lines using:
* regular expressions (? for single character, * for many characters)
* exclusions (lines starting with !)
After this change:
* Guild name and guild rank is still supported.
* A line with "*" is supported to allow everyone - this must be the only character in that line
* Access list is limited to 100 entries and each entry can be max 100 characters long.
Using booleans in config.lua (strings are still supported for backwards
compatibility)
Improved maintainability of existing enums
Removed unused enums
Reduced memory footprint of item abilities
This commit breaks backwards compatibility with breakchance and
ammoaction in items.xml and also certain global event names. Break
chance and action for weapons are now specified in weapons.xml and can
be applied to any weapon. This commit also removes the config option
"removeAmmoWhenUsingDistanceWeapon" as there were issues with that and
it is preferred that end-users configure actions for their weapons
(which provides better customizability) instead of having a global
variable that toggles it for every weapon.
Closes#1125
