Age | Commit message (Collapse) | Author | Files | Lines |
|
Fixes getbattleflag on npc/other/auction.txt
|
|
|
|
Fixes Range Exploit
|
|
remove useless check for questprogress
|
|
Add quest log for moscovia quests
|
|
|
|
|
|
Adjust 2@nyd areamobs
|
|
Adds GvG2 zone to WoE:SE maps
|
|
|
|
- In stretch, `libmysqlclient-dev` is no longer available. All the
stretch builds are now using `libmariadbclient-dev-compat` instead.
- `clang-4.0` builds have been added.
- Where it makes sense to, version-specific builds are now targeting the
distribution name rather than the meta-name (`jessie` instead of
`stable`). This makes them less prone to breakage when stretch will be
released.
- The `mysql-5.7` builds now use the `mysql-client-5.7` package since
it's available (they were previously using a generic `mysql-client`
package.)
- The `mariadb-10` builds have been renamed to `mariadb-10.0`, since
they use that specific version of the package.
- The `mariadb-latest` builds now use the `mariadb-client-10.1`
package, and are based on debian unstable.
Signed-off-by: Haru <haru@dotalux.com>
|
|
Signed-off-by: HerculesWSAPI <dev@herc.ws>
|
|
remove hardcoded chat area size
|
|
|
|
fixes 1551
http://herc.ws/board/tracker/issue-8657-nydhoggs-nest/
|
|
Add quest log for Juperos Ruins History Quest
|
|
Correct Para_Team_Mark_ effect.
|
|
Update Eden Quest script
|
|
in kRO Para_Team_Mark_ warp the player to eden group.
|
|
* also change name of 2 variables to the official names
- yuno_hist -> yuno_book
- jupe_hist -> jupe_book
partial merge of
rathena/rathena@c488268d8c2fa74e1d16daf0c04a6bf2d36e2350
|
|
When the server is called with a plugin-defined argument expecting
additional values, in the form '--foo bar', the parser is unable to
skip the additional value until the plugin is fully loaded.
The issue was caused by the first scans of the argument list to find
CMDLINE_OPT_PREINIT or CMDLINE_OPT_SILENT arguments, which happen before
plugins are loaded, and would cause the parser to choke on the
additional values, interpreting them as separate arguments.
This is related to PR #1552, where we attempted to use this option for
the first time.
Signed-off-by: Haru <haru@dotalux.com>
|
|
Update md5 calculation to be able to hash a binary buffer instead of …
|
|
Signed-off-by: hemagx <ibrahem.h.basyone@gmail.com>
|
|
strings
Signed-off-by: hemagx <ibrahem.h.basyone@gmail.com>
|
|
|
|
zenylog missing type 'K' for Bank Transactions
|
|
Fixing an small markdown mistake
|
|
Fixed airships.txt
|
|
Fixed incorrect OnTouch label in Crow of Destiny Quest
|
|
- when trigger event label, it run as *donpcevent() not *doevent(), no
player are attached to the script when it's triggering the event.
|
|
Signed-off-by: HerculesWSAPI <dev@herc.ws>
|
|
Signed-off-by: HerculesWSAPI <dev@herc.ws>
|
|
Signed-off-by: HerculesWSAPI <dev@herc.ws>
|
|
|
|
Credit: rathena/rathena@a9faab82cbcfbdb3009c5584032505e8617310bd
|
|
Add a custom weight check in ring of the wise king quest
|
|
|
|
|
|
Related to 2ceb249879148be0fca7d81f31158eccf3142aa2, which removed the
option since it didn't appear to be necessary on Linux or macOS.
Signed-off-by: Haru <haru@dotalux.com>
|
|
Job Class vs Job MapID cleanup
|
|
Signed-off-by: Haru <haru@dotalux.com>
|
|
`struct status_data::class_` was platform dependent since
c30bb75ec50624429bff7b4106db4be0fda366d6 in order to silence some
compile warnings (uint32 on 64 bit builds and uint16 on 32 bit builds).
It's now been changed to the correct type, int32, on all platforms.
Since the change has potential to silently break third party code, the
variable was renamed to `class`.
Signed-off-by: Haru <haru@dotalux.com>
|
|
This commit adds the function `pc->famelist_type()` to retrieve the
appropriate fame list for a given job (common operation). When the given
job ID doesn't have an appropriate fame list, the newly introduced value
RANKTYPE_UNKNOWN is returned.
Signed-off-by: Haru <haru@dotalux.com>
|
|
For consistency with `pc->addfame()`, the argument to pc->famerank() is
now an enum fame_list_type.
The function was renamed to `pc->fame_rank()` to avoid silently
compiling old non-compliant code.
Signed-off-by: Haru <haru@dotalux.com>
|
|
The function now takes the rank type as argument, rather than guessing
it from the character's class. If the wrong fame point type for the
current character is requested, the request is ignored.
This fixes some (unofficial) edge cases where a Taekwon or an Alchemist
refined a signed item, they could obtain rank points.
Signed-off-by: Haru <haru@dotalux.com>
|
|
This commit ensures that `sd->job` and related variables only contain
MapIDs (i.e. the serverside optimized values, where High Novice is
MAPID_NOVICE | JOBL_UPPER) and are never checked against the
client-based Job Class values.
As a rule of thumb, from now on, when a variable is named `job` or
`jobid`, it is intended to contain a MapID and not a Job Class ID. The
type of such variable shall be an unsigned `uint16` or `uint32`.
To ensure that related third party code is also verified when this
commit is merged, the variable `struct map_session_data::class_ (i.e.
`sd->class_`) is renamed to `job`.
Some issues in related lines are also fixed, including:
- The atcommand `@mount` would not check properly that the requesting
character is a 2nd class Swordsman type.
- `pc->addfame()` would silently accept invalid MapIDs, sending unknown
values to the client (more on this in a subsequent commit).
- `pc->famerank()` would not use the passed job as a bitmask, causing
the caller to have to mask it beforehand (more on this in a
subsequent commit).
- The Soul Linker check in TK_JUMPKICK wasn't future-proof (no harm
caused currently).
- Gunslingers would be able to be targeted by Spiritual Bestowment
(`MO_KITRANSLATION`) and Spiritual Sphere Absorption
(`MO_ABSORBSPIRITS`) due to a faulty check introduced when the
Rebellion class was implemented (causing unintended interaction with
Coins).
Signed-off-by: Haru <haru@dotalux.com>
|
|
This commit ensures that `sd->status.class` and related variables only
contain Job Classes (i.e. the client-compatible values, where High
Novice 4001) and are never checked against the bitmask-based MapID
values.
As a rule of thumb, from now on, when a variable is named `class`, it
is intended to contain a Job Class ID and not a MapID. The type of such
variable shall be a signed `int16` or `int`.
To ensure that related third party code is also verified when this
commit is merged, the variable `struct mmo_charstatus::class_ (i.e.
`sd->status.class_`) is renamed to `class`.
Some issues in related lines are also fixed, including:
- A wrong check in the char server would prevent the correct detection
of babies in code related to the family exp sharing.
- Baby Arch Bishops would not be affected by Eucharistica.
- A wrong check would cause the `questinfo()` script command not to
display its information for most classes (except 1-1 classes).
- Map IDs and Job Classes were mixed up in `itemdb_jobid2mapid()` and
`itemdb_jobmask2mapid()` for 1-1 classes (causing currently no harm,
since they just happen to coincide).
- The Baby Sura class would not cause parties to be marked as
containing a monk type character (for SLS Team Up purposes).
- Baby Geneticists would bypass the cart check when trying to equip
ammunitions.
- Baby Mechanics would bypass the Mado Gear check when trying to equip
ammunitions.
- Transcendent Shadow Chasers would lose the Stalkers' ability to clone
transcendent skills.
Signed-off-by: Haru <haru@dotalux.com>
|
|
The enum values are now written in a more explicit way, showing how
they're composed (upper mask + base job).
A future-proof static assertion is added, to make sure the base jobs
won't overlap the upper masks.
Signed-off-by: Haru <haru@dotalux.com>
|
|
This introduces the macro `STATIC_ASSERT(ex, msg)`, that works like its
C11 counterpart `_Static_assert(ex, msg)`, on compilers that support it.
Support is provided, depending on the compiler:
- When in C11 mode, use the native `_Static_assert`
- If the compiler advertises having the `c_static_assert` feature, use
`_Static_assert` (according to the clang documentation).
- If the compiler is GCC >= 4.7 (tested to be compatible), use
`_Static_assert` (nonstandard extension, C11 feature available in C99).
- If the compiler is MSVC (all the currently supported versions have
been tested to be compatible), then use `static_assert` (nonstandard
extension, C++ feature)
- Otherwise, define it as a no-op macro.
Signed-off-by: Haru <haru@dotalux.com>
|
|
Signed-off-by: Haru <haru@dotalux.com>
|