List of GameEventType Events

2025-07-08T10:25:51Z

XxharCs: Created page with "== List of Events (GameEventType) == This page lists the currently available events you can hook into using the <code>geb.on("EVENT_NAME", ...)</code> function from JavaScript. All events come from the <code>GameEventType</code> enum in either the '''game server''' or '''chat server''' codebase. These are used in event scripts placed inside <code>scripts/event/</code>. == Game Server Events == {| class="wikitable sortable" ! Event Name !! Called? !! Description |-..."

== List of Events (GameEventType) ==

This page lists the currently available events you can hook into using the <code>geb.on("EVENT_NAME", ...)</code> function from JavaScript.

All events come from the <code>GameEventType</code> enum in either the '''game server''' or '''chat server''' codebase.
These are used in event scripts placed inside <code>scripts/event/</code>.

== Game Server Events ==

{| class="wikitable sortable"
! Event Name !! Called? !! Description
|-
| ON_TICK || ✅ || Called on every server tick
|-
| ON_LOGIN || ✅ || Player logs in
|-
| ON_LOGOUT || ❌ || Player logs out
|-
| CHALLENGE_INIT_HP || ❌ ||
|-
| CHALLENGE_DAMAGE || ❌ ||
|-
| CHALLENGE_POINT || ❌ ||
|-
| CHALLENGE_FINISH || ❌ ||
|-
| EMBLEM_INIT || ❌ ||
|-
| ENCHANT_ON_ANNOUNCE || ❌ ||
|-
| ON_ENCHANT || ❌ ||
|-
| GACHA_OPENED || ❌ ||
|-
| RECIPE_COMBINED || ❌ ||
|-
| INVENTORY_ITEM_TIME_EXPIRED || ❌ || Time-based item expired
|-
| ON_PLAYER_ANNOUNCE || ❌ ||
|-
| PLAYER_QUICK_SLOT_USE || ❌ ||
|-
| LOBBY_JOINED || ❌ || Player entered the lobby
|-
| LOBBY_LEFT || ❌ || Player left the lobby
|-
| ROOM_LOBBY_JOINED || ❌ ||
|-
| ROOM_CREATED || ❌ ||
|-
| ROOM_JOINED || ❌ || Player joined a room
|-
| ROOM_LEFT || ❌ || Player left a room
|-
| ROOM_POSITION_CHANGED || ❌ ||
|-
| ROOM_MAP_CHANGED || ❌ ||
|-
| MP_RELAY_CONNECTED || ❌ ||
|-
| MP_GAME_ANIM_SKIP_TRIGGERED || ✅ || After skipping the match intro, this is called before Player stats are sent to the client
|-
| MP_GAME_ANIM_SKIP_END || ✅ || Skipping match intro finished and is called right before guardian serve in battle or guardian mode, or serve in basic mode
|-
| MP_MATCH_START || ❌ || Match begins
|-
| MP_MATCH_END || ✅ || Match ends
|-
| MP_PLAYER_USE_SKILL || ✅ || A skill was used
|-
| MP_PLAYER_PICKING_UP_CRYSTAL || ✅ || Player crystal pickup
|-
| MP_PLAYER_HITS_TARGET || ✅ || A target is hit during battle or guardian mode
|-
| MP_PLAYER_SWAP_QUICK_SLOT_ITEMS || ❌ ||
|-
| SHOP_MAINTENANCE_REQUESTED || ❌ ||
|-
| ON_SHOP_LOAD || ❌ ||
|-
| ON_SHOP_LOAD_PREPARE || ❌ ||
|-
| SHOP_ITEM_BOUGHT || ❌ ||
|-
| TUTORIAL_INIT || ❌ ||
|-
| TUTORIAL_FINISH || ❌ ||
|-
| ON_DEV_PACKET || ❌ || Developer-only test packet
|-
| SESSION_TIME_UPDATE || ❌ ||
|-
| ON_HEARTBEAT || ❌ ||
|}

== Chat Server Events ==

{| class="wikitable sortable"
! Event Name !! Called? !! Description
|-
| ON_TICK || ✅ || Called on every server tick
|-
| ON_LOGIN || ❌ || Player logs in
|-
| ON_LOGOUT || ❌ || Player logs out
|}

