Jump to content

Recommended Posts

Posted

Hello M.X.C!

 

 

I am writting this guide for people who use windows server 2003. This will mostly also apply to people who use other versions of windows.

 

1.Hardware/OS

 

Before doing anything, you should have a look at your server hardware. A intel pentium core 2 duo with 2 gb ram may look nice but with l2j, its not.

Although this is budget based and you will probally build up some nice server allong the way of having a private server, you will need some powerfull hardware to support 1000+.

Currently i am using this configuration:

 

Cpu: Quad Core Xeon 3220 - 2.40GHz (Kentsfield) - 2 x 4MB cache

MBram: 8 GB DDR2 667

HDD: 73GB SA-SCSI 15K RPM

HDD2: 73GB SA-SCSI 15K RPM

Connection: 1000mbit up/down

OS: Windows server 2003 64bit RC2

 

You might think that cpu power is all that matters when hosting a gameserver but in fact, your harddisk and ram are way more important.

If you want to run more then 600 players with 0 lag i am advicing you to go for 15k rpm hdds. I have two of them and without these i wouldnt be able to run 1000+.

The first harddisk is running my windows and has all my program files on it etc. The second harddisk is dedicated for my database. If you want performance you

should always do this. Will increase acces time allot and as l2j with allot of player on has many writes/reads its a must if you want lag free gameplay.

About the ram, 6 Gb should do fine have run on that for a long time.About the connection, 100mbit is more then enough.

 

OS, well i recommend using the 64bit version of windows server 2003. This way you can run your java and mysql in 64 bit wich speeds it up a bit.

Also, you can allocate more ram to your startup file but i will tell more about this later on.

 

 

2.Windows server 2003

 

So lets see, we got a awesome server machine wich is up and running with windows server 2003. I think we are ready for some configuration changes for windows.

The first thing you need to change is the resource allocating. Windows server sets it to background services by default.]

Although this might be very good for stuff like Exchange, we dont want it like this.

 

1.Other mouse button on my computer and select properties(new window will popup)

2.Click on the "Advanced" tab

3.You will see Performance with a button "settings...." Click on it.(new window will open)

4.Click on the "Advanced" tab

5.Now set Processor scheduling and Memory usage to "Programs".

6.Press apply and dont close the window yet cause we are also gonna change the pagefile size.

 

Ok now the resource allocation is correct. Now we are going to change the pagefile size. The pagefile is windows virtual memory wich is stored on the harddisk.

As the pagefile is used allot we want to increase it and we want to set it to a set value. That means setting the initial size the same as the maximum.

This is done cause this way you want have fragmentation with your page file and your hardisk doesnt have to resize it all the time wich creates extra reads and writes.

Lets continu where we left the Advanced tab open.

 

7.You will see Virtual Memory with a button that says "Change". Click on this.(New window will popup)

8.Now set it to custom size.

9.Windows advices you to take 1.5x your ram size as your page file. I am not following this and i am setting mine on 6114. Make sure that the initial size and maximum size are the same!

10.Once you have filled in the two valeus, press set and then apply.

11. Apply all and restart your computer.

 

If you want to give the pagefile optimal performance and you got an harddisk unused you can also change the location of the pagefile. This will give it a little bit more performance.

 

 

3.Mysql

 

Well well, we are at MySql now. Most people hate changing the config files but its really needed if you want a nice server.

Im not an expert with this but hours of reading and watching mysql workshops i came up with some stuff wich needs to be changed.

I will post parts of the Mysql config i am using so you will know what you need to change.

Although the main resource mysql wants is ram its not needed to set giant values at the ram settings.

This will only create a unwanted giant space usage in your page file. Just keep a look at the size of your database regulary and change the size of the ram setting according to it.

(example: My database is 200 mb in total, i will set my ram usage size to 512mb).

 

Shutdown your Mysql before changing anything!!!

 

Ok open your my.ini

