Leaderboard

Classi is the soon to be 3rd ever ClassiCube server to fully support all of the CPE specifications. Please check out the readme on instructions on how to run it and how many features it has. This server is made as a replacement for MCGalaxy on cope's City and cope's Freebuild. https://git.sad.ovh/sophie/classi

Why are these your server rules

hii

Thank you! I'm promising quite lot of support for this software, as I'm running my own servers on it and I plan to make several gamemode servers (CTF, BedWars, PVP) with the plugin system.

Hello everyone i'm new in this game, but i'm so glad for can play

hi lol :D

Bro. I run that and my PC explodes.

There's no software that "doesn't support port forwarding". Port forwarding is a router thing, not a software thing.

The server now fully supports the CPE standard. The plugin system is vast and supports almost anything you'd imagine of doing with a classicube server. The barrier for entry in this plugin system aswell is very, very low. Documentation exists in .forgejo/.lua-stubs.lua, explaining all of the api.* functions that are in the Lua VM. It uses (as mentioned) Lua and is suitable even for Roblox luau developers.

It isn't censorship when there aren't many people in the community that can speak Spanish and willing to moderate.

The software's source code is right here. I think it would be a stupid move to slip some malware in when anyone can audit the code.

I did a little photo editing and dark magic, and I was just able to cheat the system, by replacing my skin with my desired avatar then disabling the sync feature so it locks!

It's no surprise already of all the amazing projects already made on ClassiCube. Whether it be the insane port of the Super Mario 64 movement or the Survival plugin which the community has been begging about for a while now, or even fun mini games such as Zombie Survival and Lava run. ClassiCube has already proven that it can be used as a basic game engine. Now what if someone were to port DooM or Quake to Classicube, possibly as a multiplayer deathmatch arena, single player campaign, or hecc maybe even both! This to me is a very interesting concept and I love seen other game engines being used to make totally new games. If anything I might personally take a look into making something similar. Though I believe the most difficult part would be copying the fast-paced movement from quake and possibly even the health + shield system. I would also want to optimize the project to be able to run well on most if not all platforms that ClassiCube has been ported to, as well as having features which make it easier for console players to play while not giving them too much power. Thus, balancing the gameplay. What do you guys think about this idea? If someone wants to help develop this, I can help with making the textures! (And if Im correct, i'm pretty sure ClassiCube already supports Quake 3 models.)

If I had to guess, the number you are currently thinking about is between 1-10000.

I highly recommend checking out Xonotic, it is a fast-paced action arena shooter similar to Quake. It's also free & open-source.

I've already shared this around on NA² discord and such, but thought this would be an appropriate post to mark off my return to the forums, as well as to show those of you who are unaware... Survival in ClassiCube is real now... Generally based on survival test c0.28, custom inventory handling and world save storage. I tried to keep it as kosher as possible for usage on servers but there are some edge cases where it can do bad things, like reloading your last save when you shouldn't be able to restore your position (parkour or adventure maps usually...). Servers can easily block it by kicking players with "+survival" in their appnames. You can punch your friends if they have the plugin as well, and death is handled appropriately. GitHubGitHub - xIcee/CC-SurvivalTest: multiplayer compatible Su...multiplayer compatible Survival Test plugin for ClassiCube - xIcee/CC-SurvivalTest

Welcome to the gang, enjoy your stay :3

https://f.classicube.net/profile/658-sand_block/reputation/ Clicking on the "reputation" box in your profile tells you what your rep is and why you have it

Cool stuff, I remember messing with this last year (made my own shader files and such), but reshade is unfortunately only usable on windows... An actual, real shader pipeline would be cool...

Well, that was stupid of me too.

I think so too🙂

it runs fine on emulators and real hardware

I'm not a good texture pack designer , but I present DigDown ⛏️ The current version is "Alpha 1.0". But I working now in the texture pack. The texture pack makes blocks with textures that haves a not big count of pixels in hers blocks. Download here About the "I'm not a good texture pack designer", it's real. I'm a player that a designer.