=== Legend ===
;✅ : Event is currently called (triggered by the server)
;❌ : Event exists but is not currently triggered

''Don't see your needed event called yet?''
→ You can still write scripts using them and ask for the event to be wired on Discord.
Include the event name and what parameters your handler expects.

== Event Lists ==
* [[#Game Server Events|Game Server]]
* [[#Chat Server Events|Chat Server]]

[[Category:Guides]]
[[Category:Event]]

Event MP PLAYER HITS TARGET

2025-07-08T09:45:37Z

XxharCs:

Event MP PLAYER HITS TARGET

2025-07-08T09:45:07Z

XxharCs:

Event MP PLAYER HITS TARGET

2025-07-08T09:44:43Z

XxharCs: Created page with "= Event MP_PLAYER_HITS_TARGET = '''MP_PLAYER_HITS_TARGET''' is one of these events that are called from multiple places with multiple argument count. Therefore accessing the parameters passed to that event require proper handling to avoid errors. Currently it is called 3 times in sum: <pre> GameEventBus.call(GameEventType.MP_PLAYER_HITS_TARGET, ftClient, game, skill); // ftClient might be changed to connection in future GameEventBus.call(GameEventType.MP_PLAYER_HITS_T..."

= Event MP_PLAYER_HITS_TARGET =

'''MP_PLAYER_HITS_TARGET''' is one of these events that are called from multiple places with multiple argument count.

Therefore accessing the parameters passed to that event require proper handling to avoid errors.

Currently it is called 3 times in sum:
<pre>
GameEventBus.call(GameEventType.MP_PLAYER_HITS_TARGET, ftClient, game, skill); // ftClient might be changed to connection in future
GameEventBus.call(GameEventType.MP_PLAYER_HITS_TARGET, connection, game, newHealth, skillHitsTarget);
GameEventBus.call(GameEventType.MP_PLAYER_HITS_TARGET, connection, game, newHealth, skill, skillHitsTarget);
</pre>

You need to register and handle it the following way:
<syntaxhighlight lang="js">
geb.on("MP_PLAYER_HITS_TARGET", function () {
switch (arguments.length) {
case 3:
handleUniqueSkill(arguments[0], arguments[1], arguments[2]);
break;
case 4:
handleBallLossDamage(arguments[0], arguments[1], arguments[2], arguments[3]);
break;
case 5:
handleSkillDamage(arguments[0], arguments[1], arguments[2], arguments[3], arguments[4]);
default:
logUnexpectedArgs(arguments);
}
});

</syntaxhighlight>

<code>arguments</code> is a built-in object in JavaScript functions, especially in non-arrow (<code>function (...) {}</code>) style functions. It is implicitly available inside any function declared with the classic <code>function (...) {}</code> syntax.

It is:
* an array-like object
* holds all the values passed to the function
* always available in classic functions (not in arrow <code>functions ()=>{}</code>)

[[Category:Server]]
[[Category:Scripting]]

2025-02-24T19:57:41Z

XxharCs:

= Database Schema & Cheatsheet =
This page provides an overview of the database structure used in Fantasy Tennis, showing the key tables, their columns, and relationships. The schema diagram below visually represents how different entities connect within the system.

== Schema ==
[[File:Db-entities.svg|200px|thumb|center|alt=Database Schema|Database Schema]]

== Tables of Interest ==
Tables might worth looking into as they are important on setting up your own Fantasy Tennis Server Configuration inside the Database.

=== Config ===
The `config` table is used to store various server wide settings that control gameplay mechanics, security settings, logging behavior, and feature toggles. Each configuration entry consists of:

* '''name''' – The unique identifier of the config setting.
* '''description''' – A short explanation of what the setting controls (may be null).
* '''value''' – The actual configured value.
* '''type''' – The data type of the value (e.g., boolean, int, double, string).

Administrators can modify these values to tweak server behavior, enable or disable features, and adjust game mechanics dynamically.

Below is a list of currently supported configuration values along with their default settings.

{| class="wikitable"
! Name !! Type !! Default Value !! Description
|-
| '''anticheat.enabled''' || boolean || false || Enables or disables the built-in anticheat (JFTSE exclusive).
|-
| '''anticheat.port''' || int || 1337 || Port used for the anticheat system (JFTSE exclusive).
|-
| '''dev.packets.handle''' || boolean || false || Handles developer/debug packets.
|-
| '''packets.id.translate.enabled''' || boolean || true || Enables translation of packet IDs.
|-
| '''logging.packets.all.enabled''' || boolean || true || Enables logging of all network packets.
|-
| '''network.encryption.enabled''' || boolean || false || Enables network encryption for secure communication.
|-
| '''password.encryption.enabled''' || boolean || false || Encrypts player passwords upon login.
|-
| '''player.level.max''' || int || 60 || Maximum player level (JFTSE exclusive, levels above 65 require client modifications).
|-
| '''command.room.mode.change.player.level''' || int || 60 || Minimum required level to change room mode via command.
|-
| '''game.bonus.global.gold''' || int || 5 || Global gold bonus multiplier (Single Player).
|-
| '''game.bonus.global.exp''' || int || 5 || Global experience bonus multiplier (Single Player).
|-
| '''game.bonus.wongame.exp''' || double || 0.2 || Experience bonus for winning a game (Basic & Battle).
|-
| '''game.bonus.wongame.gold''' || double || 0.2 || Gold bonus for winning a game (Basic & Battle).
|-
| '''logging.packets.console-output.enabled''' || boolean || true || Enables logging of packets in console output.
|-
| '''matchplay.guardian.hard.won.ranking-point.multiplier''' || double || 1.0 || Multiplier applied to ranking points in Guardian Hard mode.
|-
| '''game.map.allow.snowmoon''' || boolean || false || Allows Snow Moon map in Guardian mode.
|}

'''Notes:'''
* Config values marked as '''JFTSE exclusive''' are unique to this server implementation and may not be available in other Fantasy Tennis servers.
* Those values represent the development chosen defaults and does not represent values set within the [https://jftse.com JFTSE] hosted server.

=== M_Scenarios ===
Each game mode has multiple scenarios. A scenario marked as "default" is always selected first. If multiple scenarios are active (`status = 1`), the default scenario is prioritized. If multiple active scenarios are marked as default, the first one retrieved from the database is chosen.

Scenario types:
* '''Guardian Normal (non Boss Battle)''' → `GUARDIAN`
* '''Boss Guardian''' → `BOSS_BATTLE`
* '''Boss Guardian v2 (new mechanics defined through scripting)''' → `BOSS_BATTLE_V2`

=== S_Maps ===
Defines all available maps and references client map id's.

{| class="wikitable"
! id !! bossPlayTime !! breathTime !! description !! isBossStage !! map !! name !! playTime !! triggerBossTime !! useBreathTime
|-
| 1 || [NULL] || 100 || [NULL] || 0 || 0 || Rubycrab || [NULL] || [NULL] || 0
|-
| 2 || [NULL] || 100 || [NULL] || 0 || 1 || Emerald Beach || [NULL] || [NULL] || 0
|-
| 3 || 10 || 100 || [NULL] || 0 || 2 || Twinkle Town || 15 || 10 || 0
|-
| 4 || [NULL] || 100 || [NULL] || 0 || 3 || The Aeolos || [NULL] || [NULL] || 0
|-
| 5 || [NULL] || 100 || [NULL] || 0 || 5 || Life Wood || [NULL] || [NULL] || 0
|-
| 6 || 5 || 100 || [NULL] || 1 || 4 || Snow Moon || [NULL] || 8 || 0
|-
| 7 || 5 || 100 || [NULL] || 1 || 6 || Arena || [NULL] || 3 || 0
|-
| 8 || 5 || 100 || [NULL] || 1 || 7 || Monslava || [NULL] || 3 || 0
|-
| 9 || 5 || 100 || [NULL] || 1 || 8 || Monslava Blue || [NULL] || 3 || 0
|-
| 10 || 5 || 100 || [NULL] || 1 || 9 || Devaberg || [NULL] || 3 || 0
|-
| 11 || 5 || 100 || [NULL] || 1 || 10 || Atlantis || 8 || 4 || 0
|-
| 12 || 5 || 100 || [NULL] || 1 || 11 || Temple || [NULL] || 3 || 0
|-
| 13 || [NULL] || 100 || [NULL] || 0 || 12 || Room of Shadow || [NULL] || [NULL] || 0
|-
| 14 || 5 || 100 || [NULL] || 1 || 13 || Machine City || [NULL] || 3 || 0
|-
| 15 || 5 || 100 || [NULL] || 1 || 14 || Dance Time || [NULL] || 3 || 0
|}

=== Guardian_2_Maps ===
Connects a guardian (or boss guardian) to a map with a specific scenario. Each scenario has a unique set of guardians available for matches.

=== Skill_2_Guardians ===
Links skills to guardians. The connection is made through `Guardian_2_Maps`, associating skills with a guardian in a specific scenario and map. If no `guardian_2_maps` entry is set, it defaults to `btItem`, which is predefined for guardian types. `btItem` is shared among similar guardian types (e.g., Dokaro and related "ro" types).

=== S_Guardian_Multipliers ===
Defines multipliers for Guardian Mode, applicable for gold or experience.

These multipliers can be linked in the `S_Relationships` table.

{| class="wikitable"
! id !! description !! multiplier
|-
| 1 || default exp multiplier || 1.0
|-
| 2 || default gold multiplier || 1.0
|-
| 3 || exp x3 || 3.0
|-
| 4 || exp x4 || 4.0
|-
| 5 || exp x5 || 5.0
|-
| 6 || exp x6 || 6.0
|-
| 7 || exp x7 || 7.0
|-
| 8 || gold x7 || 7.0
|-
| 9 || gold x5 || 5.0
|-
| 10 || gold x3 || 3.5
|-
| 11 || exp x3 || 3.5
|}

=== S_Relationships ===
Defines connections between various entities within the game, enabling precise control over item drops, multipliers, and other gameplay mechanics. Relationships are established using two key fields:

* '''`id_f`''' (`id_from`): Represents the originating entity of the relationship, such as a Product or Multiplier.
* '''`id_t`''' (`id_to`): Represents the target entity of the relationship, such as a Guardian, Boss Guardian, or Map.

When linking products specifically to guardians, the '''`productIndex`''' from the product definition is used for '''`id_f`''', and the '''`guardian_2_maps.id`''' (not the direct Guardian or Boss Guardian ID) is used for '''`id_t`'''. Each relationship is further described by its type and role, defining how it influences gameplay.

Relationships can be individually toggled on or off via the '''`status`''' field.

==== Advanced Item Drop Control (Role ID 1) ====
Additionally, enhanced item drop control is available specifically for the '''Item Drop''' role (role ID '''1'''):

* Default item weight is '''20.0''' when no specific weight is provided.
* A fixed weight of '''15.0''' is used to determine scenarios where no item is awarded (displayed as an "X").
* Drop exclusivity can be defined specifically for:
** '''`forHardMode`''': Drops exclusive to Guardian Hard Mode.
** '''`forRandomMode`''': Drops exclusive to Guardian Random Mode.
* The '''`levelReq`''' field, currently unused, is reserved for future use to restrict drops based on player levels in a planned progression system.

'''Quantity Determination for Item Drops:'''
{| class="wikitable"
! Condition !! Quantity Result
|-
| '''`qty`''' is set, '''`qtyMin`/`qtyMax`''' not set || Exact quantity from '''`qty`'''
|-
| '''`qty`''' not set, '''`qtyMin`/`qtyMax`''' set || Random quantity between '''`qtyMin`''' and '''`qtyMax`'''
|-
| All quantity fields '''NULL''' || Defaults based on item type:
* '''Material''': Min 1 / Max 3
* '''Quick''': Min 5 / Max 100
* '''Parts & Others''': Min 1 / Max 1
|-
| '''`qty`''' and '''`qtyMin`/`qtyMax`''' both set || Random quantity between '''`qtyMin`''' and '''`qtyMax`'''
|}

=== S_Relationship_Types ===
Defines supported relationship types, describing what entities can be linked together:

{| class="wikitable"
! id !! Description
|-
| 1 || Product to Guardian
|-
| 2 || Product to Boss Guardian
|-
| 3 || Product to Map
|-
| 4 || Multiplier to Guardian
|-
| 5 || Multiplier to Boss Guardian
|-
| 6 || Multiplier to Map
|-
| 7 || Product to Map (Guardian Mode)
|-
| 8 || Product to Sell Price
|}

=== S_Relationship_Roles ===
Defines the supported roles that relationships can take, describing their in game functionality:

{| class="wikitable"
! id !! Description
|-
| 1 || Item Drop
|-
| 2 || Exp Multiplier
|-
| 3 || Gold Multiplier
|-
| 4 || Item Sell Price
|}

=== K_Status ===
Defines the different status types used in game.

{| class="wikitable"
! id !! Description
|-
| 1 || Active
|-
| 2 || Inactive
|}

=== Notes & Additional Information ===
* The database schema is subject to updates as new mechanics and features are introduced.
* Some tables may have additional columns not explicitly documented if they are not required for core functionality.
* Unused fields, such as `levelReq` in `S_Relationships`, are placeholders for future game progression updates.

[[Category:Server]]

Database Schema & Cheatsheet

2025-02-24T19:45:07Z

XxharCs:

Commands

2025-02-24T18:31:01Z

XxharCs: Created page with "= Ingame Commands = This page provides a list of available ingame commands for '''Fantasy Tennis''' within '''JFTSE'''. Commands must be prefixed with a `-` to execute. Some commands are '''restricted to Game Masters (GMs)'''. == General Commands == These commands can be used by all players. === 🎲 Random Mode === Random guardians will spawn instead of the default ones (boss remains the same). <pre> -random </pre> === 🔥 Hard Mode === Enables '''Hard Mode''', inc..."

= Ingame Commands =

This page provides a list of available ingame commands for '''Fantasy Tennis''' within '''JFTSE'''. Commands must be prefixed with a `-` to execute. Some commands are '''restricted to Game Masters (GMs)'''.

== General Commands ==
These commands can be used by all players.

=== 🎲 Random Mode ===
Random guardians will spawn instead of the default ones (boss remains the same).
<pre>
-random
</pre>

=== 🔥 Hard Mode ===
Enables '''Hard Mode''', increasing enemy stats and spawning additional guardians.
<pre>
-hard
</pre>

=== 🎁 Gacha Opening ===
Opens gachas without animation for faster processing.
<pre>
-og "Gacha Name" <amount>
</pre>
'''Example:'''
<pre>
-og "Western Coin" 50
</pre>
➡ '''Note:''' Some gachas contain "ll" (e.g., `"Rare Box ll"`), requiring a lowercase `L` in the command.

=== 🏆 Arcade Mode ===
Enters '''Arcade Mode'''. WIP.
<pre>
-arcade
</pre>

=== 🔄 Pointback ===
Allows players to vote for resetting the last point in '''[[Basic Mode]]'''.
<pre>
-pb
</pre>
➡ '''Note:''' All players must vote using `-pb` before a new point is made.

== GM Commands ==
These commands are '''restricted to Game Masters (GMs)'''.

=== 🚫 Player Management ===
Banning, unbanning, and kicking players.
<pre>
-ban <player>
-unban <player>
-serverKick <player>
</pre>

=== 📝 Server Notice ===
Sets and broadcasts a '''server wide notice'''.
<pre>
-sN <message>
</pre>

=== 🔄 Reset & Reload ===
Resets or reloads server data.
<pre>
-rsLogin <player> # Resets login status
-reloadScripts # Reloads all scripts
-event # Event configuration
</pre>

=== 🎁 Item & Gift Commands ===
Used to grant items, experience, or gold to players.

Give items to '''another player''':
<pre>
-give <player> <item> <amount>
</pre>

Give items to '''yourself''':
<pre>
-get <item> <amount>
</pre>

Send a '''gift''' to another player:
<pre>
-gift <player>
</pre>

== Help Command ==
Displays all commands and their description.
<pre>
-help
</pre>

----

<big>'''Notes:'''</big>
* Commands '''must always start with `-`'''.
* Some commands may have additional restrictions (e.g., requiring level 60).
* GM commands are '''restricted''' to authorized users.

For further details, refer to the ingame chat.

[[Category:Guides]]

Guides & Tutorials

2025-02-24T18:03:37Z

XxharCs: Undo revision

== 📖 Guides & Tutorials ==
Here you can find various guides and tutorials.

=== 📜 Available Guides ===
''This list is automatically generated. To add a guide, create a new page and categorize it under Guides.''

<dpl>
category=Guides
ordermethod=title
order=ascending
namespace=Main
mode=unordered
format=list
linkstoresult=true
noresultsheader=❌ No guides found. Be the first to add one!
</dpl>

== 🛠 Contributing ==
* '''Want to add a guide?''' Create a new page and add <code><nowiki>[[Category:Guides]]</nowiki></code> at the bottom.

[[Category:Guides]]

Guides & Tutorials

2025-02-24T18:02:27Z

XxharCs:

Here you can find various guides and tutorials.

=== 📜 Available Guides ===
''This list is automatically generated. To add a guide, create a new page and categorize it under Guides.''

<dpl>
category=Guides
ordermethod=title
order=ascending
namespace=Main
mode=unordered
format=list
linkstoresult=true
noresultsheader=❌ No guides found. Be the first to add one!
</dpl>

== 🛠 Contributing ==
* '''Want to add a guide?''' Create a new page and add <code><nowiki>[[Category:Guides]]</nowiki></code> at the bottom.

[[Category:Guides]]

JFTSE Wiki

2025-02-19T18:28:31Z

XxharCs:

= JFTSE Wiki =

Welcome to the '''JFTSE Wiki'''.


Please [https://wiki.jftse.com/index.php?title=Special:UserLogin Log In] with your JFTSE account to edit and contribute.


This Wiki is a community driven knowledge base for everything related to '''JFTSE and Fantasy Tennis'''. Here you will find guides, tutorials, tips, tricks, and information about gameplay mechanics, server configurations and much more.

This Wiki should be considered a place where community members can create new informative webpages that cover specific topics,
and where fellow community members can contribute to and improve existing pages.

We strongly believe in the idea that this Wiki should be a free and open method of overlaying information to everyone. Therefore, our stance is that everyone should be able to contribute to this Wiki, as long as the information is accurate and relevant. As a guest, you are free to access and read all the information the Wiki has to offer. As a community member, you are free to contribute to the Wiki by creating new pages, editing existing pages, and discussing the content of the Wiki with other community members as long as you conform to the [[JFTSE Wiki:Community Rules|Community Rules]].

= 📚 Usage And Information =
=== Information ===
* [[About_JFTSE|About JFTSE]]
* [[About_Fantasy_Tennis|About Fantasy Tennis]]
* [[JFTSE Wiki:Community Rules|Community Rules]]

=== Contributing ===
Only registered JFTSE users can edit pages. 
To contribute, [https://wiki.jftse.com/index.php?title=Special:UserLogin Log In] with your JFTSE account and help expand the knowledge base! 
Please read and follow the [[JFTSE Wiki:Wiki Guidelines|Wiki Guidelines]] before contributing.

= 🛠 Getting Started =
* [[Game Lore]] - Dive into the world of Fantasy Tennis.
* [[Game Installation Guide]] - Step-by-step guide on installing the game.
* [[Beginner's Guide]] - Basics of gameplay, controls and UI.
* [[Gameplay Mechanics]] - Strategies, combos and in-depth gameplay mechanics.
* [[Troubleshooting|Troubleshooting & Fixes]] - Solutions for common issues.

= 📖 Game Information =
* [[Characters]] - Information about the characters in Fantasy Tennis.
* [[Items]] - List of items and their effects.
* [[Skills]] - List of skills and their effects.
* [[Maps]] - Learn about the different maps in Fantasy Tennis.
* [[Game Modes]] - Information about the different game modes.
* [[Guides & Tutorials]] - Learn tips and tricks from experienced players.

= 📜 Server Information =
* [[Database Schema & Cheatsheet]] - Database Schema used for Fantasy Tennis & Cheatsheet.
* [[Server Configuration]] - Information about server configuration.

= 🔗 Useful Links =
* [https://jftse.com/ JFTSE Website]
* [https://discord.gg/MwamzbMTMy Discord]
* [[Special:RecentChanges|Recent Changes]]
* [[Special:AllPages|All Pages]]
* [[Special:Random|Random Page]]
* [[Special:Categories|Categories]]

Category:Server

2025-02-19T18:26:57Z

XxharCs: Created blank page

Database Schema & Cheatsheet

2025-02-19T18:26:44Z

XxharCs: Created page with "= Database Schema & Cheatsheet = This page provides an overview of the database structure used in Fantasy Tennis, showing the key tables, their columns, and relationships. The schema diagram below visually represents how different entities connect within the system. == Schema == Database Schema Category:Server"