Jump to content

Recommended Posts

Posted (edited)

A server console with a small patch integraded for all chronicles for autoreward system.

 

My package contains

The jar that console uses.

1 Sql file that holds the votes.

1 patch for the vote system you have.

1 Configuration file.

 

Setup free via team viewer

PS: it works after the latest hopzone change and almost all systems not working

 

Why i sell this and whats the point of this console:

This console has some differences from the shared codes i will say some examples

You can have it on other computer (less ram/cpu)

Libraries not load on game server -> less libraries since they moved on that console for the specific purpose to load less ram faster cpu and script excecution time

Console checks hopzone and it uses database 1 time per checktime (30sec) or what you want

Less database communication from the shared systems are shared arround

You know the fix for topzone is 10mb libs more... i mean thats not so good for loading in a game server isnt it?

PLUS

The patch removes imports from some java libraries nessesary to connect on votesites also and they wont need to load on game server

 

My comments: some ppl might find this unusfull but when i can do something little more faster i do it, because when you have 50 players online it wont lag.. but if you have more than 200-300 players you look even the smallest thing to remove to gain some speed, with that said i think i answer some questions.

 

 

Configs:

# Url's Check
TimeCheck = 30

# Debug
Debug = False

# Url's
URLHop=http://l2.hopzone.net/lineage2/details/96034/L2-Tales
URLTop=http://l2topzone.com/lineage2/server-info/8703/L2ExtremeCustomPVP.html

# Database Settings
Host = localhost
Port= 3306
DBName = l2jhellas
DBUser = root
DBPass =

Photo :

opMRxpX.png

No source 10Euro (You cant add more vote sites, no support)

Source 30Euro (More vote sites and i provide updates)

addskype.png?u=nightwol.black&c=gray

Edited by Nightw0lf
Posted (edited)

For this shit 50 euros?

you have big audacity to say something like that, if you do that in your real life when you go to a store or something thats has nothing to do with my program instead it has to do with your parrents and the way they rise you, go back on your tree ape.

 

 

whats the difference between source and no source?

the difference is that you can edit the source when you have it, to add more sites instead of hopzone and topzone.

 

 

 

basically, whats the difference from the shared version? only the fix for hopzone and the saved data in db??

it has some differences from the shared i will say some examples

you can have it on other computer (less ram/cpu)

it not loads on game server less libraries since they moved on that server for the specific purpose to load less ram faster cpu and script excecution time

it checks hopzone and it uses database 1 time per checktime (30sec) or what you want

less communication from the shared systems

if you know the fix for topzone is 10mb libs more... i mean thats not so good for loading in a game server isnt it?

 

edit:

the patch removes imports from some java libraries also and they wont need to load on game server

 

some ppl might find this unusfull but when i can do something little more faster i do it, because when you have 50 players online it wont lag.. but if you have more than 200-300 players you look even the smallest thing to remove to gain some speed, with that said i think i answer some questions.

Edited by Nightw0lf
Posted (edited)

you have big audacity to say something like that, if you do that in your real life when you go to a store or something thats has nothing to do with my program instead it has to do with your parrents and the way they rise you, go back on your tree ape.

 

 

the difference is that you can edit the source when you have it, to add more sites instead of hopzone and topzone.

 

 

 

it has some differences from the shared i will say some examples

you can have it on other computer (less ram/cpu)

it not loads on game server less libraries since they moved on that server for the specific purpose to load less ram faster cpu and script excecution time

it checks hopzone and it uses database 1 time per checktime (30sec) or what you want

less communication from the shared systems

if you know the fix for topzone is 10mb libs more... i mean thats not so good for loading in a game server isnt it?

 

edit:

the patch removes imports from some java libraries also and they wont need to load on game server

 

some ppl might find this unusfull but when i can do something little more faster i do it, because when you have 50 players online it wont lag.. but if you have more than 200-300 players you look even the smallest thing to remove to gain some speed, with that said i think i answer some questions.