Go rent a server or something. It only really costs like 6€ a month. You cannot open a server without being able to port forward.

hmm

I need help figuring out how to get back to the main map when I die. It's for a map I'm making for MCGALAXY 1.9.5.3

:)

the forums are not for ban appeals

On the server you got blacklisted on.

hi

Se que la censura del idioma español le moleste,pero la comunidad hispana siempre anda por ahí molestado a los de habla inglesa,por ello, ellos censuran el idioma español porque están cansados de ser molestados y de la forma de como hablan la comunidad hispana

ok

no malware? 🤨

i reccomend making a classicube server using ZERO ai to start off, in a easier language to comperehend than C++, something like Python, JS, et cetera. i've made several classicube servers over the years, about 5 to 6 years ago I made cla55ic, which was a extremely simple classicube server that supported creating worlds, and that's about it about 3-4 years ago I made cla66ic which was a way more complicated and convoluted server I wrote using Deno and writing the whole protocol myself. now I'm working on Classi, which is a even more complicated and more convoluted general purpose server. it'll be used as a replacement for MCGalaxy on the cope's City server and currently runs the cope's Freebuild server. for example, you mentioned psudeoinfnite worlds, i wouldn't reccomend working on that at all to start off. try to limit your AI usage to as much as you can, ask it only questions that you'd ask google. don't just say "Fix my code why not work", ask for example "It seems like <this line> is returning false, why is this happening? Inspect my codebase". actually debug and figure out what you're writing. you should actually be working on: 1. Moderation of any kind 2. Plugins in a language of your choice (Lua, Python, et cetera) 3. BlockDB 4. High performance database for users, user bans and whatnot else you need to store. working on features that are extremely complicated like that will lead to you asking everything about the topic to AI, and in turn learning nothing yourself

You wake up in a dark room. Engulfed in complete blackness. Cold. It's so cold; almost unnatural. Then, suddenly, you hear a disembodied voice, echoing: "one word posts will get you banned."

How hypocritical of you. You talked about NSFW topics on my server long ago, and got warned for it.

You shouldn't be born then

still trying to fully read this without an aneurysm

isnt this just a reshade shader collection?

We will be working with the assumption that your map is named mylevel. If it's not, replace occurances of "mylevel" with your map's name when following this tutorial. You must have server file access to both servers to accomplish this. In order to fully move mylevel to another server you will need: For blocks and zones, mylevel.lvl file in `levels` For blockdefs (custom blocks), if the level only uses local blocks and does not use any globally defined blocks: lvl_mylevel.json in `blockdefs` if the level only uses global blocks: Clone global.json from `blockdefs` and rename it to lvl_mylevel.json before cloning the file to the other server if the level uses both global and local blocks: use ClassiCube to save the level as temp.cw, import it into a server (/help import), then grab lvl_temp.json and rename it to lvl_mylevel.json before cloning that file to the other server this servers the purpose of combining local and global blocks into one blockdef file For blockprops (slab stacking and etc), _mylevel.txt in `blockprops` For message blocks, 1. Extract the messages from the server database with /server backup table Messagesmylevel 2. Messagesmylevel.sql will now be in the root folder of your server. Bring this file to the root folder in the other server. 3. In the other server, use /server import Messagesmylevel For Portals, Repeat the steps for message blocks, but instead of "Messagesmylevel" use "Portalsmylevel" For bots, extra/bots/mylevel.json For all the remaining level properties (env, settings from /map, etc), mylevel.properties in `levels/level properties`

ClassiCube on TempleOS.

Hello everyone, I have recently made a full in depth custom block guide for ClassiCube. People have asked for it and it's finally here, enjoy: https://www.youtube.com/watch?v=DG9JgmdiJ-k

You have a humongous brain

