Jump to content

Recommended Posts

Posted

THE COUNTDOWN BEGINS NOW! I'm excited to announce that the Windforge Pirates Beta will be releasing on December 28th! Add this IP to your server list to join the moment it's open! 69.175.72.194:25587

I also wanted to take this chance to give everyone a bit of a tour of the world, and some more details about the gameplay of Windforge.


 

Brewing

vshQytA.jpg

One of the main ways to make money in Windforge is brewing. Invest money into creating and maintaining your brewing stations, and then flip it for a profit at the nearest Tavern.

v2PvsbL.pnghKN7rwl.png

 


 

Mining

vnfqwmc.jpg

Until you have breweries and farms set up, the secondary way of making money would be mining. Sell your hard earned valuables to the Blacksmith as you start your journey in the world.

kuajGpL.jpgPwKPL2B.png

 


 

Farming

The easiest, but by far the least profitable way to make money is farming. Sell your produce in bulk and make a decent profit.

5KUn2N1.jpgluQxHHD.png

 


 

Blackwater Port

A view of the docks.

Ports are safezones where all the trading and selling happens. When the beta opens there will be at least one port, although upon full release there will be three total. (one as the server spawn, and two more on opposite edges of the map) All ports will be linked by portals, which will make them serve as a "fast-travel" of sorts. Physically walking through these portals will be the only form of teleportation on the server. (except for /faction home, to save the location of your base) The lack of instant teleports will increase the challenge, the use of airships, and in turn the possibility of airship combat.

vH4g3jM.jpg

The town and the marketplace.

ZUU70AA.jpg

Some more of the town.

Kc4uluV.jpg

 


 

The Wilderness

M5YJVwr.jpg

The wilderness is the vast unexplored area of the world that YOU can claim for your own, build your own cities, farms, breweries and airships. Build or do anything you like. Live your life as a pirate, sailing the skies and preying on others. Or make an honest living as a merchant. It's entirely up to you.

IEit1JY.jpg

As you can see in this screenshot, the entire world is a mix of floating sky islands as well as regular land. It's incredibly diverse, and far more interesting than your regular old vanilla world.

zgMlQ99.jpg

More of the natural terrain generation.

KeAYyBM.jpg

LeO3l9b.jpg

There are still plenty of perfect places to build, as shown here.

QO7FEdr.jpg


 

All of this AND MORE will be releasing to the public on the 28th of this month! Spread the word!

Add this IP to your server list to join the moment it's open! 69.175.72.194:25587 (1.12.2 server version)

Also be sure to join our official Discord server for further updates and announcements! https://discord.gg/qCeFWg4

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Hello all. I'm currently grappling with the updateShape method in a custom class extending Block.  My code currently looks like this: The conditionals in CheckState are there to switch blockstate properties, which is working fine, as it functions correctly every time in getStateForPlacement.  The problem I'm running into is that when I update a state, the blocks seem to call CheckState with the position of the block which was changed updated last.  If I build a wall I can see the same change propagate across. My question thus is this: is updateShape sending its return to the neighbouring block?  Is each block not independently executing the updateShape method, thus inserting its own current position?  The first statement appears to be true, and the second false (each block is not independently executing the method). I have tried to fix this by saving the block's own position to a variable myPos at inception, and then feeding this in as CheckState(myPos) but this causes a worse outcome, where all blocks take the update of the first modified block, rather than just their neighbour.  This raises more questions than it answers, obviously: how is a different instance's variable propagating here?  I also tried changing it so that CheckState did not take a BlockPos, but had myPos built into the body - same problem. I have previously looked at neighbourUpdate and onNeighbourUpdate, but could not find a way to get this to work at all.  One post on here about updatePostPlacement and other methods has proven itself long superceded.  All other sources on the net seem to be out of date. Many thanks in advance for any help you might offer me, it's been several days now of trying to get this work and several weeks of generally trying to get round this roadblock.  - Sandermall
    • sorry, I might be stupid, but how do I open it? because the only options I have are too X out, copy it, which doesn't work and send crash report, which doesn't show it to me, also, sorry for taking so long.
    • Can you reproduce this with version 55.0.21? A whole lot of plant placement issues were just fixed in this PR.
    • Necro'ing that thread to ask if you found a solution ? I'm encountering the same crash on loading the world. I created the world in Creative to test my MP, went into survival to test combat, died, crashed on respawn and since then crash on loading the world. Deactivating Oculus isn't fixing it either, and I don't have Optifine (Twilight forest is incompatible)
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.