about topzone fix no i dont know. i ask the differences from shared version and i take the answer. but write the differences in your sell topic because the configs looks same like shared version :)

 

edit: I forgot to say you good luck with your sales :)

Edited by nikosdevil20
Posted

about topzone fix no i dont know. i ask the differences from shared version and i take the answer. but write the differences in your sell topic because the configs looks same like shared version :)

 

edit: I forgot to say you good luck with your sales :)

yes you have a point thank you i will update it

Posted (edited)

so we cant edit jar files?

 

and about libs they arent loaded unless u call them so there is no difference, the only difference your engine got is a splitted console and source which is more viable in many cases

Edited by brut
Posted (edited)

so we cant edit jar files?

 

and about libs they arent loaded unless u call them so there is no difference, the only difference your engine got is a splitted console and source which is more viable in many cases

"they arent loaded unless u call them"

"the only difference your engine got is a splitted console"

you are way missinformed read again the topic and some java.

 

and NO you cannot edit the jar.

edit:

well i will help you search your mistake in google

type exception java.lang.noclassfounderror

Edited by Nightw0lf
Posted (edited)

i guess u worked on that a month, which is 20lines code, and the fact that u cant even edit jar files proves that u have no knowledge on java

and dont try to troll me again or ull see that code shared after a hour

Edited by brut
Posted

Let me understand. This code is checking vote count on Hopzone and Topzone every 30 seconds and when difference between last checked count(saved in database too) and new count is >= x, then all players are rewarded right?

 

If i am correct then:

 - 10 mb of new code to make Topzone work too? WTF?

 - How shared version of this code could affect performance when many players are online on the server?

 - "You can have it on other computer" - your code is so heavy for PC that it is better to more it to other machine? :O

 

Give more info please because you can see by yourself this doesn't make sense :P

Posted (edited)

What is all this? o.O

a wannabe that troll us with nonsense, i loved the part source and no-source, and the explanation with google quote that class files are finalized and cannot be reverted for editing o.O

 

he's probably offering along with "his" engine a new java version with class file encoding, or an engine with server conectivity where the files are hosted o.O which would be totally useless cuz the base of that vote reward engine is already shared.

 

so what actually he offers? the shared engine in a new console? o.O

 

This console has some differences from the shared codes i will say some examples

You can have it on other computer (less ram/cpu)

Libraries not load on game server -> less libraries since they moved on that console for the specific purpose to load less ram faster cpu and script excecution time

Console checks hopzone and it uses database 1 time per checktime (30sec) or what you want

Less database communication from the shared systems are shared arround

You know the fix for topzone is 10mb libs more... i mean thats not so good for loading in a game server isnt it?

PLUS

The patch removes imports from some java libraries nessesary to connect on votesites also and they wont need to load on game server

 

My comments: some ppl might find this unusfull but when i can do something little more faster i do it, because when you have 50 players online it wont lag.. but if you have more than 200-300 players you look even the smallest thing to remove to gain some speed, with that said i think i answer some questions.

 

compared to your ram and cpu theory and saving some microseconds in your version we have one more threadpool and sql connection per cycle which is in core

 

normal one > save data to sql each cycle, load sql data only on gs loading

yours         > save data to sql each cycle, load sql data every single cycle by core

xD

 

i wont even bother my self checking your post anymore, GOOD LUCK with your sales and your theories

Edited by brut
Posted

i guess u worked on that a month, which is 20lines code, and the fact that u cant even edit jar files proves that u have no knowledge on java

and dont try to troll me again or ull see that code shared after a hour

for you might took a month i actually worked it 1 day to find a fix for hopzone the rest xm dont remember

yes there is a more in compile than you see and you cant edit jar

throw me shit like i dont know like you know me shows alot

 

Let me understand. This code is checking vote count on Hopzone and Topzone every 30 seconds and when difference between last checked count(saved in database too) and new count is >= x, then all players are rewarded right?

 

If i am correct then:

 - 10 mb of new code to make Topzone work too? WTF?

 - How shared version of this code could affect performance when many players are online on the server?

 - "You can have it on other computer" - your code is so heavy for PC that it is better to more it to other machine? :o

 

