Jump to content

Recommended Posts

Posted

Hello, i want to ask someone who know from Freya or previous the Map Regions are in SQL as you see bellow 

yE8aO18.png

With some sec1, sec2, sec3 which i don't understand what they are.

 

I've noticed that in H5 they dropped this and move the regions to xmls in mapregion/ and now they are like this:

 

<region name="aden_town" town="Aden Castle Town" castle="5" locId="924" bbs="13">
		<respawnPoint X="146494" Y="30584" Z="-2420" />
		<respawnPoint X="146038" Y="30519" Z="-2420" />
		<respawnPoint X="148112" Y="30439" Z="-2420" />
		<respawnPoint X="148565" Y="30463" Z="-2420" />
		<respawnPoint X="150227" Y="29104" Z="-2420" />
		<respawnPoint X="144626" Y="29145" Z="-2420" />
		<respawnPoint X="144635" Y="26664" Z="-2220" />
		<respawnPoint X="144526" Y="24661" Z="-2100" />
		<respawnPoint X="144559" Y="22835" Z="-2100" />
		<respawnPoint X="145686" Y="21114" Z="-2100" />
		<respawnPoint X="148946" Y="21121" Z="-2070" />
		<respawnPoint X="148010" Y="27996" Z="-2256" />
		<respawnPoint X="147970" Y="27040" Z="-2191" />
		<respawnPoint X="146814" Y="27108" Z="-2189" />
		<respawnPoint X="146819" Y="28063" Z="-2252" />
		<respawnPoint X="136398" Y="28901" Z="-3582" isChaotic="true" />
		<respawnPoint X="137292" Y="28485" Z="-3290" isChaotic="true" />
		<respawnPoint X="155925" Y="28554" Z="-3164" isChaotic="true" />
		<respawnPoint X="157608" Y="23866" Z="-3760" isChaotic="true" />
		<respawnPoint X="157463" Y="28770" Z="-3371" isChaotic="true" />
		<respawnPoint X="159348" Y="28561" Z="-3400" isChaotic="true" />
		<respawnPoint X="160236" Y="14119" Z="-3892" isChaotic="true" />
		<respawnPoint X="156764" Y="13774" Z="-3960" isChaotic="true" />
		<respawnPoint X="161426" Y="23055" Z="-3670" isChaotic="true" />
		<respawnPoint X="136380" Y="21899" Z="-3647" isChaotic="true" />
		<respawnPoint X="137708" Y="15640" Z="-3800" isChaotic="true" />
		<respawnPoint X="136629" Y="28127" Z="-3258" isChaotic="true" />
		<map X="23" Y="18" />
		<map X="24" Y="17" />
		<map X="24" Y="18" />
		<map X="24" Y="19" />
		<map X="25" Y="17" />
		<map X="25" Y="18" />
		<map X="25" Y="19" />
	</region>

 

I need someone to enlight me. What are those numbers? Why H5 has different numbers than freya? If i want to drop SQl and move them to xml regions as H5 did

how should i write down?  

 

Thanks.

Posted (edited)
13 minutes ago, SweeTs said:

Why don't you ask, directly, to someone from L2J team? I guess it's your only option.

 

Tell me 1 person from L2J who talk directly? Sdw? This guy is like he took marijuana all day. Only if i add anime girls and kawai photos he will enter to comment. :D

Really i need drop this SQL since is ugly sec1,sec2,sec3 and make it in XML but i dont know what those numbers mean or how it should be the structure of it. 

 

http://www.youtube.com/watch?v=ykcn1OL-8eg&t=1m06s

Edited by Evie Frye
Posted (edited)
10 minutes ago, Evie Frye said:

 

Tell me 1 person from L2J who talk directly? Sdw? This guy is like he took marijuana all day. Only if i add anime girls and kawai photos he will enter to comment. :D

Really i need drop this SQL since is ugly sec1,sec2,sec3 and make it in XML but i dont know what those numbers mean or how it should be the structure of it. 

I'm not a master (actually, I don't know sh1t about it) but can't you see the whole problem backwards? Check the table's variables, what's their module, etc...Check your source to see the way the table is created and also how the xml file and the table are connected. It might lead you somewhere..

Edited by protoftw
  • Like 1
Posted (edited)
7 minutes ago, protoftw said:

I'm not a master (actually, I don't know sh1t about it) but can't you see the whole problem backwards? Check the table's variables, what's their module, etc...Check your source to see the way the table is created and also how the xml file and the table are connected. It might lead you somewhere..

 

Aww so kind that you answered. I'll suggest you for moderator instead of this nab @SweeTs who send me cat's nude everyday on skype. 

Well the problem is that i want to transfer those values to xml no change the code. So example H5 right now have a dedicated folder data/mapregion/ 

and inside has few xml like elf_town.xml , fantasy_island.xml, dwarf_town.xml which each one contains respawnPoint data and map X-Y. I guess those

X-Y are the region's. So in freya i want basically to move the regions to TownZones xmls or idk but i dont even know which values should be there.

 

Ps. i dont know why Freya has different values than H5 regions. I mean i check H5 X-Y and i try find similar to Freya's SQL but for example 34 does not exist. Does H5 has different region than Freya? o.O 

 

Edited by Evie Frye
Posted (edited)
8 minutes ago, Evie Frye said:

 

Aww so kind that you answered. I'll suggest you for moderator instead of this nab @SweeTs who send me cat's nude everyday on skype. 

Well the problem is that i want to transfer those values to xml no change the code. So example H5 right now have a dedicated folder data/mapregion/ 

and inside has few xml like elf_town.xml , fantasy_island.xml, dwarf_town.xml which each one contains respawnPoint data and map X-Y. I guess those

X-Y are the region's. So in freya i want basically to move the regions to TownZones xmls or idk but i dont even know which values should be there.

 

I don't want to rework the whole system of Respawn and blabla. I'm lazy.

Well, I'm confused even reading this. Nah, nah I get it :) . I guess in order to have a folder in data/xxxx there should be a path in java to read it and allow you to use it..Check the source of h5 and the way they implemented this and follow their steps.Take a town that is the same in both clients (h5,freya) , copy its xml which h5 is currently using in data/mapregion/ and paste it to your data/mapregion. Do all the lazy work you have to do when it comes to java and the most important , I wish you luck and may you find a solution :P

Edited by protoftw
Posted
9 hours ago, protoftw said:

Well, I'm confused even reading this. Nah, nah I get it :) . I guess in order to have a folder in data/xxxx there should be a path in java to read it and allow you to use it..Check the source of h5 and the way they implemented this and follow their steps.Take a town that is the same in both clients (h5,freya) , copy its xml which h5 is currently using in data/mapregion/ and paste it to your data/mapregion. Do all the lazy work you have to do when it comes to java and the most important , I wish you luck and may you find a solution :P

 

Np ill check Celsa's photo thanks for ur respond little.

 

8 hours ago, Celsas said:

I dont know how to say it in words :) but i make a image, maybe you understand something ;)

 

Oh i kinda start getting the idea, thanks ill check it tonight and tell you.

Posted

The SQL table is simply a matrice X/Y, similar to mapRegions.xml of aCis. It references point of teleport when you die or use a SoE. If the point is valid, it uses the associated list of teleport locations - karma list if you're PK, regular list otherwise.

Posted
8 hours ago, Tryskell said:

The SQL table is simply a matrice X/Y, similar to mapRegions.xml of aCis. It references point of teleport when you die or use a SoE. If the point is valid, it uses the associated list of teleport locations - karma list if you're PK, regular list otherwise.

 

Thanks. So the 1st cell is the Y value and all the other is the X? 

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
    • Dragonic 2 – High Five is a fully custom private server, built with an original visual identity and integrated premium systems. We offer a stable, modern, and optimized experience, combining classic High Five gameplay with new features created especially for the community. The server is live and available to all players. You can access the official website here:  https://dragonic2.com/ If you encounter any bugs or issues, please report them so we can fix them as quickly as possible. Join the adventure and discover Dragonic 2 — High Five.
  • Topics

×
×
  • Create New...

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