(If you won't add textures skip to step 3) Requirements: - Copy paste knowledge - Acces to classicube files - A program to open .zip files - paint.net or gimp (Don't use Microsoft paint /3D or the transparency will be gone from the entire image) - A classicube server with /gb or /lb and textures (in my case I use MCGalaxy) Step 1: Creating the texture First, you need to get the textures to be able to modify them. Go to the folder where all your classicube files are. There try to find a folder named: In there is a file named: Copy the file and paste it into your desktop or anywhere else that is not in the classicube files. Open with the program you use to open .zip file. There, try to find and extract the file from . Open and start editing. To create a new texture replace with the texture/textures you will add (If you will add an animation read to understand how to add animations work) After adding the texture save the changes and takeagain inside in and upload to google drive or anything else Step 2: Enable the textures Go to you server's files In your server's files go to and in the folder find Open the file and find: Set the url with the url of the place you uploaded Start the server and join your server Step 3: Block creation The server will ask you if you want to use their textures. If not, press F10 to check if the textures are enabled To add the block in a specific level use /lb. To add the block in the entire the server use /gb then use /gb add then /gb (name of the block) then /gb 0 if it is a solid block like stone or type /gb 1 if its a sprite like flowers It will ask for textures of the block. To know wich texture is wich press F10. Each one has its own texture id EXAMPLE: The bedrock texture has an ID of 17 The other things /gb will explain to you Reply to this if you need help

they shouldn't be using a school machine to play video games tbh

