Jump to content

Recommended Posts

Posted

BWE2_header.jpg

Heroes of Tyria!

 

My name is Chris Whiteside, and I’m the lead producer of Guild Wars 2. Normally, I’m head-down in the trenches, making sure we’re producing the best MMO possible, but I wanted to come up for air and share some exciting news with you:

 

Beta Weekend Event 2 will begin on Friday, June 8th, at noon PDT (GMT-7) and will run until Sunday, June 10th, at 11:59 p.m. PDT (GMT-7).

 

 

If that isn’t enough to get you all bursting with excitement, here is some more news:

 

Your existing beta characters have not been deleted, and you will be able to continue right where you left off! This means that enterprising players with characters level 35 or higher will be able to test their mettle against the explorable version of the Ascalonian Catacombs dungeon!

 

In addition to sharing this news with you, I want to convey a massive “thank you” to all of you for playing in our beta events so far. The participation and enthusiasm we’ve seen has exceeded our expectations, and we’re all very grateful and appreciative here at the studio. Your support during our first Beta Weekend Event and throughout development has been instrumental in getting us prepared for launch and helping us take massive steps in the evolution of Guild Wars 2 as a whole. You, our community, are an integral part of the development process, and Guild Wars 2 simply would not be what it is today without you.

 

Your participation is even more important when you consider that we take our beta events very seriously in terms of our development strategy. At ArenaNet, “beta event” means exactly that—it’s a development-centric event in which we test our systems, discover new and exciting bugs, and get pivotal feedback from our testers about what is going in the right direction and what isn’t.

 

We have listened intently to all of your feedback from our first Beta Weekend Event, and we’ve made great strides toward resolving many of the issues you’ve helped us identify. These include party movement into overflow servers, chat functionality, key bindings, server stability, performance, and many more that we will detail in the near future.

Norn-Guardian-600x308.jpg

Of course, there’s no denying the benefits of having such a vocal, outspoken community. And I’m not speaking just in terms of development; I’m also referring to how our players are spreading the word that Guild Wars 2 is more than just a game, it’s an evolving, online world that is shaped and driven by its players. Our community and our studio won’t accept anything less than excellence, and above all else, we both value a pioneering approach to the future of online worlds.

 

Having said all that, what is the one thing we most look forward to in our second Beta Weekend Event? In a nutshell, it’s getting the chance to play with you all: sharing a world we’ve built together, discovering what’s great and what could be better, and defining a ground-breaking world that we can all enjoy for many years to come. That’s what these beta events mean to us.

 

 

Source :http://www.arena.net/blog/announcing-the-next-guild-wars-2-beta-weekend

Posted

Yes thx god,i cant wait till then..the only bad is that it starts 6:00 on the morning GMT +2 greek time the next day and it ends on Monday 8:59 in the morning ;)..but still i cant wait.!

  • 6 months later...
Guest
This topic is now closed to further replies.


  • Posts

    • Update M54: Global HP/MP/CP consumable handling expanded beyond combat-only usage. Offensive mage idle recovery with learned skill Battle Heal. Spellhowler/Storm Screamer prioritizes Hurricane, using Vampiric Claw mostly below 90% HP. Major structural refactor initialized: Added category/class organization such as Archer, Dagger, Tank, Mage, Healer, Support and Specialized class files. Further structural cleanup. Extracted combat memory/state and more class-policy logic from the main controller. Added global stuck/inactivity watchdog for bots blocked by terrain/geodata. Added unreachable dropped ground-item timeout/temporary blacklist. Reworked Necromancer/Soultaker PvP: Dominator level 78+ maintains learned Arcane Power toggle on. Overlord/Dominator level 44+ maintains learned Soul Guard toggle automatically. Stability/scalability update: Bot controller ticks staggered instead of all starting in the same phase: Same 350 ms update rate retained Reduces simultaneous AI workload bursts. Removed the old manual aggressive-monster EVT_AGGRESSION bridge. Phantoms now use native Lucera setActive() behavior so monsters aggro them naturally. Reduced unnecessary NPC scans and native AI event pressure. Added saved-bot equipment overrides using a separate database table:         lucera_autobots_items Existing lucera_autobots remains the main saved-bot identity/state table. Equipment rows are linked to saved bots through bot_id. Added optional convenience view to show bot name together with equipment overrides:         lucera_autobots_items_view Added editable equipment slots in columns: Weapon Shield Helmet Chest Legs Gloves Boots Necklace Left/Right Earrings Left/Right Rings Equipment override values: 0 = use normal class/level profile item -1 = force slot empty >0 = equip that Item ID Custom equipment works only for saved database bots. Default class/level equipment profiles remain unchanged. Supports custom equipment from No Grade to S Grade, regardless of the bot's current level. Added validation for invalid item IDs and incompatible equipment slots. Added handling for: Two-handed weapons vs shields Full-body armor vs separate leggings Added all-grade Soulshots and Spiritshots to bot inventory/replenishment so custom lower-grade weapons still use the correct shots. Mage profiles that already use Blessed Spiritshots keep that behavior with all relevant grades available. First save the bot normally so it exists in table:         lucera_autobots Then open:         lucera_autobots_items Find the row with the same bot_id and edit only the equipment slots you want. Example: weapon_id = 6608 shield_id = -1 helmet_id = 0 chest_id = 0 legs_id = 0 gloves_id = 0 boots_id = 0 This means: weapon_id 6608 → custom weapon shield_id -1 → no shield all 0 values → keep normal default profile equipment After editing the DB, despawn and respawn the saved bot so M54 reloads its equipment overrides. Do not edit bot_id. Use it only to identify which saved bot the equipment row belongs to.   DOWNLOAD
    • It will be multi client so it will detect the client from the files and adapt the packets and asset loading. I am aiming for C4 and H5 after IL
    • this is just to simplify your life, time, and can be done for free by yourself just watch some tutorials, in case you don't wanna waste time check it out!   https://l2getwork.art   https://l2getwork.art/showcase.html  
    • Good job! Any chance for it to be downgradeable or at least compatible with older chronicles?
    • Fermata now runs in a web browser too. Try it here: https://web.fermata.gg/    
  • 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..