Give more info please because you can see by yourself this doesn't make sense :P

10mb for hopzone because if you have server your hopzone reward propably not working

you didnt understand a think from the first topic i already answer the qeustions

and no its not heavy i dont say "You can have it on other computer" because the server is heavy

i say "You can have it on other computer" because your game server can have more memory and less threads if you remove anything isnt that right?

 

 

 

a wannabe that troll us with nonsense, i loved the part source and no-source, and the explanation with google quote that class files are finalized and cannot be reverted for editing o.O

 

he's probably offering along with "his" engine a new java version with class file encoding, or an engine with server conectivity where the files are hosted o.O which would be totally useless cuz the base of that vote reward engine is already shared.

 

so what actually he offers? the shared engine in a new console? o.O

 

This console has some differences from the shared codes i will say some examples

You can have it on other computer (less ram/cpu)

Libraries not load on game server -> less libraries since they moved on that console for the specific purpose to load less ram faster cpu and script excecution time

Console checks hopzone and it uses database 1 time per checktime (30sec) or what you want

Less database communication from the shared systems are shared arround

You know the fix for topzone is 10mb libs more... i mean thats not so good for loading in a game server isnt it?

PLUS

The patch removes imports from some java libraries nessesary to connect on votesites also and they wont need to load on game server

 

My comments: some ppl might find this unusfull but when i can do something little more faster i do it, because when you have 50 players online it wont lag.. but if you have more than 200-300 players you look even the smallest thing to remove to gain some speed, with that said i think i answer some questions.

 

compared to your ram and cpu theory and saving some microseconds in your version we have one more threadpool and sql connection per cycle which is in core

 

normal one > save data to sql each cycle, load sql data only on gs loading

yours         > save data to sql each cycle, load sql data every single cycle by core

xD

 

i wont even bother my self checking your post anymore, GOOD LUCK with your sales and your theories

i troll only apes that throw shit on others without even know some things

i will answer as much detailed as i can so an ape like you can understand

yes finalized no edit

no i am not offering any engine no server connectivity the console is not connected to anything (you can cry because i created it)

WHY NOT CHECKING MY POST YOUR OTHER APE FRIENDS WILL MISS YOU COME BACK! I CAN START COMING ON YOUR POSTS !

 

oh i forgot

 

normal one > save data to sql each cycle, load sql data only on gs loading

yours         > save data to sql each cycle, load sql data every single cycle by core

xD

 

 

now lets see

every cycle a normal shared system checks :

1 hopzone (connections http/SQL)

2 topzone (connections http/SQL)

 

mine

1 hopzone (connections removed/SQL) along with the jar imports for http

1 hopzone (connections removed/SQL) along with the jar imports for http

 

i could say more but i think you wouldnt understand

Posted (edited)

10mb for hopzone because if you have server your hopzone reward propably not working

you didnt understand a think from the first topic i already answer the qeustions

and no its not heavy i dont say "You can have it on other computer" because the server is heavy

i say "You can have it on other computer" because your game server can have more memory and less threads if you remove anything isnt that right?

My friend... i asked you if i understood correctly and the visible effects of your system are the same as shared version(except performance) and it looks like they are(please prove me wrong).

 

- This code(for Hopzone and for Topzone) can be done and fully working WITHOUT adding some 10mb of bullshit

- 1 Thread running every 30 seconds and checking for vote count is NOTHING - it would be something if you would run it on PC made out of wood and i think admins are running servers on dedicated machines...

- Of course .JAR can be opened, if you don't believe so you can send me the jar and i will send you it's source :)

Edited by vampir
Posted (edited)

the problem is that you didnt understand that i dont sell the console i mostly want to sell the fix for hopzone that the console consept is based on.

the plus parts are only plus parts nothing more nothing has to do with the jar or the source or anything else.

about the jar i open you a private discution and i will tell you there why i am negative.

Edited by Nightw0lf

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • 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