(text between ----->blaatblaat<--- are my comments!

 

First setting you should check:

# The default storage engine that will be used when create new tables when

default-storage-engine=INNODB

 

-------->Set this to a high value, something like mine.

# The maximum amount of concurrent sessions the MySQL server will

# allow. One of these connections will be reserved for a user with

# SUPER privileges to allow the administrator to login even if the

# connection limit has been reached.

max_connections=600

 

 

-------->This can be set at 0, not used by l2j and only slows it down

# Query cache is used to cache SELECT results and later return them

# without actual executing the same query once again. Having the query

# cache enabled may result in significant speed improvements, if your

# have a lot of identical queries and rarely changing tables. See the

# "Qcache_lowmem_prunes" status variable to check if the current value

# is high enough for your load.

# Note: In case your tables change very often or if your queries are

# textually different every time, the query cache may result in a

# slowdown instead of a performance improvement.

query_cache_size=0

 

 

------>If your tables are getting big, you should locate more to this.This should be more then enough though!

# Maximum size for internal (in-memory) temporary tables. If a table

# grows larger than this value, it is automatically converted to disk

# based table This limitation is for a single table. There can be many

# of them.

tmp_table_size=256M

 

--------->setting this to 8mb is more then enough

# Additional memory pool that is used by InnoDB to store metadata

# information. If InnoDB requires more memory for this purpose it will

# start to allocate it from the OS. As this is fast enough on most

# recent operating systems, you normally do not need to change this

# value. SHOW INNODB STATUS will display the current amount used.

innodb_additional_mem_pool_size=8M

 

------>This one is tricky and i dont know wich one is the best, never had time to test it allot.

------>I do know that if you set it to "0" it will create major I/O spikes

------>I havent had any problems using option "2"

# If set to 1, InnoDB will flush (fsync) the transaction logs to the

# disk at each commit, which offers full ACID behavior. If you are

# willing to compromise this safety, and you are running small

# transactions, you may set this to 0 or 2 to reduce disk I/O to the

# logs. Value 0 means that the log is only written to the log file and

# the log file flushed to disk approximately once per second. Value 2

# means the log is written to the log file at each commit, but the log

# file is only flushed to disk approximately once per second.

innodb_flush_log_at_trx_commit=2

 

------->Not needed to be any higher then 16Mb, comment of mysql explains it

The size of the buffer InnoDB uses for buffering log data. As soon as

# it is full, InnoDB will have to flush it to disk. As it is flushed

# once per second anyway, it does not make sense to have it very large

# (even with long transactions).

innodb_log_buffer_size=16M

 

--------> Set this to the ammount of ram you have free for your database. At mine, 1024 is enough.

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and

# row data. The bigger you set this the less disk I/O is needed to

# access data in tables. On a dedicated database server you may set this

# parameter up to 80% of the machine physical memory size. Do not set it

# too large, though, because competition of the physical memory may

# cause paging in the operating system. Note that on 32bit systems you

# might be limited to 2-3.5G of user level memory per process, so do not

# set it too high.

innodb_buffer_pool_size=1024M

 

----------> I have always set this to 50% of my innodb_buffer_pool_size.

----------> Remember if you change this you need to delete your log files in order to start mysql again.

----------> They are located here: MySQL Server 5.0\data

----------> you should delete ib_logile0 and ib_logfile1 if you change this.

# Size of each log file in a log group. You should set the combined size

# of log files to about 25%-100% of your buffer pool size to avoid

# unneeded buffer pool flush activity on log file overwrite. However,

# note that a larger logfile size will increase the time needed for the

# recovery process.

innodb_log_file_size=512M

 

--------->The thread concurrency depends on your hardware.

--------->you should play around with it a bit but if you cpu is a powerfull one you can easily set this to 60

# Number of threads allowed inside the InnoDB kernel. The optimal value

# depends highly on the application, hardware as well as the OS

# scheduler properties. A too high value may lead to thread thrashing.

innodb_thread_concurrency=60

 

-----> Setting so mysql uses your memory instead of the pagefile

memlock

 

-----> Creates a file for every table. this creates a minor performance boost

-----> Remember, if you want this setting to work you have to add it to your config and then re-import your database again.

-----> Only that way it will create a file per table.

innodb_file_per_table

 

 

Ok that should cover mysql. I recommend getting a dedicated hardisk for your database. This will improve performance ALLOT!.

 

 

 

4.L2j Threadpool config

 

Well we are getting there, only a couple of things left to do and your good to go.Lets start with the threadpool config.

Here is defined how much threads can be created(Correct me if im wrong!).These settings have always been a mistery to me so i have experimented allot with them.

Before setting them really high you should once again consider your cpu. Dont set them to high if you dont have a fast cpu.

 

Open your options.properties file and look for this:

 

# ================================================== ===============

# Threads configuration - Take care changing this

# ================================================== ===============

 

ThreadPoolSizeEffects = 50

ThreadPoolSizeGeneral = 65

 

#Default 2

UrgentPacketThreadCoreSize = 10

#Default 4

GeneralPacketThreadCoreSize = 20

#Default 4

GeneralThreadCoreSize = 20

 

AiMaxThread = 20

 

------------------------------------------------------------------

 

I have set them 5x the normal values. This works great for my server but you should experiment with it.

Just start of with normal settings and see how it runs. If you think it lags and your cpu isnt used much just set it 2x normal values.

You should play around with this until you find a nice configuration for your hardware.

 

5.Other configurations

 

Ok now its time for some other configurations.

 

--------> This should not log items, wil suck up your I/O load. Logging chat well, also not doing that for the same reason.

# ================================================== ===============

# Logging features

# ================================================== ===============

# Logging ChatWindow

LogChat = False

# Logging Item handling NOTE: This can be very space consuming if enabled for all items.

LogItems = False

# Log GM actions

GMAudit = True

 

-------> Having them not running around can improve performance a bit

# Maximum range mobs can randomly go from spawn point

MaxDriftRange = 0

 

-------> Definitly set this to false!

# setting false can improve server performance on high rate servers

PreciseDropCalculation = False

 

-------> Dont know precisly wich is the best one but 1 has always worked great for me.

# This is setting of experimental Client <--> Server Player coordinates synchronization,

# 0 - no synchronization at all

# 1 - parcial synchronization Client --> Server only * using this option it is difficult for players to bypass obstacles

# 2 - parcial synchronization Server --> Client only

# 3 - full synchronization Client <--> Server

# -1 - Old system: will synchronize Z only

CoordSynchronize = 1

 

 

6.Startup parameters

 

Ok so everything is set to go just for one thing, your java startup parameters.

This is just like the thread pool config, they should be configured for your hardware.

There are a couple of things you need to think about.

First, if you have 32 bit java you cannot set your xmx and xms higher then 1536

Second, the -server parameter. You should only use this if you have 2 Cores or more and more then 2 GB ram! If you dont DO NOT USE this parameter.

The difference between starting your server in -server mode is that it runs waaaaaay better. Will have less lag and better resource usage. So if you can, always use this.

Other settings like ram all depend on how much you got. You should set these setting according to your ram size: -Xmx4096m -Xms2048m -Xmn1024m -XX:PermSize=256m.

At my server this works great and i havent touched this for ages.

 

 

title Game Server Console

:start

echo Starting L2J Game Server.

echo.

REM -------------------------------------

REM Default parameters for a basic server.

REM java -Xmx1024m -cp ./../libs/*;l2jserver.jar net.sf.l2j.gameserver.GameServer

REM

REM If you have a big server and lots of memory, you could experiment for example with

java -server -Xmx4096m -Xms2048m -Xmn1024m -XX:PermSize=256m -XX:SurvivorRatio=8 -Xnoclassgc -XX:+AggressiveOpts -cp ./../libs/*;l2jserver.jar net.sf.l2j.gameserver.GameServer

REM -------------------------------------

 

 

Ok thats it, a guide to configurate your server to be able to run 1000+ players. I have done it myself with this config with almost no lag.

If someone has a comment on it please let me know, also when you think i made a mistake or something.

The grammer in it well, dont have time to check it all so sorry if its not correct. Have fun with your gameserver.

 

 

Written by Nitrozik for the L2j Community

Posted

Thanks guyz. I found 3 threads like that but i found this one as more easy to understand so i posted it.

Posted

TY hackz0r But I Wanna Ask You Something

This Hardware How Many Money Will Take to buy it?????

plz in tell me in euro

 

Cpu: Quad Core Xeon 3220 - 2.40GHz (Kentsfield) - 2 x 4MB cache

MBram: 8 GB DDR2 667

HDD: 73GB SA-SCSI 15K RPM

HDD2: 73GB SA-SCSI 15K RPM

Connection: 1000mbit up/down

OS: Windows server 2003 64bit RC2

Posted

+1 from me

 

Mate don't spam

1st-You can't give karma

2nd- You comment thats what inside the thread not me or anything thanks.. ...

Guest
This topic is now closed to further replies.


  • Posts

    • ✔ We offer more services than listed. Prices of goods may vary depending on country, warranty, phone number, and other factors. We are available 24/7. ⠀⠀⠀⠀⠀⠀⣀⣠⣤⣀⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⣴⡿⠋⠉⠉⠻⢿⣦⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⢸⣿⠀⠀⠀⠀⠀⠀⠹⣷⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠈⣿⡄⠀⠀⠀⠀⠀⠀⢸⣇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠸⣷⠀⠀⠀⠀⠀⠀⢸⣿⠀⠀⢀⣀⣀⣀⣀⣀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀⠀⠀⠀⢻⣇⠀⠀⠀⠀⠀⢸⣿⣿⡿⠿⠿⠟⠛⠛⠻⢿⣿⣶⣄⠀⠀⠀ ⠀⠀⠀⠀⠀⢈⣿⠆⠀⠀⠀⠀⠀⠀⠀⠀⣀⣠⣤⣤⣤⣤⠀⠈⠻⣿⣇⠀⠀ ⠀⠀⠀⠀⢀⣾⡏⠀⠀⠀⠀⠀⠀⠀⣴⡿⠋⠉⠀⠀⠀⠀⠀⠀⠀⢹⡿⠀⠀ ⠀⠀⣀⣤⣼⣿⠀⠀⠀⠀⠀⠀⠀⢸⡟⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⣿⣷⣄⠀ ⢠⣾⠟⠋⠉⠋⠀⠀⠀⠀⠀⠀⠀⠈⣿⣦⣀⣀⣀⣤⣤⣶⣶⠿⠋⠁⢹ ⢸⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣴⡟⢉⣿⠋⠉⠉⠉⠁⠀⠀⠀⠀⢸⣿⠀ ⢸⣿⠀⠀⠀⠀⠀⢀⣀⣀⣤⣴⠿⠋⠀⠘⣷⡀⠀⠀⠀⠀⠀⠀⢀⣴⣿⠏⠀ ⢸⣿⡄⠀⠀⠀⠀⠈⠉⠉⠁⠀⠀⠀⠀⠀⣸⣿⢶⣤⣤⣴⡶⠿⠛⠙⣿ ⠈⣿⣇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢰⣿⠁⠀⠀⠀⠀⠀⠀⠀⠀⣽⣿⠀ ⠀⠘⣿⣆⠀⠀⠀⠀⣠⣤⡀⠀⠀⠀⠀⠈⠻⣧⣀⡀⠀⠀⠀⣀⣠⣴⡿⠇⠀ ⠀⠀⠘⢿⣿⣦⣤⣴⡿⠻⠿⣷⣦⣤⣤⣤⣴⣾⣿⡿⠿⠿⠿⠟⠛⠉⠀⠀⠀ ⠀⠀⠀⠀⠀⠀
    • Frozen is more popular coz adm can edit npc from client side and no need dig in xml and etc  )
    • Your work is as good as your arrogance. If you didn't break 10 systems to fix 1, I would recommend aCis. Yes, I use aCis and I fixed a lot of things that you left aside to reorganize and rename things. You insist on recommending your broken public project. Don't do that because there are many people who dream of owning a server, and in aCis 409 every dream is broken. I've seen many people break things by using this. aCis 409 doesn't work at the basics. Water movement and flying movements are broken, which is the basics. Seven Sings is completely broken, Sieges need fixing, and worst of all, level 3 and 4 clan quests are bugged, besides other quests that you intentionally broke and still recommend. You are an excellent programmer, but your arrogance in feeling superior to everyone is killing you. Happy New Year to you, and be more transparent and honest when recommending this. I'm not sharing the corrections I made, nor my Geodata system, precisely because of your arrogance. I'll soon post a video of my Geoengine system, which you spent 12 years on and didn't finish. I can send you a list of everything you need to fix, but you're too arrogant for that because you're a superior God and don't accept advice from mortals.
    • Changelog   All notable changes to this project will be documented in this file. [English Version](#english-version) | [Versión en Español](#versión-en-español)   ---   English Version   [1.1.3] - 2026-01-05   Added   Donation System Integration - Integrated comprehensive donation panel into the main CMS - Implemented direct donation system without requiring user login - Added automatic coin crediting directly to character inventory - Created new React component for donation interface with modern design - Implemented real-time coin calculation based on payment method and currency - Added support for multiple payment gateways:   - MercadoPago (ARS)   - PayPal (USD, BRL, EUR)   - PagSeguro (BRL) - Developed new backend endpoint for processing direct donations - Implemented character validation system before payment processing - Added automatic webhook handling for payment confirmations - Created comprehensive logging system for all donation transactions - Implemented bonus system for bulk coin purchases - Added donation history tracking and management   Vote Reward System - Integrated vote reward panel into the CMS - Implemented multi-topsite voting system - Added automatic reward delivery upon vote verification - Created vote tracking and cooldown management - Implemented anti-fraud measures for vote validation - Added vote history and statistics for users - Developed admin panel for vote reward configuration - Implemented automatic vote verification through topsite APIs   Database Enhancements - Created new table structure for donation management (`site_donations`) - Added `auto_credit` field for automatic coin delivery - Implemented balance tracking system (`site_balance`) - Created conversion and transfer logging tables - Added comprehensive indexing for performance optimization - Implemented transaction history tracking   Frontend Improvements - Developed new donation panel component with consistent site design - Added multi-language support (Spanish, English, Portuguese) - Implemented form validation and error handling - Created responsive design for mobile and desktop - Added real-time price calculation display - Implemented loading states and user feedback messages   Backend Infrastructure - Created secure API endpoints for donation processing - Implemented webhook system for payment gateway integration - Added comprehensive error logging and debugging tools - Developed configuration management system - Implemented security measures for sensitive data handling - Added support for sandbox and production environments   Documentation - Created comprehensive production setup guide - Developed security checklist for deployment - Added database setup scripts with detailed instructions - Created API integration documentation - Developed troubleshooting guides - Added configuration examples for all payment gateways   Changed - Updated navigation system to include donation and vote panels - Modified routing to support new panel pages - Enhanced translation system with new text strings - Improved error handling across the application - Updated proxy configuration for backend communication   Security - Implemented credential protection in configuration files - Added example configuration files without sensitive data - Created .htaccess rules for protecting sensitive directories - Implemented webhook signature validation - Added SQL injection prevention measures - Implemented session security enhancements   Technical Details - React 19.2.0 for frontend components - TypeScript for type safety - Vite 6.2.0 for build tooling - PHP 7.4+ for backend processing - SQL Server 2012+ for database management - Integration with MercadoPago SDK - RESTful API architecture   ---   Versión en Español   [1.1.3] - 2026-01-05   Agregado   Integración del Sistema de Donaciones - Integración completa del panel de donaciones al CMS principal - Implementación de sistema de donaciones directas sin requerir inicio de sesión - Agregada acreditación automática de coins directamente al inventario del personaje - Creación de nuevo componente React para interfaz de donaciones con diseño moderno - Implementación de cálculo de coins en tiempo real según método de pago y moneda - Agregado soporte para múltiples pasarelas de pago:   - MercadoPago (ARS)   - PayPal (USD, BRL, EUR)   - PagSeguro (BRL) - Desarrollo de nuevo endpoint backend para procesamiento de donaciones directas - Implementación de sistema de validación de personajes antes del procesamiento de pago - Agregado manejo automático de webhooks para confirmaciones de pago - Creación de sistema completo de logs para todas las transacciones de donación - Implementación de sistema de bonos para compras de coins en volumen - Agregado seguimiento y gestión de historial de donaciones   Sistema de Recompensas por Votación - Integración del panel de recompensas por votación al CMS - Implementación de sistema de votación multi-topsite - Agregada entrega automática de recompensas al verificar votos - Creación de seguimiento de votos y gestión de tiempos de espera - Implementación de medidas anti-fraude para validación de votos - Agregado historial de votos y estadísticas para usuarios - Desarrollo de panel administrativo para configuración de recompensas - Implementación de verificación automática de votos mediante APIs de topsites   Mejoras en Base de Datos - Creación de nueva estructura de tablas para gestión de donaciones (`site_donations`) - Agregado campo `auto_credit` para entrega automática de coins - Implementación de sistema de seguimiento de balance (`site_balance`) - Creación de tablas de registro de conversiones y transferencias - Agregada indexación completa para optimización de rendimiento - Implementación de seguimiento de historial de transacciones   Mejoras en Frontend - Desarrollo de nuevo componente de panel de donaciones con diseño consistente - Agregado soporte multi-idioma (Español, Inglés, Portugués) - Implementación de validación de formularios y manejo de errores - Creación de diseño responsive para móvil y escritorio - Agregada visualización de cálculo de precios en tiempo real - Implementación de estados de carga y mensajes de retroalimentación al usuario   Infraestructura Backend - Creación de endpoints API seguros para procesamiento de donaciones - Implementación de sistema de webhooks para integración con pasarelas de pago - Agregadas herramientas completas de registro de errores y depuración - Desarrollo de sistema de gestión de configuración - Implementación de medidas de seguridad para manejo de datos sensibles - Agregado soporte para entornos sandbox y producción   Documentación - Creación de guía completa de configuración para producción - Desarrollo de checklist de seguridad para despliegue - Agregados scripts de configuración de base de datos con instrucciones detalladas - Creación de documentación de integración de APIs - Desarrollo de guías de solución de problemas - Agregados ejemplos de configuración para todas las pasarelas de pago   Modificado - Actualización del sistema de navegación para incluir paneles de donación y votación - Modificación del enrutamiento para soportar nuevas páginas de paneles - Mejora del sistema de traducciones con nuevas cadenas de texto - Mejora del manejo de errores en toda la aplicación - Actualización de configuración de proxy para comunicación con backend   Seguridad - Implementación de protección de credenciales en archivos de configuración - Agregados archivos de configuración de ejemplo sin datos sensibles - Creación de reglas .htaccess para proteger directorios sensibles - Implementación de validación de firma de webhooks - Agregadas medidas de prevención de inyección SQL - Implementación de mejoras de seguridad en sesiones   Detalles Técnicos - React 19.2.0 para componentes frontend - TypeScript para seguridad de tipos - Vite 6.2.0 para herramientas de construcción - PHP 7.4+ para procesamiento backend - SQL Server 2012+ para gestión de base de datos - Integración con SDK de MercadoPago - Arquitectura API RESTful   ---   Migration Notes / Notas de Migración   For Existing Installations / Para Instalaciones Existentes   **English:** If you are upgrading from a previous version, please follow these steps: 1. Backup your database before applying any changes 2. Run the database migration script (`database_setup.sql`) 3. Update your configuration file with new settings 4. Configure payment gateway credentials 5. Test the donation flow in sandbox mode before going to production 6. Review the security checklist before deployment   **Español:** Si está actualizando desde una versión anterior, siga estos pasos: 1. Realice una copia de seguridad de su base de datos antes de aplicar cambios 2. Ejecute el script de migración de base de datos (`database_setup.sql`) 3. Actualice su archivo de configuración con las nuevas opciones 4. Configure las credenciales de las pasarelas de pago 5. Pruebe el flujo de donaciones en modo sandbox antes de pasar a producción 6. Revise el checklist de seguridad antes del despliegue   ---   Known Issues / Problemas Conocidos   **English:** - Webhook notifications may experience delays during high traffic periods - Some payment gateways require manual configuration of webhook URLs - Character names are case-sensitive in the donation form   **Español:** - Las notificaciones de webhook pueden experimentar retrasos durante períodos de alto tráfico - Algunas pasarelas de pago requieren configuración manual de URLs de webhook - Los nombres de personajes son sensibles a mayúsculas/minúsculas en el formulario de donación   ---   Roadmap / Hoja de Ruta   Planned Features / Características Planeadas   **English:** - Admin dashboard for donation management - Automated refund processing - Subscription-based donations - Gift card system - Enhanced reporting and analytics - Mobile application support   **Español:** - Panel administrativo para gestión de donaciones - Procesamiento automatizado de reembolsos - Donaciones basadas en suscripción - Sistema de tarjetas de regalo - Reportes y análisis mejorados - Soporte para aplicación móvil   ---   Contributors / Contribuidores   This release includes contributions from the development team focused on creating a secure, user-friendly donation and voting system integrated seamlessly with the existing CMS.   Este lanzamiento incluye contribuciones del equipo de desarrollo enfocado en crear un sistema de donaciones y votación seguro y fácil de usar, integrado perfectamente con el CMS existente.   ---   Support / Soporte   **English:** For issues, questions, or feature requests, please refer to: - `PRODUCTION_SETUP_GUIDE.md` for setup instructions - `SECURITY_CHECKLIST.md` for security guidelines - `DONATION_DIRECT_SYSTEM.md` for technical documentation   **Español:** Para problemas, preguntas o solicitudes de características, consulte: - `PRODUCTION_SETUP_GUIDE.md` para instrucciones de configuración - `SECURITY_CHECKLIST.md` para pautas de seguridad - `DONATION_DIRECT_SYSTEM.md` para documentación técnica   ---   License / Licencia   This project maintains its original licensing terms. Please refer to the LICENSE file for details.   Este proyecto mantiene sus términos de licencia originales. Consulte el archivo LICENSE para más detalles.   ---   **Last Updated / Última Actualización:** January 5, 2026   **Version / Versión:** 1.1.3
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..

AdBlock Extension Detected!

Our website is made possible by displaying online advertisements to our members.

Please disable AdBlock browser extension first, to be able to use our community.

I've Disabled AdBlock