Platform updates: release 2024.04 (April 2024)

Short answer. Gambling Soft platform release 2024.04 (April 2024) opens the current generation of the platform: the casino API moves to a new repository with coding standards, a layered structure and automated tests; fast login and registration by phone arrive; the support chat gets attachments; notification and transaction endpoints appear; a cron scheduler with declarative schedules and an acceptance-test runner with reports are introduced; the sportsbook gets a new betting structure fed by a sports data feed; and the poker room 2.0 is started from scratch with betting rounds, winners, auto start and dynamic card counts. 310 changes across the API, the front end and poker.

Release 2024.04 at a glance

Player API

• New: repository and standards. The API moves to its own repository with a code sniffer, php-cs-fixer for tests and written development rules; the ajax layer is cleaned up and restructured into controllers, services, validators and request and response DTOs with a shared abstract response and status trait.
• New: login and registration. Fast login by phone or email, registration by phone, login by phone action, password reminder by phone, bonus id passed at registration with domain-group-aware bonus queries; validators covered by unit tests and acceptance tests.
• New: dependency handling. Global variables injected through an attribute into readers, writers, services and validators; factories removed and models refactored; constants for static data and default limits.
• Improved: email notifications in ajax requests with template replacements; free-spin and deposit bonuses separated; deposit and VIP level changes; a render function on Smarty in the core.

Support chat

• New: chat API with message history, attachments with validation, integer casting of ids, date formats for the front end and performance fixes; the front end sends through the new endpoint, clears inputs and attachments after sending and renders history blocks.

Notifications and transactions

• New: notification controller and send service; transaction endpoints for the balance log and payment history; acceptance tests and service tests for both.

Scheduler, mailing and tests

• New: cron scheduler. Jobs declare their schedule with an attribute; a schedule handler and executor run them with a default time zone; start and finish output per job; last-wins job fixed.
• New: mailing cron job with the mail controller, domain groups and receiver types.
• New: test runner. Codeception runner with a test suite entry point, report helper and report directory; acceptance tests for cron, logs and the API; a jackpot folder and a fortune wheel module added to the codebase.

Security and mail

• New: spam protection for sending emails and for phone activation with request limits and error messages; a security module; password requirement rules; the password in the registration email is escaped.

Betting

• New: betting structure. All coefficients delivered through a sports data feed; betting folders and tests added; parser cron job for outcomes.

Poker room 2.0

• New: project start. Table API for bets, correct request sending for the front end, bet and equal-bet logic, winner search and a new game after the round, auto start, leaving the table, table view without authorisation, fold handling, dynamic card creation per player with a card count field, round start and game end times, ready-to-play flow, finishing the game when one player remains, small and big blind amounts, max bet move.

Compatibility and upgrade notes

• The API repository starts with migrations and an htaccess routing prototype; later releases move all installations onto it.
• Cron jobs must be registered through the Schedule attribute; the old schedule file is removed.

Delivery to clients

Projects hosted by Gambling Soft are updated by our team. Source-code licensees receive the release from the repository under their support terms. Questions about a specific item: the contact page. All issues are listed under Platform updates; the platform itself is described on the architecture page.