Skip to content

feat: Summer Update 2026 - #805

Open
jprzimba wants to merge 39 commits into
mainfrom
summer-update
Open

feat: Summer Update 2026#805
jprzimba wants to merge 39 commits into
mainfrom
summer-update

Conversation

@jprzimba

@jprzimba jprzimba commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator

This is a pre-made of Summer Update 15.25
This PR is under construction
Very thanks to @Mckay666 and @Jattartajjar

  • Echo Warden
  • Shape Weapon Proficiency
  • New Weapons Stellar
  • New Perks Ranks
  • New Maps

NOTE: for now game client uploaded to media fire until release
https://www.mediafire.com/file/d5bq6c3iuv3cc3l/15.30_localhost.rar/file

jprzimba and others added 27 commits June 22, 2026 16:19
Co-Authored-By: Jattartajjar <207260357+Jattartajjar@users.noreply.github.com>
Adds the spell-unlock banner the 15.x client shows when a player unlocks
a new spell ("New Spell Unlocked: <name>").
Adds the banners the 15.x client shows when a player finishes a Bounty task
or a Weekly specific-creature kill task ("Completed task: <creature>").
Co-Authored-By: Lacory <168381961+Mckay666@users.noreply.github.com>
My testes using logger
[2026-27-06 08:30:00.481] [warning] [Battle Healing] Player: Rullys, Factor: 1.3, Primary: 1025 -> 1333, Secondary: 0 -> 0
[2026-27-06 08:30:24.279] [warning] [Battle Healing] Player: Rullys, Factor: 1.3, Primary: 993 -> 1291, Secondary: 0 -> 0
Base automatically changed from game1525 to main July 5, 2026 12:03
jprzimba and others added 2 commits July 5, 2026 14:04
Thanks to @Jattartajjar

Co-Authored-By: Jattartajjar <207260357+Jattartajjar@users.noreply.github.com>
@orafal-dev

orafal-dev commented Jul 6, 2026

Copy link
Copy Markdown

Do you happen to have client with 15.30 version for this?

Also Summer Update is 15.30 update.

@Mckay666

Copy link
Copy Markdown
Contributor

Do you happen to have client with 15.30 version for this?

Also Summer Update is 15.30 update.

15.30 just been released today... you can get it and change IP
all this updates was maded in test server client, waiting for release 15.30, everything is the same just update the server protocol.

iloveShaders added a commit to iloveShaders/bettercrystalserver that referenced this pull request Aug 13, 2026
@Paco161315

Copy link
Copy Markdown
Contributor

Sent some updates to Jattar!

@iloveShaders

iloveShaders commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

new perk ranks doesn't work, for example when reshaping Bonus Damage it says "+0 Damage" it seems it has missing opcodes ?
image

@iloveShaders

Copy link
Copy Markdown
Contributor

another issue is with the badges present on bestiary page for killing an Echo Warden on every monster... even on a character pre 15.30 update who didnt participate in Echo Raid yet.
image

@jeswilldbm

Copy link
Copy Markdown

There is an issue with the character’s Dust capacity and the /setdusts GOD command.

When executing a command such as:

/setdusts GOD, 1000

The command only assigns 325 Dusts and displays a message indicating that this is the character’s maximum capacity.

This appears to be related to how Dust limit upgrades are calculated internally. Previously, each upgrade increased the Dust limit by 1. The system has now been changed so that each upgrade should increase the limit by 20, but this change is only reflected visually.

For example:

Create a new character with a maximum Dust capacity of 100.
Upgrade the character’s Dust limit three times.
The client correctly displays a maximum capacity of 160 Dusts: 100 + (3 × 20) = 160.
Execute the following command:

/setdusts CHARACTER_NAME, 160

The character only receives 103 Dusts, and the command reports that this is the maximum allowed amount.

This indicates that the client calculates each upgrade as +20, while the server or /setdusts command still calculates each upgrade as only +1.

The internal Dust limit calculation and the /setdusts command should use the updated value of 20 Dusts per upgrade, matching the capacity displayed in the client.
image

image image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants