Share [Autobots] Lucera2 PvP+PvE+OLYMPIAD

[Dimaris]

AI is future !!!!

Кловен

 

[Smotritel]

Жопагорящие парни которые недавно вкатились в IT-техноложис и начали зарабатывать по 20$ с рыла, а тут ещё и ИИ выкатили КАКОЙ УЖАС, скоро на помойку)))

 

[Hellcat]

UPDATE M84:

• Changed Party Logic to optional:
  • Allow Party: No / Yes to Autobot creation.
  • Default is No.
  • Added persisted database field:
    • allow_party
    • 0 = No
    • 1 = Yes
  • Existing saved bots default to party-disabled.
  • Yes preserves existing real-player Party Logic behavior.
• Olympiad bots remain party-disabled.
• Added autobots_path.xml.
  • Added per-saved-bot custom death-return routes.
  • Added configurable <start> XYZ.
  • Added ordered custom <point> waypoints.
  • Added native Scroll of Escape fallback for failed custom routes.
  • Added maximum 256 waypoints per bot.
  • Prevented repeated formatting growth after subsequent saves.
  • Improved startup synchronization so saved-bot XML entries are handled in a single document operation instead of repeatedly rewriting the XML.
  • Fixed saved bots ignoring populated custom paths.
  • Route is now resolved from AutobotPathRepository using the bot's saved database ID when recovery begins.
  • Route definition is frozen for the current recovery cycle.
  • Replaced overly strict initial GeoEngine waypoint rejection with actual movement-progress detection.
  • Bot now attempts to physically travel toward each configured waypoint.
  • Bad waypoint detection uses a maximum 5-second no-progress window and prints a warning on the gameserver console.
  • Combat temporarily pauses route movement without restarting the route.
  • After combat, the bot continues from the same waypoint with a fresh stuck timer.

You can download the extension and view all the details regarding the latest Autobots in the original post of this thread.

 

[Sami]

This system has been around for a long time in certain circles and on certain servers)
Why would Dizer waste time on something he doesn't need?
You can't even imagine how global and large the code is; the author, using AI, implemented a superficial piece of code that's only 1-2% of the full volume.

It’s not a waste of time or anything like that; it’s about giving the project an update. It’s a contribution from someone—regardless of whether AI was used or not—that Lucera doesn't currently offer. If Lucera *did* offer it, then fair enough—criticize away. But right now, Lucera’s fake system or bot is abysmal. It makes no sense.

That’s why the Lucera team could take user feedback like this and use it as a basis for implementation. I can guarantee that 50% of Lucera users want a functional bot—ideally one released by the developer themselves—rather than relying on experimental tests with external tools that might not work reliably.

So, my point is: instead of being negative, they should use this as an example and update the default bot system. All the best.

 

[Project-X]

It’s not a waste of time or anything like that; it’s about giving the project an update. It’s a contribution from someone—regardless of whether AI was used or not—that Lucera doesn't currently offer. If Lucera *did* offer it, then fair enough—criticize away. But right now, Lucera’s fake system or bot is abysmal. It makes no sense.

That’s why the Lucera team could take user feedback like this and use it as a basis for implementation. I can guarantee that 50% of Lucera users want a functional bot—ideally one released by the developer themselves—rather than relying on experimental tests with external tools that might not work reliably.

So, my point is: instead of being negative, they should use this as an example and update the default bot system. All the best.

В

It’s not a waste of time or anything like that; it’s about giving the project an update. It’s a contribution from someone—regardless of whether AI was used or not—that Lucera doesn't currently offer. If Lucera *did* offer it, then fair enough—criticize away. But right now, Lucera’s fake system or bot is abysmal. It makes no sense.

That’s why the Lucera team could take user feedback like this and use it as a basis for implementation. I can guarantee that 50% of Lucera users want a functional bot—ideally one released by the developer themselves—rather than relying on experimental tests with external tools that might not work reliably.

So, my point is: instead of being negative, they should use this as an example and update the default bot system. All the best.

Это не выгодно и не интересно разработчику ( Дизер давно придерживается нейтральной политики в этом плане)
Пользователям дали все инструменты для создания стороннего контента на свой вкус любые дополнения можете запилить самостоятельно нету ограничений( все упирается в ваши знания или $ возможности )
На рынке много вариантов ботов / Но не один здравый предприниматель не продаст курицу которая несёт золотые яйца за пару сотен $