





🌟 Special thanks to our amazing supporters:
✨ $10 Tier: [Geeks Love Detail]
🌈 $5 Tier: [Arch Toasty][Benedikt][David Martínez Martí]
This entire week was dedicated to the dueling mechanics, since Duelland is an instance of a map and not a singular map the changes included some new instance mechanics and fixes too
Duels are between any 2 parties or individuals, they are flexible. Participants are restored to full hp/mp and a clean status state. After the duel, they are restored to their original positions and to their original states
Currently duels can be engaged with the /challenge chat command - either with name or by targeting someone
Technically, each duel is added to the server data, i.e. parent.S - If there's a duel in parent.S.duels - the transporter NPC lets anyone join and spectate the duel, during the duel, the instance data, i.e. parent.I is populated, parent.I.A includes the challenger party, I.B includes the acceptor party, each entity of the array is updated secondly with coordinates and other info like hp/character type (Going to document these soon)
This week was a "work freely" kind of week, while the dueling logic was complex, it was a 3 days job, so overall the performance of the week wasn't high, going back to working more structured in Week 14. As an important bit of info, acquired Google GCP Startup credits, so future servers will likely be hosted on the Google Cloud Platform (the backend was already on App Engine). Thanks to these credits, don't have to worry about costs as much
Wanting to concentrate on an improved Guide, Documentation and Tutorial for Week 14 - at least make some progress - as these 3 seem like prerequisites for growth
[ 6084 ]
[ 777 ]
[ 4040 ]