Age | Commit message (Collapse) | Author | Files | Lines |
|
`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>
|
|
Add *makeitem2 script command.
|
|
Fixed areawarp cell check
|
|
Update party_check_state
|
|
The script command areawarp has been checking the wrong target map for ages. It has been checking the mapindex rather than the mapid and therefore returned a wrong result.
Original commit: rathena/rathena@ac2ba09
|
|
Fix wrong command usage at the sign quest
|
|
disabled npc's do not show the effects
|
|
Signed-off-by: HerculesWSAPI <dev@herc.ws>
|
|
Signed-off-by: HerculesWSAPI <dev@herc.ws>
|
|
Itemdb AegisName fixes
|
|
The apostrophe (`'`) is no longer an allowed symbol in libconfig key
names. It is no longer necessary since it is no longer allowed in
constant names.
Signed-off-by: Haru <haru@dotalux.com>
|
|
Supporting apostrophes (`'`) inside constants or variables is no longer
necessary thanks to the more strict AegisName ruleset we're using now.
Signed-off-by: Haru <haru@dotalux.com>
|
|
Signed-off-by: Haru <haru@dotalux.com>
|
|
This removes the remaining unsupported symbols (despite they being
official names) in AegisNames: The apostrophe (`'`) sign is suppressed.
The full replacement rules (cumulative with the step 1 commit) are thus:
- Any apostrophe is suppressed.
- Any non-`[A-Za-z0-9_]` character is replaced with an underscore (`_`).
- If the replaced symbol is at a word boundary (beginning or end of the
string, or next to another underscore), it is suppressed instead.
- If the replacement causes an AegisName conflict, underscores are
appended appropriately.
Signed-off-by: Haru <haru@dotalux.com>
|
|
This removes some unsupported symbols (despite they being official names) in
AegisNames. The replacement rules used are:
- Any non-`[A-Za-z0-9_']` character is replaced with an underscore (`_`).
- If the replaced symbol is at a word boundary (beginning or end of the string,
or next to another underscore), it is suppressed instead.
- If the replacement causes an AegisName conflict, underscores are appended
appropriately.
Signed-off-by: Haru <haru@dotalux.com>
|
|
This removes special symbols (spaces, dashes, parentheses) from various custom
AegisNames for which we don't have the official value available. Where
possible, the appropriate name was guessed (based on similar existing items).
Signed-off-by: Haru <haru@dotalux.com>
|
|
They are whips, not musical instruments.
Signed-off-by: Haru <haru@dotalux.com>
|
|
Some missing items were copied to the pre-renewal database. In general,
when an item ID is hardcoded in source, it's preferable that the item
exists in both databases.
Signed-off-by: Haru <haru@dotalux.com>
|
|
Signed-off-by: Haru <haru@dotalux.com>
|
|
- Mostly whitespace, with the exception of the 'Wurst' item rename (was
previously incorrectly named Brusti)
Signed-off-by: Haru <haru@dotalux.com>
|
|
This commit just propagates the AegisName changes to the pre-re database
and to the (re) scripts.
Two issues are fixed as a side-effect:
- The ghost_palace script was referring the non-existing constant(s):
Thanatos_Two-Handed_Staff == (Thanatos_Two) - (Handed_Staff) == 0.
Paired with the script engine's inability to differentiate between
constants and player variables, that produced a very subtle issue.
- The item RAG203 is sold by a NPC (Rebellion Weapon Vending). Due to a
pair of swapped AegisName constants (RAG203 and RAG203_), the slotted
version was sold by the NPC instead of hte non-slotted one (the issue
was actually fixed in the previous commit, although the description of
the fix is here - these two commits are only split for legibility
purposes but they're to be considered indivisible).
Signed-off-by: Haru <haru@dotalux.com>
|
|
The values are based on Divine-Pride.
This also fixes several unusable AegisName constants containing spaces
or special characters.
Signed-off-by: Haru <haru@dotalux.com>
|
|
Libconfig quickupdate
|
|
For the time being, test_libconfig only (test_spinlock is very time
consuming)
|
|
The config_t objects need to be initialized through libconfig->init()
before use (except when loaded through libconfig->load_file(), which
initializes the object).
Signed-off-by: Haru <haru@dotalux.com>
|
|
This also fixed a typo (misplaced parentheses around LIBCONFIG_OBJ) in
the *_DEPENDS variable of makefiles
Signed-off-by: Haru <haru@dotalux.com>
|
|
The library common.a depends on common_sql.a.
Signed-off-by: Haru <haru@dotalux.com>
|
|
|
|
As we use int64 (instead of long long int) through the code, it's
preferable if our libconfig interface does the same, avoiding us to
create temporary interchange variables for that purpose.
Signed-off-by: Haru <haru@dotalux.com>
|
|
|
|
Signed-off-by: Haru <haru@dotalux.com>
|
|
The version of flex used here includes a workaround for
https://github.com/westes/flex/issues/113 (since it's otherwise
not-compilable)
|
|
Signed-off-by: Haru <haru@dotalux.com>
|
|
Signed-off-by: HerculesWSAPI <dev@herc.ws>
|
|
Fixed incorrect item type for weapons and armor
|
|
The issue was caused by an evident patch mishap in commit
5e04f472e1ef618d9201fd22e382dca829992b3b. The misplaced piece of code
has now been moved to the most likely place it was supposed to be in.
This commit also removes an extra 'break' introduced by accident in
commit f4e8189545642ee0bf87f3da546bddc918682935 (which caused no harm).
Related: http://herc.ws/board/topic/13672-heaven-driver/
Signed-off-by: Haru <haru@dotalux.com>
|
|
Add some new packets and fix packet versions
|
|
|
|
|
|
|
|
into packets.h
|
|
|