Here are a list of other tutorials in the series: Chapter 1 - Introduction to building/building philosophy Chapter 2 - Familiarity with common commands/usages COMING SOON! Chapter 3 - Basic geometries and build styles COMING SOON! Chapter 4 - Detailing your builds COMING SOON! Chapter 5 - Creating and landscaping terrain COMING SOON! Chapter 1 - Introduction to building/building philosophy Having been a builder for around 11 years now, I think it's safe to say I've definitely learned some things and techniques through the years and these guides will hopefully help you improve on becoming a better builder. Before we start, I'm aware that many of you are eager to get to building - which is great! - and will likely skip this first chapter. I can safely say that this chapter is the most crucial and essential chapter in the series and skipping it will make the building process harder than it has to be. Planning your builds Many people like to rush into building without having an idea of what they're actually going to build. While this may work for some, for the rest of us, it makes building awkward and oftentimes we will lose inspiration quite quickly or head in a direction that we're not happy with. You should have a mental image of what you're wanting to build in your head. The more detail you provide, the better your build will be. Here are some examples taken from the Not Awesome 2 server. Keywords are highlighted in bold. "I'm going to build a cozy, Elven house with some trees surrounding it." Build created by Westbeam. Map: westbeam+2 on Not Awesome 2. "I'm going to build a European village with lots of buildings and next to some hills." Build created by okias (saiko). Map: okias+11 on Not Awesome 2. "I'm going to build a suburban neighbourhood with a city backdrop." Build created by StarlightGlimmer. Map: novacity on Not Awesome 2. Gathering inspiration Much like all great art pieces, artists need to gather inspiration from somewhere. Whether it be from your friends, builders you look up to or from the internet, inspiration can be found literally anywhere. A method I use quite often is going onto Google images and searching for "[whatever you're after] ArtStation". The reason I use ArtStation for inspiration is because it is home to some of the craziest artists I've ever seen and there is an endless supply of inspiration to be found there. After you've found some inspiration, it's important to know the three Rs of building: Remixing, Replicating and Ripping Off. Remixing Remixing occurs when you find a source of inspiration and you put your own spin on it to make it look unique. It's probably the most common of the three. It doesn't have to look exactly the same but you should be getting inspiration towards certain things from the source. For example in the images below, I wanted to make a medieval gate for my city so I decided to use a similar shape as the original image in my build. "Castle Gate" created by Jonathan Dufresne sourced from: ArtStation. Build created by Venk. Map: venk+1 on Not Awesome 2. Replicating To replicate something is to remake it almost the exact same as the source. I like to replicate things to learn new styles and from there, I can incorporate those styles into my future builds. "Statue Forest" created by Daniel Riise sourced from: ArtStation. Build created by Venk. Map: riise on Not Awesome 2. As you can see, I've started to replicate the image here by building it to look the same. Ripping Off Ripping Off is something you should not do, ever. Similarly to replicating, ripping off is making something exactly the same as something somebody else did, but claiming you made it entirely yourself without even acknowledging the original source. I've had a couple of instances of my maps being plagiarized over the years and it's definitely not a great feeling. Mapping out your builds Labelling Now that you've got an idea in your head and some inspiration, let's put it to work and start building it. When starting a build, you should always try and map out what is going to go where before actually starting to build. To do this, most servers have a command to write text. In MCGalaxy, it is /write, for others it may be /writetext or something else. Below is an image of one of my maps after labelling what I want to go where. Build created by Venk. Map: venk+ on Not Awesome 2. As you can see, I've labelled things like library and tavern so I know that a library and tavern will go here. Creating assets Assets are a nice and easy way to fill up your map quickly. While most people like to make all of their buildings unique and individualistic, using the same building once or twice isn't harmful at all. Away from your build - often in the sky -, you should make buildings or trees, essentially whatever assets you're planning on using later. This is so we can /copy them easily without getting the nasty excess blocks that we would get just copying from within the build itself. Build created by Venk. Map: venk2 on Puissant Royale. After you've created an asset bundle, you can start copying and pasting some of these builds into your main build. Build created by Venk. Map: venk2 on Puissant Royale. Colour coordination Colour coordination is a great way to identify things and assort them into groups. You should try and use blocks and colours that you aren't using in your build as it can be quite confusing when removing the labels. Below is an example of using colour coordination to plan directions for a road system. Build created by okias (saiko). Map: okias+15 on Not Awesome 2. Of course, this technique can be used in many different ways. For example, I use it to focus on areas that need to be worked on more than others. Build created by Venk. Map: ombshire_old on Puissant Royale. To-do lists To-do lists are probably the best method of monitoring your progress and knowing which areas need to be worked on. Surprisingly, not many people use this technique in their builds but you'll notice that the best builders use this technique quite often. Using that /write command we discussed earlier, we can make checkboxes which we can cross off after we've finished an area. Build created by okias (saiko). Map: ochre2 on Not Awesome 2. Maintaining focus and motivation Oftentimes when I build, I lose a lot of motivation on a project. In-fact, I'm notoriously known for having so many unfinished projects, it's scary. The reason for this is because I am constantly coming up with new ideas and want to build them all before I lose the flow, which I do recommend. If you're losing motivation on one of your builds, take a break from it and come back another time. If you keep going with no motivation/interest to keep going, chances are it will make the build seem like a chore and eventually, your build may start to go down-hill and you'll be unhappy with your project. Building is something you should do for fun, not as a chore.

I agree 654 but they should also make an outline of what they are going to build like then add the edges and build off of that like this simple house

sick kickflip numero uno: you can hover over the reaction button in the bottom right to show a list of reactions you can use. negative reactions will take away from the user's points, positive will add, and the more neutral/joke-y reactions don't do anything. epic kickflip dos: you can switch between the default theme and an experimental dark theme at the bottom of every page post more sick kickflips here and maybe i'll add them to the list

