Jump to content

Ainz Ooal Gown

Elite Contributor
  • Posts

    623
  • Joined

  • Last visited

  • Days Won

    54

Ainz Ooal Gown last won the day on January 29

Ainz Ooal Gown had the most liked content!

About Ainz Ooal Gown

  • Birthday 09/07/1987

Profile Information

  • Gender
    Male
  • Location
    UK

Profile Fields

  • My Project
    Othala Dawn
  • GamerTag
    Ainz Ooal Gown
  • Steam ID
    RecoStar7

Recent Profile Visitors

15450 profile views

Ainz Ooal Gown's Achievements

  1. New World of Tanks: HEAT is decent, free to play so been blasting that since it came out
  2. Just set the Player Respawn LOC when a user is created or in common event "Set New Player Variables". Depending on your game you should have a common event that runs for your new players when they first create a character to set all the players variables.
  3. Hey, I believe this would have to be a source edit to set the default scale
  4. Can you show your weapon setup and NPC? As out the box calculations look to work fine. You can change how damage and defence is calculated by changing the formulas.json in server side folder > resources: { "ExpFormula": { "Source": "BaseExp * Power(Gain, Level)" }, "MagicDamage": "Random(((BaseDamage + (ScalingStat * ScaleFactor))) * CritMultiplier * .975, ((BaseDamage + (ScalingStat * ScaleFactor))) * CritMultiplier * 1.025) * (100 / (100 + V_MagicResist))", "PhysicalDamage": "Random(((BaseDamage + (ScalingStat * ScaleFactor))) * CritMultiplier * .975, ((BaseDamage + (ScalingStat * ScaleFactor))) * CritMultiplier * 1.025) * (100 / (100 + V_Defense))", "TrueDamage": "Random(((BaseDamage + (ScalingStat * ScaleFactor))) * CritMultiplier * .975, ((BaseDamage + (ScalingStat * ScaleFactor))) * CritMultiplier * 1.025)" }
  5. I have same issue with latest build. Issue raised: https://github.com/AscensionGameDev/Intersect-Engine/issues/2744
  6. Hi, Have you had a look through the official documentation for deployment? https://docs.freemmorpgmaker.com/en-US/deploy/forwarding/ Also this might be helpful: Double Check Port Forwarding Intersect Engine uses port 5400 by default (TCP). In your router settings: Make sure you're forwarding TCP port 5400 to your local IP address (like 192.168.x.x). Double-check the internal and external port numbers match. Make sure the local IP hasn't changed (set a static IP or DHCP reservation for your host machine). Firewall + Antivirus Temporarily disabling the firewall was a good test, but also check if antivirus software might have its own network protection. If your firewall is back on, make sure there's an inbound rule allowing TCP on port 5400. Test Using External IP Is the second device you are testing within the same network, or external to your network? Have a friend (or yourself using mobile data/tether) try connecting with your public IP address. You can find this at whatismyip.com. Example: if your IP is 123.123.123.123, they should enter that in the Intersect client. Check Intersect Server Config Open your resources/config.json on the server. Make sure port is correct “5400” or whatever you are using. Also verify the client configuration (client's resources/config.xml) points to your public IP (not localhost). ISP NAT or CGNAT Some ISPs use Carrier-Grade NAT (CGNAT), which blocks inbound connections. You can check if you’re behind CGNAT by comparing your router’s WAN IP with your public IP from whatismyip.com. If they're different, you might be under CGNAT, and port forwarding won’t work. In this case, you’d need to: Contact your ISP for a public/static IP. Or use a VPN with port forwarding like ZeroTier, Tailscale, or a VPS. UPnP and Router Reboot If your router supports UPnP, try enabling it or disable it if it’s causing issues. Always reboot the router after making port forwarding changes to ensure they apply. Server Logging / Debug Check Intersect’s server logs to see if it even registers the connection attempt from the outside device. If there’s no attempt at all, it means the request isn’t reaching your PC—pointing to a router or ISP block. Also I tend to do all my development locally on my machine and use Intersects Hosting for my deployed server: Hope this helps
  7. Good luck buddy, I hope you get a new laptop/PC soon and get back to development
  8. Hi, What you are trying to do is possible but will be a lot of work overall and wont be that efficient. Doing a source edit would be better to make this an actual function. Here are some issues you will come across using events to do this: You cant use \pv{variable} inside the descriptions of items/spells and such (I might raise this as a feature request as could be useful) You will need to create a variable for each item you want durability Need to consider what happens if the player has two of the same weapon/armour, using player variables will mean same items will have the same durability Setting the durability on pickup randomly: this will allow players to just drop the item and pick it back up for new durability? unless you make the items non droppable
  9. Hey sorry, no its not playable yet, far from it currently building the core system still. Might even put a few of them on here as new AOG event tutorials if I get time. Heres a preview of a cave I am currently making:
  10. Not playing any Intersect games currently. Middle Ages was one I was going to check out, but just been busy with work and building my game.
  11. This means that the developers have been working on a fix and applied to latest version. You can download the latest version of the engine from the nightly builds: Follow this guide to update you engine version: https://docs.freemmorpgmaker.com/en-US/upgrade/upgrading/
×
×
  • Create New...