Having been a server owner for over 9 years now, I think it's safe to say I've been around long enough to see what works and what doesn't. Many people think having their own server makes them "cool" or "special" and rush into creating a server without knowing any of the essentials. Hopefully upon reading this guide, you'll understand what to do and what not to do. Knowing what your server will be about This is the most integral part in coming up with your own server. Before starting your server, you should have a general idea on what you want your server's purpose to be. The majority of servers on this site are effortless and generic freebuilds that offer little-to-nothing except for a freebuild map and overseer maps. You'll notice that these types of servers rarely get players because they are inherently boring and bring nothing new to the table. If you really want to stick with the freebuild genre, you should at least come up with some ideas on extra features to add to the server to ensure people don't get bored. Here are some ideas you could try: Themed freebuild maps An economy/money system Unique commands/plugins A server theme. E.g, oriental/fantasy, sci-fi/futuristic, modern, medieval etc. Your server's image Server name So you've come up with your server idea, now you just need a fancy name to lure the players in. You should include something related to your server's genre in your server's name. For example, if you are running a zombie survival server, you could set it to something like this: [Zombie Survival] Reign of Blood . This will tell people what your server is about and improve your chances of getting them to join. You should try and stay away from names that include your username. For example, Venk's Server. This is very boring and people probably won't join. Maturity and professionalism The way your server comes across is very important. If you want your server do well, you should typically stay away from messages that are rude or contain swearing/slurs. Don't get me wrong, there are a bunch of toxic servers out there that occasionally do well but at the end of the day, they all die out eventually. Grammar and punctuation is optional but it helps a lot. You should avoid stuff like this in any form of representations of the server: Bad: if u guys wanna go to other maps u should type the cmd /goto map Good: You can join other maps by typing /goto [map]. In regards to maturity, you should at least try and act mature but you do you... Below is an example of what to include and not to include in your rules. Bad: dont grief or u'll be banned!! WE DONT ALLOW GRIEFERS ON THIS SERVER SO JUST DONT!!! Good: Griefing is not allowed on the server. Hiring the right staff Chances are, you're not going to be on the server all the time, right? Having trustworthy staff online is a huge help and will heavily benefit you further down the track. Every server has their own expectations of staff but here is a template on what to look for in a staff member: Have they been active on the server? If they've only been on for like a couple of hours total, they're probably not a great choice as you may not know much about them. If they ask for staff, don't give it to them. Back in the day we used to call these people "Leeches" and muted them right off the bat... Are they respectful towards other players? You should probably refrain from hiring someone who is constantly carrying on and being rude to other people. This should ultimately go without saying but don't abuse your power. Just because you have a higher rank than someone doesn't mean you can behave like an ignoramus. I've seen countless instances where staff members abuse players and it's just despicable. You should also put your personal feelings towards someone aside and only punish them if they've actually violated the rules. "I just don't like them." is not a valid reason to punish somebody. Aesthetic Server hub If you want to provide a memorable experience for your players, you should make the server visually pleasing. A good-looking server hub or lobby is a great start as it immediately shows players that you've put some time into the server. If you don't consider yourself a good enough builder, I recommend asking a friend that you think is a good builder and see if they are willing to help. Colour scheme This might not seem to be that important but colours also help promote visual aesthetic. You should try and stay away from setting colours that are so bold and defining such as black, gray, maroon or navy. These colours are quite irritating to look at when used frequently. In MCGalaxy servers, you can add your own colours with the /customcolours command. Textures and block palette If your server software doesn't support these features, feel free to skip this section. As much as the default textures provide a sense of nostalgia, it gets old fast and people want to try something new. More tips coming soon!

These are some super important guidelines to follow when making your dirt house tutorial. If your thread is found to be of low enough quality, it will be expunged with extreme prejudice. Perhaps you'll even get a temporary ban, to sate our thirst for bans. Jk we won't ban you (probably). Title Guidelines Your thread's title must describe what the tutorial is about and be about the length of a short sentence. As an example: How to make a dirt house in 3 easy steps! Once you've got the title out of the way, you must make sure to set the tags. It's not super important that you add more than one, but that one is a doozy. It must categorize what the tutorial is for. As an example, if your tutorial pertains to a particular server software, add that server software name to your tags and then set it as your Item prefix. Here's an example: Tutorial Guidelines Make sure your tutorial ticks the following boxes: Has clear, easy-to-follow steps. Descriptive descriptions. Images for clarification A point (no, "how to get OP on my server" is not a good tutorial) Good luck making tutorials!